FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 11-06-2010, 03:36 AM
Andrew Lowe
 
Default Updating a profile from 2005

Hi all,
I've just done an

emerge --sync

ad got, along with all the usual stuff, the following:

*************************
...
...
...
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?


Any thoughts greatly appreciated,

Andrew
 
Old 11-06-2010, 11:30 AM
Neil Bothwick
 
Default Updating a profile from 2005

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.
 
Old 11-06-2010, 02:56 PM
Andrew Lowe
 
Default Updating a profile from 2005

On 11/06/10 20:30, Neil Bothwick wrote:

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,
Simple answer to your first question, I'm not - well I didn't do
anything to ask for a profile from 2005. As I said, this thing was built
form scratch, using an install disk downloaded about 6 months ago, I did
nothing such as bringing across old configs/profiles, this thing has
just showed up.


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)


the line that will tell me which profile I'm running? As I said, I've,
not knowingly, done anything to make this profile appear, it's just
appeared. In the dir /usr/portage/profiles/updates, there are a whole
series of profile file. Do all of these need to exist? Should I get rid
of all of them, except for the current?


Andrew
 
Old 11-06-2010, 04:17 PM
Mick
 
Default Updating a profile from 2005

On Saturday 06 November 2010 04:36:01 Andrew Lowe wrote:
> Hi all,
> I've just done an
>
> emerge --sync
>
> ad got, along with all the usual stuff, the following:
>
> *************************
> ...
> ...
> ...
> 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?
>
> Any thoughts greatly appreciated,

I can't really answer your question (other than your may have used a really
old install CD).

You could check to see which make.profile your /etc/make.profile is symlinked
to. For example:

# ls -la /etc/make.profile
lrwxrwxrwx 1 root root 56 Jun 8 20:36 /etc/make.profile ->
../usr/portage/profiles/default/linux/amd64/10.0/desktop

Or you can try the eselect tool to list/set a suitable profile; e.g.:

# eselect profile list
Available profile symlink targets:
[1] default/linux/amd64/10.0
[2] default/linux/amd64/10.0/desktop *
[3] default/linux/amd64/10.0/desktop/gnome
[4] default/linux/amd64/10.0/desktop/kde
[5] default/linux/amd64/10.0/developer
[6] default/linux/amd64/10.0/no-multilib
[7] default/linux/amd64/10.0/server
[8] hardened/linux/amd64/10.0
[9] hardened/linux/amd64/10.0/no-multilib
[10] selinux/2007.0/amd64
[11] selinux/2007.0/amd64/hardened
[12] selinux/v2refpolicy/amd64
[13] selinux/v2refpolicy/amd64/desktop
[14] selinux/v2refpolicy/amd64/developer
[15] selinux/v2refpolicy/amd64/hardened
[16] selinux/v2refpolicy/amd64/server

HTH.
--
Regards,
Mick
 
Old 11-06-2010, 05:57 PM
Stroller
 
Default Updating a profile from 2005

On 6/11/2010, at 3:56pm, Andrew Lowe wrote:
> ...
> 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)

Considering that, you should be perfectly safe to update to the current profile (as explained by Mick in his message of 40 minutes ago) and `emerge --update -p world`.

If your system hasn't been updated in 6 months then look out for the libpng update:
http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update

> the line that will tell me which profile I'm running? As I said, I've, not knowingly, done anything to make this profile appear, it's just appeared.

This is somewhat inexplicable.

> In the dir /usr/portage/profiles/updates, there are a whole series of profile file. Do all of these need to exist? Should I get rid of all of them, except for the current?

