SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-21-2008, 09:41 AM
| ||||
| ||||
 emerge question what does the following mean after and emerge --sync? Performing Global Updates: /usr/portage/profiles/updates/2Q-2005 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' @='/var/db move' s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*' .......... ** Skipping packages. Run 'fixpackages' or set it in FEATURES to fix the tbz2's in the packages directory. Note: This can take a very long time. I ran fixpackages and it went away for a while, but is now back. Bigbob      |
|
02-21-2008, 09:41 AM
| |||
| |||
| Re: emerge question bigbob enlightened us with: > ** Skipping packages. Run 'fixpackages' or set it in FEATURES to fix the > tbz2's in the packages directory. Note: This can take a very long time. You only need to do this if you're maintaining a repository of binary packages. I'm not 100% sure what it does, though. Sybren -- The problem with the world is stupidity. Not saying there should be a capital punishment for stupidity, but why don't we just take the safety labels off of everything and let the problem solve itself? |
|
02-21-2008, 09:41 AM
| ||||
| ||||
| Re: emerge question bigbob wrote: > what does the following mean after and emerge --sync? > Performing Global Updates: /usr/portage/profiles/updates/2Q-2005 > (Could take a couple of minutes if you have a lot of binary packages.) > .='update pass' *='binary update' @='/var/db move' > s='/var/db SLOT move' S='binary SLOT move' > p='update /etc/portage/package.*' > ......... > > > > ** Skipping packages. Run 'fixpackages' or set it in FEATURES to fix the > tbz2's in the packages directory. Note: This can take a very long time. > > I ran fixpackages and it went away for a while, but is now back. fixpackages reads the binary files that you have and updates the metadata that's present (for them) to match the information stored in /usr/portage/profiles/updates/[1-4]Q-200*, which are quarterly update informations for all binary packages (the reason why this message comes up from time to time). Sometimes packages move in the portage tree (i.e., changes its category). Because portage stores tree metadata in the package itself, it won't accept a the binary package if the metadata says that it's actually <category/<whatever> which you have rather than <anothercategory>/<whatever>. -- Regards, Karsten |
Linear Mode
