e2fsprogs, com_err, and ss blockers

[d2_racing]

I tought that the Expat Hell was something....now this one.

I have a Stable x86 box and a AMD64 box, both have this problem.

For my concen, I choice this to protect my box :

Code: Select all

# cat /etc/portage/package.mask
>=sys-fs/e2fsprogs-1.41
>=sys-libs/e2fsprogs-libs-1.41.2
>=app-crypt/mit-krb5-1.6.3-r4

[d2_racing]

By the way, why not make a special warning like for Udev, a blinking red spot that says that removing the package will break your installation.

[RazielFMX]

I tought that the Expat Hell was something....now this one.

I have a Stable x86 box and a AMD64 box, both have this problem.

For my concen, I choice this to protect my box :

Code: Select all

# cat /etc/portage/package.mask
>=sys-fs/e2fsprogs-1.41
>=sys-libs/e2fsprogs-libs-1.41.2
>=app-crypt/mit-krb5-1.6.3-r4

I like this approach and did the same until this is all sorted out. Thanks for the tip.

[d2_racing]

No problem, by the way, I'm not flaming anyone here, I just want to make sure that a common user will not crash his box like with the Expat Hell last year.

[anton_kg]

Wait for the bug https://bugs.gentoo.org/show_bug.cgi?id=241670 stabilization or make it "stable" yourself:

Code: Select all

echo "=app-crypt/mit-krb5-1.6.3-r4" >> /etc/portage/package.keywords
emerge -DNuf system
emerge -C ss com_err e2fsprogs e2fsprogs-libs

emerge -DNupv system
[ebuild  N    ] sys-libs/e2fsprogs-libs-1.41.2
[ebuild     U ] app-crypt/mit-krb5-1.6.3-r4 [1.6.3-r1]
[ebuild  N    ] sys-fs/e2fsprogs-1.41.2

[honeymak]

emerge blockage has an end-user level issue
at the back, it means system stability by --oneshot

that option helps solving emerge blockage
but other apps from time to time compile with com_err or ss may get broken mysteriously

hm~~~

[anton_kg]

but other apps from time to time compile with com_err or ss may get broken mysteriously

I guess it's time to move on and fix such cases one by one.
btw, don't forget run "revdep-rebuild" as usual.

[honeymak]

actually i saw files in e2fsprogs + e2fsprogs-libs can replace com_err + ss
maybe some maintainers want to separate them for versioning? or pkg-ing?
wget works again after that......i download e2fsprogs thing by my last firefox session......juz saved my life

i just unmerge com_err + ss
then emerge e2fsprogs + e2fsprogs-libs
and then emerge update other pkg manually


it works temporarily........unless next time has a big hit on portage....
wait for ur fix >.^

[GungHo]

Hi,

today I broke my box by doing a (symbollically spoken) "eix-sync && emerge -u -deep world"

I got

Code: Select all

Calculating world dependencies... done!
[ebuild     U ] sys-apps/findutils-4.4.0 [4.3.13] 
[ebuild     U ] gnome-base/libbonobo-2.24.0 [2.22.0] 
[ebuild     U ] media-libs/libtheora-1.0_beta3-r1 [1.0_beta2-r1] 
[ebuild     U ] sys-fs/e2fsprogs-1.41.2 [1.40.9] 
[ebuild  N    ] sys-libs/e2fsprogs-libs-1.41.2  USE="nls" 
[ebuild     U ] app-crypt/mit-krb5-1.6.3-r4 [1.6.3-r1] 
[blocks B     ] sys-libs/ss (is blocking sys-libs/e2fsprogs-libs-1.41.2)
[blocks B     ] sys-libs/com_err (is blocking sys-libs/e2fsprogs-libs-1.41.2)
[blocks B     ] <sys-fs/e2fsprogs-1.41 (is blocking
sys-libs/e2fsprogs-libs-1.41.2)
[blocks B     ] sys-libs/e2fsprogs-libs (is blocking sys-libs/ss-1.40.9,
sys-libs/com_err-1.40.9)

and unmerged the blockers, of course not being aware that this breaks wget, as wget depends on libcom_err.so.2

Code: Select all

# ldd /usr/bin/wget 
        linux-vdso.so.1 =>  (0x00007fff766f0000)
        libssl.so.0.9.8 => /usr/lib64/libssl.so.0.9.8 (0x00007f9f6e23e000)
        libcrypto.so.0.9.8 => /usr/lib64/libcrypto.so.0.9.8 (0x00007f9f6dec1000)
        libdl.so.2 => /lib/libdl.so.2 (0x00007f9f6dcbd000)
        librt.so.1 => /lib/librt.so.1 (0x00007f9f6dab4000)
        libc.so.6 => /lib/libc.so.6 (0x00007f9f6d775000)
        libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00007f9f6d54a000)
        libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00007f9f6d2b3000)
        libcom_err.so.2 => /lib/libcom_err.so.2 (0x00007f9f6d0af000)
        libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00007f9f6ce89000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x00007f9f6cc75000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f9f6e492000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00007f9f6ca5a000)
        libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007f9f6c852000)

