RESOLVED: Vague portage msg about fixpackages/FEATURES

bus_drivr · n00b Joined: 20 Feb 2003 Posts: 48 Location: Florida

Hi
From what I have seen of fixpackages behaviour it complains about invalid packages if a newer version of a package is being used. This was the case once. It complained about another pkg here as well. Not sure why on that one. Dependency that is no longer required?
The categories under /usr/portage are changing and packages are moving. I suspect that fixpackages handles changes in catgories helping to resolve moved dependencies. No proof of that, just a guess.

bus_drivr

StuBear · Posted: Fri Jun 20, 2003 5:59 am Post subject:

jukka · Posted: Fri Jun 20, 2003 8:35 am Post subject:

tecknojunky · Posted: Wed Jun 25, 2003 12:27 am Post subject:

Keyed · Posted: Tue Jul 15, 2003 5:37 am Post subject:

To date I have'nt seen much good in the "fixpackage" script. Almost after every "emerge sync" I get this with one or more file names

jukka · Posted: Tue Jul 15, 2003 6:36 am Post subject:

Problem solved!

I replaced Gentoo with NetBSD, and now I don't have to run 'fixpackages' and 'emerge sync' anymore, so the problems are gone. ;-)

HTH, Jukka

Genone · Posted: Fri Sep 19, 2003 4:38 am Post subject:

fixpackages (both FEATURE and script) will hopefully be much friendlier in the next portage release (increased speed, only run when necessary), see bugs 28704 and 28705.

trinladen

Im now certian after reading all the posts here that fixpackages is really a DLL thats suppose to run on XP.

I get those kinda errors and fixpackages doesnt help at all. Does anyone have any better ideas?

...........!!! Cannot update binary: Destination exists.
!!! sys-apps/jfsutils-1.1.2 -> sys-fs/jfsutils-1.1.2
.....!!! Cannot update binary: Destination exists.
!!! sys-apps/raidtools-1.00.3-r1 -> sys-fs/raidtools-1.00.3-r1
.!!! Cannot update binary: Destination exists.
!!! sys-apps/reiserfsprogs-3.6.8 -> sys-fs/reiserfsprogs-3.6.8
...!!! Cannot update binary: Destination exists.
!!! sys-apps/xfsprogs-2.3.9 -> sys-fs/xfsprogs-2.3.9
..!!! Cannot update binary: Destination exists.
!!! app-admin/dosfstools-2.8-r3 -> sys-fs/dosfstools-2.8-r3
.....!!! Cannot update binary: Destination exists.
!!! dev-libs/progsreiserfs-0.3.0.4 -> sys-fs/progsreiserfs-0.3.0.4

etc , etc and etc ......

running "fixpackages" did nada. I Do HOPE this gets fixed. Im running the latest version of the awesome fixpackages. Lemme know if any of you have a fix or a workaround.

Thanks
trinity

jaz9090 · Apprentice Joined: 11 Sep 2003 Posts: 214

yeah i keep getting the errors above, can anyone help?

cybrjackle · Apprentice Joined: 09 Jan 2003 Posts: 248 Location: USA

Is there any reason why if you use some binary's during the inital install that you just cant wipe /usr/portage/packages out of the tree?

Genone · Posted: Fri Oct 10, 2003 8:58 pm Post subject:

If you don't plan to install binaries you can delete /usr/portage/packages. Personally I just keep them as a backup in case a new package breaks.

torque2k3 · Posted: Sat Oct 11, 2003 1:55 am Post subject:

Sorry to flog a dead horse, but mine's come back to life. Has anyone confirmed that removing the .tbz2 file (no name, just extension) makes "fixpackages" go away?! I see that lots of people have yet to "confirm" it works, but this is from June. My system's bugging me again after EVERY emerge sync, and I'm using a GRP install of build 20030911 (i686) over a dialup on a P4... and it takes over 20 minutes to run fixpackages!!! :evil:

Thanks,
Dan

Genone · Posted: Sat Oct 11, 2003 2:04 am Post subject:

If there aren't any .tbz2 packages fixpackages doesn't have much to do. The message will stay there. If you don't want to run fixpackages don't do it.
fixpackages only corrects wrong dependencies in .tbz2 packages
(I should know that as I rewrote nearly the complete fixpackages code).

