On Sat, 06 Nov 2010 12:36:01 +0800, Andrew Lowe wrote: > Performing Global Updates: > (Could take a couple of minutes if you have a lot of binary packages.) > > > .='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........ > # > > > * An update to portage is available. It is _highly_ recommended > ... > ... > ... > ************************* > > The question is: Should a profile from 2005 be > updated as well? I built this machine from scratch about 6 months ago > so there wasn't something like a "favourite config" I brought across > from another machine. Is this normal behaviour? Should I be worried? > Should I zealously try and track this down and kill it or should I let > bygones be bygones?
Why are you running a 2005 profile? I don't think that was even available six months ago. emerge --info will tell you which profile you are actually using, but if portage tells you to it needs updating, it is usually right. -- Neil Bothwick A closed mouth gathers no foot.
signature.asc
Description: PGP signature
