Not that I could have missed the message... >> Updating Portage cache: 94%QA Notice: sed in global scope: sys-kernel/gentoo-sources-2.4.20-r33 99%QA Notice: has_version() in global scope: eclass gtk-engines2 !!! Your current profile is deprecated and not supported anymore. !!! Please upgrade to the following profile if possible: default-linux/x86/2005.0 To upgrade do the following steps: # emerge -n '>=sys-apps/portage-2.0.51' # cd /etc/ # rm make.profile # ln -s ../usr/portage/profiles/default-linux/x86/2005.0 make.profile # Gentoo has switched to 2.6 as the defaults for headers/kernels. If you wish # to use 2.4 headers/kernels, then you should do the following to upgrade: # emerge -n '>=sys-apps/portage-2.0.51' # cd /etc/ # rm make.profile # ln -s ../usr/portage/profiles/default-linux/x86/2005.0/2.4 make.profile # More information can be found at the following URLs: # http://www.gentoo.org/doc/en/gentoo-upgrading.xml # http://www.gentoo.org/doc/en/migration-to-2.6.xml QA Notice: has_version() in global scope: eclass gtk-engines2 !!! Your current profile is deprecated and not supported anymore. !!! Please upgrade to the following profile if possible: default-linux/x86/2005.0 To upgrade do the following steps: # emerge -n '>=sys-apps/portage-2.0.51' # cd /etc/ # rm make.profile # ln -s ../usr/portage/profiles/default-linux/x86/2005.0 make.profile # Gentoo has switched to 2.6 as the defaults for headers/kernels. If you wish # to use 2.4 headers/kernels, then you should do the following to upgrade: # emerge -n '>=sys-apps/portage-2.0.51' # cd /etc/ # rm make.profile # ln -s ../usr/portage/profiles/default-linux/x86/2005.0/2.4 make.profile # More information can be found at the following URLs: # http://www.gentoo.org/doc/en/gentoo-upgrading.xml # http://www.gentoo.org/doc/en/migration-to-2.6.xml QA Notice: has_version() in global scope: eclass gtk-engines2 !!! Your current profile is deprecated and not supported anymore. !!! Please upgrade to the following profile if possible: default-linux/x86/2005.0 To upgrade do the following steps: # emerge -n '>=sys-apps/portage-2.0.51' # cd /etc/ # rm make.profile # ln -s ../usr/portage/profiles/default-linux/x86/2005.0 make.profile # Gentoo has switched to 2.6 as the defaults for headers/kernels. If you wish # to use 2.4 headers/kernels, then you should do the following to upgrade: # emerge -n '>=sys-apps/portage-2.0.51' # cd /etc/ # rm make.profile # ln -s ../usr/portage/profiles/default-linux/x86/2005.0/2.4 make.profile # More information can be found at the following URLs: # http://www.gentoo.org/doc/en/gentoo-upgrading.xml # http://www.gentoo.org/doc/en/migration-to-2.6.xml 100% !!! Your current profile is deprecated and not supported anymore. !!! Please upgrade to the following profile if possible: default-linux/x86/2005.0 To upgrade do the following steps: # emerge -n '>=sys-apps/portage-2.0.51' # cd /etc/ # rm make.profile # ln -s ../usr/portage/profiles/default-linux/x86/2005.0 make.profile # Gentoo has switched to 2.6 as the defaults for headers/kernels. If you wish # to use 2.4 headers/kernels, then you should do the following to upgrade: # emerge -n '>=sys-apps/portage-2.0.51' # cd /etc/ # rm make.profile # ln -s ../usr/portage/profiles/default-linux/x86/2005.0/2.4 make.profile # More information can be found at the following URLs: # http://www.gentoo.org/doc/en/gentoo-upgrading.xml # http://www.gentoo.org/doc/en/migration-to-2.6.xml * IMPORTANT: 6 config files in /usr/kde/3.3/share/config need updating. * Type emerge --help config to learn how to update config files. !!! Your current profile is deprecated and not supported anymore. !!! Please upgrade to the following profile if possible: default-linux/x86/2005.0 To upgrade do the following steps: # emerge -n '>=sys-apps/portage-2.0.51' # cd /etc/ # rm make.profile # ln -s ../usr/portage/profiles/default-linux/x86/2005.0 make.profile # Gentoo has switched to 2.6 as the defaults for headers/kernels. If you wish # to use 2.4 headers/kernels, then you should do the following to upgrade: # emerge -n '>=sys-apps/portage-2.0.51' # cd /etc/ # rm make.profile # ln -s ../usr/portage/profiles/default-linux/x86/2005.0/2.4 make.profile # More information can be found at the following URLs: # http://www.gentoo.org/doc/en/gentoo-upgrading.xml # http://www.gentoo.org/doc/en/migration-to-2.6.xml These are the packages that I would merge, in order:
I missed to say that this is with Portage 2.0.51.19. etc-update prints three of these messages.
It should be painfuly clear now that you should update your profile. adding checks like this adds more code (20 bytes or so) to the base of portage which makes the image that gets loaded into memory larger/slower over time. looking at the code where there check comes from it looks like it it should only happen when the portage.py is first inherited.
Created attachment 55605 [details, diff] portage-2.0.51.19-deprecated-now-fatal.patch You could force the update with this patch.
Hmm, you should have gotten it only once (or maybe twice, but definitely not four times). If you run emerge -upvD world again, how often does it show up? solar: well, with that patch you won't be able to update portage first (if necessary).
>adding checks like this adds more code (20 bytes or so) to the base of portage which makes the image that gets loaded into memory larger/slower over time. Well, I'm not familiar with the code, but I'd say it's more about placing the message somewhere else than about adding checks. Imho this message should be only shown when you (pretend to) build stuff and not e.g. when doing `emerge --info`,... It's of course not a big issue, but as annoying as a popup window. Marius: Five messages. As I said, I had to update config files and calling etc-update by hand yields in three warning messages. My guess should't be too wild, that this relates.
i think the reason you saw it so often is because your cache was messed up and when portage regenerated the cache the hard way, you got all those warnings ...
Sure, it regenerates the cache when I call etc-update... I don't think so.
Mike was on the right track as was Ned. You get the notice each time portage.py is imported. That's once for running emerge and once for every call of portageq. $ grep portageq /usr/sbin/etc-update USERLAND="$(/usr/lib/portage/bin/portageq envvar USERLAND)" CONFIG_PROTECT=$(/usr/lib/portage/bin/portageq config_protect) CONFIG_PROTECT_MASK=$(/usr/lib/portage/bin/portageq config_protect_mask) Three times... Could just wrap the code with a PORTAGE_CALLER == emerge type hack.
Added the PORTAGE_CALLER hack.
Fixed on or before 2.0.51.22-r1
Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened.