converter · Apprentice Joined: 24 Dec 2002 Posts: 163

Why does fixpackages fix the same wrong dependencies in the same packages every time it runs?

I didn't mind fixpackages at first, but there were several package moves recently that drove the run-time through the roof. Can we not write a "fixed" file somewhere so that fixpackages applies each fix only once? I need binaries, but the last time I ran fixpackages it took about five hours to complete (ATA/100, but only a PIII 733). Sorry, but this is just awful.

Also, I noticed a "pure Python" patch for fixpackages in a bugzilla bug (sorry, I don't recall the #) several days ago that the author claims eliminates a handful of forks per package and brings a great speed increase. Has this patch been looked at?
_________________
converter

Genone · Posted: Mon Oct 13, 2003 7:43 am Post subject:

Let me start at the end: I wrote the patch, it seems to work, I'll see if it can go in one of the next portage releases.
A "fixed" status file might help a bit, I'll check this option for further improvements (don't know if it helps or hurts). There is also something in fixpackages that I call a bug while the portage maintainer calls it a feature (the fixpackages tool is always using all update files), there are reasons to do that but over time it really hurts. Because of this the FEATURES="fixpackages" method will also be faster than the fixpackages script but might run more often, that's something everyone has to decide for himself.

trinladen · Posted: Mon Oct 13, 2003 9:09 am Post subject: actually ..

I see your point. I dont run fixpackages on an older system so the speed isnt a problem, however
I run it and I STILL get packages it cant or doesnt know how to "move". Im wondering how to deal with those ??? Any ideas ...

Thanks
Trin

deathbaz · n00b Joined: 02 Oct 2002 Posts: 12 Location: NZ

ozric100 · Tux's lil' helper Joined: 23 Apr 2002 Posts: 136

tecknojunky · Posted: Mon Jan 26, 2004 6:35 am Post subject:

I usualy ignore the fixpackages, but I recently started to get emerges failing with (approximatly) "/usr/portage/packages/All/ebuildname.tbz2: already exist. Run fixpackages", so I did.

So I ran fixpackages again: it only took 18 hours (or so). The worst is that I still get the error message.

This has to stop. There must be a better way to do this.
_________________
(7 of 9) Installing star-trek/species-8.4.7.2::talax.

deathbaz · n00b Joined: 02 Oct 2002 Posts: 12 Location: NZ

alkama · n00b Joined: 18 Mar 2004 Posts: 1

I have those problems with fixpackages.

It claims it cant find a "foobar" thing and also detects existing files in destination... like:

!!! Cannot update binary: Destination exists.
!!! sys-apps/raidtools-1.00.3-r1 -> sys-fs/raidtools-1.00.3-r1
......!!! Cannot update binary: Destination exists.
!!! app-admin/dosfstools-2.8-r3 -> sys-fs/dosfstools-2.8-r3

i also have a lots of binary packages "*********************************" and this makes the fixpackage run a fucking long time....

So here is my question:
can i delete the dir and files in "/usr/portage/packages/" ?
if seems to contain a "All/" directory with a lot of .tbz2 files inside...
_________________
lets reinvent the wheel altogether

sjj698 · n00b Joined: 14 Jan 2004 Posts: 8

has anyone got any ideas on this 'fixpackages' option. I have a server which i use to build binary packages for a small cluster.
As there are lots of binary packages, it takes about 20-30min! (dual 1ghz PIII)

Are there any options to speed this up?

thanks
Steven

struhs · n00b Joined: 14 Jun 2005 Posts: 44

I have no "buildpkg" in my FEATURES and I don't need binary packages, except Sun's Java and OpenOffice, but /usr/portage/packages is full of packages. After each emerge sync I have to run fixpackages which takes a very long time (at least an hour): it starts doing something with "/usr/portage/profiles/updates/3Q-2002" until it reaches "/usr/portage/profiles/updates/4Q-2005" (each time I run it). Is this correct and neccessary?

I am very annoyed of this!

Any ideas? :?:

Can I just delete the packages directory?

sourcebased · n00b Joined: 27 Jan 2005 Posts: 4 Location: Berlin