glibc downgrades are considered a very bad thing in most cases but portage currently allows this without a warning. glibc ebuilds should check if they are downgraded, print a warning and abort if that is the case. For special cases this can be overridden with a environment flag.
Created attachment 14986 [details] pkg_setup function to detect downgrades This patch is not perfect as it also aborts if only the revision number changes but should prevent all major downgrades.
This bug has bitten me. IT HURTS!!!! I know I am stupid and all but hey thats how ya learn.
It's mostly useful for glibc, not so important for other packages.
I have also just been bitten by this. I went to "upgrade" openssh and it wanted a glibc upgrade as well but it turns out that I must have assumed, without really reading the version numbers, that portage knew what it was doing and really was upgrading glibc. Turns out it did not and now am having to build python by hand to get emerge working again so that I can fix the glibc version! Ouch!! Definitely think that emerge should check the glibc version and not allow it even this is a feature only limited to glibc.
portage people have ideas? maybe a DANGER="downgrade" type syntax in the ebuild or so?
are there any other packages where this would be such important ?
toolchain peeps, could I get at least a bit of feedback ? This is sitting here nearly for a year now. Well, if noone objects I'll add it myself at the end of next week.
done
previous python solution caused a lot of bugs ... think we could do this now with the versionator eclass ?
*** Bug 59704 has been marked as a duplicate of this bug. ***
Should be fixed by portage-2.0.51.19: # emerge -C glibc !!! Trying to unmerge package(s) in system profile. 'sys-libs/glibc' !!! This could be damaging to your system. >>> Waiting 10 seconds before starting... >>> (Control-C to abort)... Press Ctrl-C to Stop in: 10 Exiting on signal 2
