Problem with emerge, glibc - question

[beli0135]

I tried to update system with emerge, did that once good, but now it gives me error, as one library cannot compile
Emerge tries to install glibc-2.9_p20081201-r3, and Sulfur reports that I have glibc-2.12 already.
Tried to skip this with emerge, but it starts to fail as it needs that library.

How to solve this problem?

Code: Select all

 
* 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  56:  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'.

tried this:

Code: Select all

laptux ebeli # emerge --update world --skipfirst
Calculating dependencies... done!
 * One or more packages are either masked or have missing dependencies:
 *
 *   >=x11-libs/qt-multimedia-4.6.0:4 pulled in by:
 *     (app-cdr/k3b-2.0.1::gentoo, installed)
 *
 *   >=dev-libs/klibc-1.5 pulled in by:
 *     (media-gfx/splashutils-1.5.4.3-r3::gentoo, ebuild scheduled for merge)
 *
 * The resume list contains packages that are either masked or have
 * unsatisfied dependencies. Please restart/continue the operation
 * manually, or use --skipfirst to skip the first package in the list and
 * any other packages that may be masked or have missing dependencies.

[albfneto]

with new packages, only glibc 11 or 12 works, the older, not.
If glibc is downgraded, the system may breakdown!

if you dont want to use the glibc from entropy, you need to update your portage, since it is old.

Code: Select all

emerge --sync
emerge portage
layman -S
emerge -s glibc (you will see the last version)
emerge -av  =sys-libs/glibc-2.12.1-r1


in this site, you may see that the last version or Portage have the new glibc:

http://gpo.zugaina.org/sys-libs/glibc

however,update all the system in Sabayon, only using portage, is not so easy in "normal" conditions. Even more difficult, when old portage is used, or client.conf not edited.

[wolfden]

check the /etc/portage/package.mask

It was masked, you'll have to remove it from that file to upgrade it.

Code: Select all

#Joost Ruis: Tagged for Sabayon 6
dev-lang/python:3.1
>sys-devel/binutils-2.20
>sys-libs/glibc-2.10.1

[beli0135]

Seems that version of glibc available is lower then I have

Code: Select all

sys-libs/glibc
      Latest version available: 2.9_p20081201-r3
      Latest version installed: 2.11.2
      Size of files: 16,625 kB
      Homepage:      http://www.gnu.org/software/libc/libc.html
      Description:   GNU libc6 (also called glibc2) C library
      License:       LGPL-2


I have emerged latest version of portage, did layman -S and emerge -s glibc shows above.

However, I unmasked glibc as you told me here, so emerge started to update...

Thanks.. If I run into more prolems, will scream

[beli0135]

Well, stopped again..
but different thing

Code: Select all

>>>  '/var/tmp/portage/dev-libs/klibc-1.5.15-r1/temp/build.log'

 * Messages for package sys-apps/busybox-1.17.1-r1:

 * Could not locate user configfile, so we will save a default one
 * Your configuration for sys-apps/busybox-1.17.1-r1 has been saved in
 * /etc/portage/savedconfig/sys-apps/busybox-1.17.1-r1 for your editing pleasure.
 * You can edit these files by hand and remerge this package with
 * USE=savedconfig to customise the configuration.
 * You can rename this file/directory to one of the following for
 * its configuration to apply to multiple versions:
 * ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
 * [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]

 * Messages for package dev-libs/klibc-1.5.15-r1:

 * ERROR: dev-libs/klibc-1.5.15-r1 failed:
 *   No defconfig
 *
 * Call stack:
 *     ebuild.sh, line  56:  Called src_compile
 *   environment, line 2426:  Called die
 * The specific snippet of code:
 *       emake ${defconfig} CC="${CC}" HOSTCC="${HOSTCC}" || die "No defconfig";
 *
 * If you need support, post the output of 'emerge --info =dev-libs/klibc-1.5.15-r1',
 * the complete build log and the output of 'emerge -pqv =dev-libs/klibc-1.5.15-r1'.
 * The complete build log is located at '/var/tmp/portage/dev-libs/klibc-1.5.15-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/klibc-1.5.15-r1/temp/environment'.
 * S: '/var/tmp/portage/dev-libs/klibc-1.5.15-r1/work/klibc-1.5.15'

 * Regenerating GNU info directory index...
 * Processed 152 info files.

 * IMPORTANT: 1 config files in '/etc' need updating.
 * See the CONFIGURATION FILES section of the emerge
 * man page to learn how to update config files.


what do I do now?

[joost]

//offtopic.

On your blog you wrote that Entropy (the GUI --> Sulfur) is slow, and I agree.
But to take that arguement to use portage is weird. The command line alternative is "equo" why don't you just use that instead off breaking your system? You are aware off this right?

[beli0135]

Well... let me explain a bit.

Sulfur is slow as application, not how he fetches and installs things. I tried equo. Its fine, its really fine and I intent to use it as my primary install tool in most of the cases.
Portage, I will use when I need/want something compiled and installed, with my CFLAGS.

However, equo gave me 8 updates (packages).
Emerge gives me 140 to be updated.

Now... or those two does not communicate well, or equo is reffering to "sabayon team wants you to update only this".

So, to be honest, I am confused in which tool to use for system updates. At my opinion, those two should give me same things, but equo as binary based, and portage as prefering source.

[wolfden]

Entropy isn't going to be 100% in sync with portage. You have to decide if you want a binary system or a source system. Entropy just can't go bumping everything and anything as it can cause major trouble and if you aren't an experienced portage user and use portage on entropy, you will have issues. There is a reason why certain packages aren't bumped and what not.

This is why we encourage users to pick a package manager and stick with it for 99% of stuff. We have a wiki page on mixing portage and entropy, but it should be kept to a minimal.

Your error message tells you exactly what to do btw.

[beli0135]

Well, I am not expirienced with portage at all, but I like it.
Will use your advice and stick to equo for now. Thanks.

[wolfden]

If you are interested in portage, fire up a VirtualBox and grab yourself a core cd spinbase and build it up with portage. Our wiki has portage guide to help learn it. You need to dig into the config files and build it to what you want. It's a great thing to learn, just not on a productive system as you will probably break it several times learning like most new people do to portage. It took me 3 tries to get my first gentoo install from stage3. The 3rd time I used the documentation, amazing how that works.

Or grab a stage 3 gentoo tar ball and chroot in to build up in a VirtualBox. The gentoo documentation on that is excellent, will also work for our core cd. It will take time to learn tho, months actually. Once you understand portage, you'll understand the entropy process better also, like why entropy and portage don't run 100% with updates and the big job entropy team has making sure something doesn't get through that will break your system.