After realizing what happend I was aware of being in serious trouble now

I tried to manually re-emerge e2fsprogs-1.40.9.tar.gz, in the hope to get back to the state before unmerging the three packages above. This didn't work in the first step, so I tried to re-emerge sys-libs/ss-1.40.9 and then sys-libs/com_err-1.40.9, but also no luck. But all this tries showed that e2fsprogs-1.40.9.tar.gz was not available on my box, and the broken wget was not able to d'load it:

Code: Select all

# emerge =sys-libs/com_err-1.40.9
Calculating dependencies... done!
>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) sys-libs/com_err-1.40.9 to /
>>> Downloading
'ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/distfiles/e2fsprogs-1.40.9.tar.gz'
wget: error while loading shared libraries: libcom_err.so.2: cannot open
shared object file: No such file or directory
>>> Downloading
'http://gentoo.mneisen.org/distfiles/e2fsprogs-1.40.9.tar.gz'
wget: error while loading shared libraries: libcom_err.so.2: cannot open
shared object file: No such file or directory

Then I tried to d'load the missing package e2fsprogs-1.40.9.tar.gz, but directly in the browser, into my distfiles Directoy, to get able to do the emerge of com_err-1.40.9, simply by copying and pasting the url shown in the errormessage into the adressfield of Firefox

This time I was lucky, was able to re-emerge the old e2fsprogs and the other 2 unmerged packages. Now the missing shared lib was in place again, and wget again worked. Yippiee

After reflecting the situation I came to the idea to do the same prefetching of all packages which could be of worth solving the situation before unmerging the blockers., like naib has suggested in this thread before, but not all packages of the world (which might by overkill and would let explode my disk), but only the packages for building e2fsprogs-1.41.2. So I did an

Code: Select all

# emerge -f =e2fsprogs-1.41.2

unmerged again the blockers, emerged e2fsprogs-1.41.2, re-emerged wget and that was it .

I now was able to do my emerge -u --deep world && revdep-rebuild, without other hassle.

Such a situation should not happen, that portage will be broken indirectly, and one has nearly a chance to avoid the situation. It could not be handled to check all integral parts of portage before unmerging a paket which has nothing to do with portage :Maybe all parts portage depends on should be statically linked ! Portage is vital for a Gentoo based system !


BTW, I also reflected about other FETCHCOMMANDs in /etc/make.conf, preferably without wget (to avoid this whole hassle), but the only one which came into my mind was working with curl, which also has libcom_err.so.2 in it's dependencies.
Prozilla, which is sometimes seen in the examples of make.conf, does not exist anymore, as lukemftp also (at least in portage).

So my question, who uses another tool than wget or curl ?

[d2_racing]

it's actually :

Code: Select all

# emerge -f =e2fsprogs-1.41.2

[d2_racing]

Code: Select all

echo "=app-crypt/mit-krb5-1.6.3-r4" >> /etc/portage/package.keywords
emerge -DNuf system
emerge -C ss com_err e2fsprogs e2fsprogs-libs

emerge -DNupv system
[ebuild  N    ] sys-libs/e2fsprogs-libs-1.41.2
[ebuild     U ] app-crypt/mit-krb5-1.6.3-r4 [1.6.3-r1]
[ebuild  N    ] sys-fs/e2fsprogs-1.41.2

Why fetching the whole system ?

[jeanfrancis]

Why fetching the whole system ?

Just because it's a smaller command than fetching only the precise packages . The whole system packages aren't fetched, only those who are to be updated. It avoids to fail if some packages are to be updated between the removal of com_err and the installation of e2fsprogs-libs (if such a situation exists).

[sargek]

I had the same issue last night after I sync'd but just unmerged, com_err, ss and e2fsprogs then ran emerge -vuD world and all was well. It does appear as if com_err and ss go away. The system boots fine and e2fsprogs does it's thing. Blocks used to frustrate me but then I just started yanking the offending package(s) and things clear themselves up. Maybe I am just lucky....

[d2_racing]

Why fetching the whole system ?

Just because it's a smaller command than fetching only the precise packages . The whole system packages aren't fetched, only those who are to be updated. It avoids to fail if some packages are to be updated between the removal of com_err and the installation of e2fsprogs-libs (if such a situation exists).

Yes, since it's part of the toolchain(system), I understand now

[HMC]

Hmmm...

Fresh x86 i686-stage-3 2008.0 install

Emerged gentoo-sources, grub and gentoolkit... nothing else.

No USE flags have been set... default profile... blah,blah... there is nothing to tell about this install - it has been done by the book except that it is currently lacking the system tools as outlined in the guide


emerge --sync then emerge world -NuDpv and get EXACTLY the same blockers.

EDIT same blockers as the OP almost:

