Andrew Lowe schrieb am 06.11.2010 16:56: > On 11/06/10 20:30, Neil Bothwick wrote: >> On Sat, 06 Nov 2010 12:36:01 +0800, Andrew Lowe wrote:
>>> .='update pass' *='binary update' #='/var/db update' @='/var/db >>> move' s='/var/db SLOT move' %='binary move' S='binary SLOT move' >>> p='update /etc/portage/package.*' >>> /usr/portage/profiles/updates/1Q-2005................ >>> ..................................................... >>> ..................................................... >>> ..................................................... >>> ..................................................... >>> .............. >>> /usr/portage/profiles/updates/4Q-2010........ These are normal messages you receive if there are ebuilds moved around or slots for ebuilds change within the portage tree. It has nothing to do with the profile you are running. Portage saves all data for installed packages in a database under /var/db/pkg. Lets say you have installed dev-lang/toluapp. Recently this package has been moved to dev-lua/toluapp. The information about this package is now wrong and needs to be fixed. This is what happened here. It also takes care about existing binary packages. So there is nothing to worry about. Just take a look at these files and you will find lines like: slotmove sys-libs/libchipcard 2 0 move dev-lang/toluapp dev-lua/toluapp It just informs portage about the changes, so it can fix it in the database. >>> * An update to portage is available. It is _highly_ recommended A new version of portage is available and you should update to that new version. > Is the first line of emerge --info, > > Portage 2.1.9.24 (default/linux/amd64/10.0/desktop/kde, gcc-4.4.5, > glibc-2.12.1-r1, 2.6.35-gentoo-r9 x86_64) Yes this is the profile you are running and it is the most recent, so no need to change anything here. You are not running the 2005 profile, which would be strange as it has been removed long ago. -- Daniel Pielmeier
signature.asc
Description: OpenPGP digital signature
