Error: sys-libs/glibc-2.9_p20081201-r3 failed [Solved]

[LastPanda]

Hello

I'm starting to use the portage, so I am not yet familiar with its operation.

I had the following problem when doing an upgrade on my system:

Code: Select all

emerge -au world
[...]
>>> Emerging (1 of 77) sys-libs/glibc-2.9_p20081201-r3
--- Invalid atom in /etc/portage/package.keywords: sys-libs/glibc-2.11.2
 * glibc-2.9-20081201.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                                                        [ ok ]
 * glibc-2.9-ports-20081201.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                                                  [ ok ]
 * glibc-2.9-patches-7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                                                       [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                                 [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                                [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                               [ ok ]
 * CPV:  sys-libs/glibc-2.9_p20081201-r3
 * REPO: gentoo
 * USE:  amd64 elibc_glibc kernel_linux multilib nls userland_GNU
--- Invalid atom in /etc/portage/package.keywords: sys-libs/glibc-2.11.2
 * Sanity check to keep you from breaking your system:
 *  Downgrading glibc is not supported and a sure way to destruction
 * ERROR: sys-libs/glibc-2.9_p20081201-r3 failed:
 *   aborting to save your system
 *
 * Call stack:
 *                       ebuild.sh, line  48:  Called pkg_setup
 *   glibc-2.9_p20081201-r3.ebuild, line 180:  Called eblit-run 'pkg_setup'
 *   glibc-2.9_p20081201-r3.ebuild, line 166:  Called eblit-glibc-pkg_setup
 *                 pkg_setup.eblit, line  12:  Called die
 * The specific snippet of code:
 *                      die "aborting to save your system"
 *
 * If you need support, post the output of 'emerge --info =sys-libs/glibc-2.9_p20081201-r3',
 * the complete build log and the output of 'emerge -pqv =sys-libs/glibc-2.9_p20081201-r3'.
 * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.9_p20081201-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.9_p20081201-r3/temp/die.env'.
 * S: '/var/tmp/portage/sys-libs/glibc-2.9_p20081201-r3/work/glibc-2.9-20081201'

>>> Failed to emerge sys-libs/glibc-2.9_p20081201-r3, Log file:

>>>  '/var/tmp/portage/sys-libs/glibc-2.9_p20081201-r3/temp/build.log'



I tried several possible solutions but nothing work.
how can I solve?

[DHalens]

Code: Select all

*  Downgrading glibc is not supported and a sure way to destruction
* ERROR: sys-libs/glibc-2.9_p20081201-r3 failed:
*   aborting to save your system

[wolfden]

ehehe, it's masked, remove it from the package.mask file

[Thev00d00]

Code: Select all

* Sanity check to keep you from breaking your system:
*  Downgrading glibc is not supported and a sure way to destruction

[DontPanic]

Portage can be tricky.

You need to see if you can figure out why portage thinks it needs to downgrade glibc.

The latest stable version of glibc is sys-libs/glibc-2.11.2, so I can't figure out why based on what you've supplied it would want to downgrade.

Perhaps run "emerge -Nuadv @world". Or simplify the number of packages you are looking at by running "emerge -uadv @system" first.

(Note: There's not much difference, if any between "world" and "@world")

[wolfden]

it's masked by default in Sabayon config files, we went through this on the dev ML also

[LastPanda]

it's masked by default in Sabayon config files, we went through this on the dev ML also

Yes, this worked! thank you