RESOLVED: Vague portage msg about fixpackages/FEATURES

Pythonhead · Last edited by Pythonhead on Fri May 23, 2003 9:54 pm; edited 1 time in total

After doing an 'emerge rsync' I got this message:

pjp · Administrator Joined: 16 Apr 2002 Posts: 20606

pjp · Administrator Joined: 16 Apr 2002 Posts: 20606

fixpackages is located at /usr/lib/portage/bin/fixpackages

fixpackages updates your binary packages in /usr/portage/packages in case there were package moves. A package move is when a package (ebuild) is moved from one category to another. For example, if a package was in app-misc, then was moved to app-editors.

As for the portage "FEATURE" vs. the program, the FEATURE version will run everytime you sync (I think), keeping things current. The program fixpackages is probably more useful for the first time update so you can schedule it when you want (it might take quite a while to run).
_________________
Quis separabit? Quo animo?

Braempje · l33t Joined: 31 Jan 2003 Posts: 748

Worked great, thanks!

idiotprogrammer · Apprentice Joined: 29 Jul 2002 Posts: 179 Location: Texas

so what this message means is:

When you get a chance, you need to run fixpackages. It can take a long time (how long is long?)

So this only applies to binary packages? So because most of the ebuilds are from source, this won't really matter except for certain packages (jdk-sun, open-office-bin, realplayer, etc). Right?

Is this a normal or a problem message?

avenj

Pythonhead · Posted: Fri May 23, 2003 9:49 pm Post subject:

I ran fixpackages and it seemed to go smoothly.
It took a whopping two seconds.

Thanks.

To · Posted: Sat May 24, 2003 11:32 pm Post subject:

Same thing here, no probs and only a few seconds

Sieg · Tux's lil' helper Joined: 07 Oct 2002 Posts: 87

Tks for the info. Works well, except I get errors during the process, but then it says "Done"

Peach · Posted: Tue May 27, 2003 5:51 pm Post subject:

Sieg I have your same identical problem... what's wrong with tbz2 packages ???

ARC2300 · Apprentice Joined: 30 Mar 2003 Posts: 267

Thanks. . .helped immensely.

pjp · Administrator Joined: 16 Apr 2002 Posts: 20606

fixpackages can be ignored unless you use -b or FEATURES="buildpkg".

users of "-b" and "buildpkg" should only be concerned if you try to install a binary package, and it complains about unfillable dependencies.
_________________
Quis separabit? Quo animo?

keifir · Posted: Wed May 28, 2003 12:48 am Post subject:

thx pjp,

I started building alsa-driver binary package - since i need to reemerge it everytime i compile kernel modules. Now i know what this fixpackage is. :wink:

thx for info,
keifir

no usernames left · n00b Joined: 09 Feb 2003 Posts: 72

In my opinion the message should only get displayed if there actually are some packages in /usr/portage/packages, simply because it makes no sense to display it / run fixpackages otherwise. But it's a nice feature.

_________________
[img:39112bbc59]http://www.gamers-portal.de/images/yay.gif[/img:39112bbc59]

ShadowDemon · Posted: Mon Jun 02, 2003 11:28 pm Post subject: Every time?

I ran fixpackages the first time I got the message and now every time I rsync or emerge a package it prompts me to run fixpackages again. Is this normal?

jukka · Posted: Tue Jun 03, 2003 9:47 pm Post subject: Re: Every time?

Nahor · n00b Joined: 05 Jun 2003 Posts: 51

I was getting an error too most of the time I "synced" with the added message ".!!! Invalid binary package: .tbz2".
Running fixpackages showed that error each time.
Then I looked at what kind of tbz2 I had in /usr/portage and I noticed a file named ".tbz2", no basename, just an extension. The file was 78 bytes
I just deleted the file and now fixpackages doesn't complain about the invalid binary package. I'll see tomorrow if 'emerge sync' still complains.

jukka · Posted: Thu Jun 05, 2003 7:31 am Post subject:

Braempje · l33t Joined: 31 Jan 2003 Posts: 748

jukka · Posted: Fri Jun 06, 2003 6:28 am Post subject:

Braempje · l33t Joined: 31 Jan 2003 Posts: 748

Moving it away solved the error, but I find it extremely strange that it just got there... The contents didn't seem important...
_________________
Dictionary of the Flemish Sign Language - Woordenboek Vlaamse Gebarentaal

klasikahl · Posted: Sat Jun 07, 2003 5:07 pm Post subject:

you guys who report it taking "two seconds" are quite lucky. I have been searching for a script that rm -f's packages that already have a newer version in /usr/portage/packages, but haven't quite found one yet. Thus, my packages dir looks like this...

tactless · Posted: Wed Jun 11, 2003 11:56 am Post subject:

Is it just me, or is /usr/portage/packages being used instead of /usr/portage/distfiles? In that case, how do we move all of the distfiles (quickly :wink:

).
_________________
Tactless

"If it wasn't for fog, the world would run at a really crappy framerate."

Jabber: tactless@amessage.info

Stalione · Guru Joined: 21 Apr 2002 Posts: 335

You know im just curious if there was even an annoncement made regarding the release and use of fixpackages. I just don't like surprises thats all. Also the lack of documentation (man, help) on this tool is quite frustrating. I have to come to the forums to find out exactly what it was.

jukka · Posted: Wed Jun 11, 2003 7:16 pm Post subject:

Hmm, could someone who really understands what fixpackages does please explain it to me? I can see it applies some updates to /var/db/pkg; unpacks, fixes and repacks packages in /usr/portage/packages; etc.
What I don't understand is why this is done after every 'emerge sync' for all packages (which were already fixed by the last 200 runs of fixpackages...). Yes, I know, I could remove 'fixpackages' from FEATURES, and I don't have to run fixpackages manually, but I don't like to rebuild packages after minor changes like when they are moved to another category...

Greetings, Jukka