Nope, these are generated by `emerge sync` - old ones will be deleted automagically when you update (which is why it's so confusing you have a 2005 profile configured). You just need to change to the current one and update world.

BTW: I assume you're new to Gentoo, because most everything in /usr/portage/ is managed by Portage, and this directory tree needs little maintenance or intervention. The only exceptions are /usr/portage/packages and /usr/portage/distfiles - `emerge gentoolkit` and run `eclean` a couple of times a year.

Generally speaking you should be running `emerge --update world` about every week or every month - after 2 months or more the update becomes a bit more of a chore, and if you leave it as long as 6 months you're pretty much sure to encounter problems like this one with the libpng update, but not always be so well documented.

Stroller.
 
Old 11-06-2010, 06:30 PM
Daniel Pielmeier
 
Default Updating a profile from 2005

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
 
Old 11-06-2010, 07:15 PM
Andrew Lowe
 
Default Updating a profile from 2005

On 11/07/10 02:57, Stroller wrote:


On 6/11/2010, at 3:56pm, Andrew Lowe wrote:

... 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)


Considering that, you should be perfectly safe to update to the
current profile (as explained by Mick in his message of 40 minutes
ago) and `emerge --update -p world`.

If your system hasn't been updated in 6 months then look out for the
libpng update:
http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update


No, you've misunderstood. The machine was built about 6 months ago but
has had "emerge -NuD world" run probably a dozen times in this
intervening time.





the line that will tell me which profile I'm running? As I said,
I've, not knowingly, done anything to make this profile appear,
it's just appeared.


This is somewhat inexplicable.


In the dir /usr/portage/profiles/updates, there are a whole series
of profile file. Do all of these need to exist? Should I get rid of
all of them, except for the current?


Nope, these are generated by `emerge sync` - old ones will be deleted
automagically when you update (which is why it's so confusing you
have a 2005 profile configured). You just need to change to the
current one and update world.


agl@bluey ~ $ eselect profile list
Available profile symlink targets:
[1] default/linux/amd64/10.0
[2] default/linux/amd64/10.0/desktop
[3] default/linux/amd64/10.0/desktop/gnome
[4] default/linux/amd64/10.0/desktop/kde *
[5] default/linux/amd64/10.0/developer
[6] default/linux/amd64/10.0/no-multilib
[7] default/linux/amd64/10.0/server
[8] hardened/linux/amd64/10.0
[9] hardened/linux/amd64/10.0/no-multilib
[10] selinux/2007.0/amd64
[11] selinux/2007.0/amd64/hardened
[12] selinux/v2refpolicy/amd64
[13] selinux/v2refpolicy/amd64/desktop
[14] selinux/v2refpolicy/amd64/developer
[15] selinux/v2refpolicy/amd64/hardened
[16] selinux/v2refpolicy/amd64/server

This is what I get from eselect. Once again, I haven't changed any
profiles, this is how it was before the 2005 profile appeared.




BTW: I assume you're new to Gentoo, because most everything in


Yes and no. Just had a look at forums.gentoo.org, I registered there in
2002, but my use has been sporadic. Now about to do a PhD in
Computational Fluid Dynamics and will be using my Gentoo box to run the
apps so will be using it a bit more now



/usr/portage/ is managed by Portage, and this directory tree needs
little maintenance or intervention. The only exceptions are
/usr/portage/packages and /usr/portage/distfiles - `emerge
gentoolkit` and run `eclean` a couple of times a year.

Generally speaking you should be running `emerge --update world`
about every week or every month - after 2 months or more the update
becomes a bit more of a chore, and if you leave it as long as 6
months you're pretty much sure to encounter problems like this one
with the libpng update, but not always be so well documented.



Nothing new here, I've done all these things. As I seem to be already
doing the stuff people suggest, and as everything is working and nothing
seems harmed by the 2005 profile, just leave it and hopefully it will
disappear - correct?


Andrew




Stroller.
 
Old 11-06-2010, 08:30 PM
Neil Bothwick
 
Default Updating a profile from 2005

On Sun, 07 Nov 2010 04:15:48 +0800, Andrew Lowe wrote:

> This is what I get from eselect. Once again, I haven't changed any
> profiles, this is how it was before the 2005 profile appeared.

You don't have a 2005 profile available, let alone selected. The message
related to renamed packages, and when they were renamed, your profile is
fine.


--
Neil Bothwick

RAM disk is *not* an installation procedure.
 

Thread Tools




All times are GMT. The time now is 10:55 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org