[blocks B ] sys-libs/ss (is blocking sys-libs/e2fsprogs-libs-1.41.2)
[blocks B ] <sys-fs/e2fsprogs-1.41 (is blocking sys-libs/e2fsprogs-libs-1.41.2)
[blocks B ] sys-libs/com_err (is blocking sys-libs/e2fsprogs-libs-1.41.2)

[Joseph_sys]

Hi ,

I just had to go through this a second time. Portage tree now handles this a bit better than a few weeks back.

Code: Select all

emerge --sync

just to be covered:

Code: Select all

quickpkg ss com_err e2fsprogs e2fsprogs-libs

then

Code: Select all

emerge -f ss com_err e2fsprogs e2fsprogs-libs
emerge -C ss com_err e2fsprogs
emerge -1  e2fsprogs 

It didn't work for me, after emerge -1 e2fsprogs I got the following error:

Code: Select all

make[1]: Entering directory `/var/tmp/portage/sys-fs/e2fsprogs-1.41.2/work/e2fsprogs-1.41.2/lib/ext2fs'
        SUBST ext2_err.et
        COMPILE_ET ext2_err.et
make[1]: compile_et: Command not found
make[1]: *** [ext2_err.h] Error 127
make[1]: Leaving directory `/var/tmp/portage/sys-fs/e2fsprogs-1.41.2/work/e2fsprogs-1.41.2/lib/ext2fs'
make: *** [subs] Error 2
 *
 * ERROR: sys-fs/e2fsprogs-1.41.2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2394:  Called die
 * The specific snippet of code:
 *       emake COMPILE_ET=compile_et MK_CMDS=mk_cmds || die;
 *  The die message:
 *   (no error message)
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/log/portage/sys-fs:e2fsprogs-1.41.2:20081029-154637.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/e2fsprogs-1.41.2/temp/environment'.
 *
/usr/sbin/sendmail: error while loading shared libraries: libcom_err.so.2: cannot open shared object file: No such file or directory

Any suggestion how to proceed?

[travisau]

I tried to be safe while updating these packages. I emerge fetched com_err, ss, e2fsprogs, e2fsprogs-libs mit-krb5 then quickpkg'd the progs also. I then unmerged com_err and ss and emerged e2fsprogs (1.41.2) and mit-krb5 (1.6.3-r4). Now when I reboot my system it tell me that /dev/sda3 (my /) is clean but "Root filesystem could not be mounted read/write ".

Any ideas what caused this or how to fix it without reverting to the quickpkg'd versions?


EDIT: interestingly I entered the busybox shell and remounted root as RE with "mount -o remount,rw /dev/sda3 /" and the system booted the rest of the way up successfully. Appears its just not about to remount RW during the boot process now for some reason?

[Koboneil]

I have got the same blockers today. To fix it I did (actually, a friend told me to do, thanks LA_GLOBULE) :

Code: Select all

emerge -C ss com_err
emerge -C e2fsprogs
revdep-rebuild

revdep-rebuild emerges about 10 packages including e2fprogs

then

Code: Select all

emerge -uDNav world

and now everything works fine.

[barikman]

For me the solution was simply to unmerge ss and com_err and then download e2fsprogs-libs manually (with a browser), copy the source file to /usr/portage/distfiles and then merge it. You have to do the download yourself as unmerging com_err breaks wget temporarily (at least I think that was the specific problem - I'm writing this a little after the event).

The reason for the above is that one or more shared libraries previously provided by the com_err package are now provided by e2fsprogs-libs. I think a previous poster mentioned that?

Anyway, then do a quick revdep-rebuild and all will be well. I didn't need to mess with the mit-krb5 (Kerberos) ebuild version at all, despite the experience of some of the other posters.

Edit : doing the actions that the previous poster described didn't work for me. If it works for you though then it's certainly a more elegant solution!

Cheers

Phil

[jeanfrancis]

wget getting broken is the reason why a lot of folks here suggest fetching the packages before unmerging com_err.

[GungHo]

it's actually :

Code: Select all

# emerge -f =e2fsprogs-1.41.2

uups, small mistake

[HMC]

Okay... got it fixed without any dramas, but I have to ask the question "why?"

[barikman]

wget getting broken is the reason why a lot of folks here suggest fetching the packages before unmerging com_err.

Ah yes, indeed. Sound suggestion. Shame I forgot to follow it!

[jeanfrancis]

wget getting broken is the reason why a lot of folks here suggest fetching the packages before unmerging com_err.

Ah yes, indeed. Sound suggestion. Shame I forgot to follow it!

Hehe. I got this problem months ago (~arch) and my browser didn't want to download anything, so I had to use a LiveCD to download the files, then chroot and update... Fetching is more secure hehe

[HMC]

Hehe. I got this problem months ago (~arch) and my browser didn't want to download anything, so I had to use a LiveCD to download the files, then chroot and update... Fetching is more secure hehe

I run emerge --sync plus emerge world -uDf as a daily cron job and clean out old packages from distfiles less frequently for occasions such as these. I learned that one the hard way.