Currently, when portage detects a deprecated profile via /usr/portage/profiles/$profile/deprecated, it informs the user that their profile is not supported anymore, but it does not say how to fix the problem. Current output: !!! Your current profile is deprecated and not supported anymore. !!! Please upgrade to the following profile if possible: hardened-x86-2004.0 Perhaps do something along the lines of: !!! Your current profile is deprecated and not supported anymore. !!! Please upgrade to the following profile if possible by doing !!! rm /etc/make.profile; ln -sf /usr/portage/profiles/hardened-x86-2004.0 !!! /etc/make.profile: hardened-x86-2004.0 I can create a patch if necessary. Also, when portage is emerged (2.0.50), and there is a deprecated profile, the output is a touch messed up: * Feature additions are noted in help and make.conf descriptions. * GENTOOLKIT will need to be updated to at least 0.2.0 for some tools * to work properly. * Update configs using 'etc-update' please. Maintaining current configs * for portage and other system packages is fairly important for the * continued health of your system. Recalculating the counter... Counter updated successfully. >>> Clearing invalid entries in dependency cache...!!! Your current profile is deprecated and not supported anymore. !!! Please upgrade to the following profile if possible: hardened-x86-2004.0 We need a "\n" in there.
Created attachment 24660 [details, diff] patch to allow configurable upgrade message new format for deprecated file: - first line has the name of the new profile - remaining lines can be used for the upgrade message
I just got this "deprecated profile" message on today's sync. Even after reading this bug report I have no idea what the message is talking about. I see on the Gentoo forum that I'm not alone in my confusion. How 'bout including a reference in the message to some documentation explaining what "deprecated profile" means?
the deprecation of default-amd64-1.4 and default-x86-1.4 was an accident ... it'll go away next time people rsync
supposed to be fixed in 2.0.50 which is stable now. If this bug is not fixed please reopen.
