Quick fix for e2fsprogs, com_err, and ss blockers

[chrisstankevitz]

a) the fix is obvious

Yes. Especially given a current version of sys-apps/portage, including versions which have been available since before these blocks were put in place, even before that the fix was not difficult.

Why not edit the first post of this sticky thread to note that the problem can be fixed by simply updating portage? Poor newcomers have to read through six pages of this just to realize the problem is fixed.

Chris

[desultory]

What about /usr/portage/UPDATING (as in FreeBSD) ?

That would seem to be covered by GLEP [glep=0042]42[/glep] news items.

Why not edit the first post of this sticky thread to note that the problem can be fixed by simply updating portage? Poor newcomers have to read through six pages of this just to realize the problem is fixed.

Anyone first encountering the problem now would have at least a pending update to such a version of Portage, such an update would logically be the first applied so they should largely avoid the problem. Even so, such a note has been left.

[Tortue]

On a fresh gentoo install, I first upgraded Portage. It did not work (e2fsprogs still blocking).

I then tried the instructions of the very first post. It didn't work the first time, but worked on the second.

Everything is now OK and I can continue installing programs.

Thanks very much

J-M

[chrisstankevitz]

Anyone first encountering the problem now would have at least a pending update to such a version of Portage, such an update would logically be the first applied so they should largely avoid the problem. Even so, such a note has been left.

In my opinion, all sticky threads should, when possible, have their first post updated if/when the information becomes obsolete.
1. Prevent people from attempting an obsolete fix
2. Keep people from reading 7 pages of a sticky thread to find out how to fix a problem
3. Discourage admins from leaving threads sticky indefinitely

For example, this thread. Apparently the problem has been solved by the portage devs, so why keep this post sticky? There are too many sticky threads in the world today!

Thanks,

Chris

[desultory]

In my opinion, all sticky threads should, when possible, have their first post updated if/when the information becomes obsolete.
1. Prevent people from attempting an obsolete fix
2. Keep people from reading 7 pages of a sticky thread to find out how to fix a problem
3. Discourage admins from leaving threads sticky indefinitely

To address those points in order, as they pertain to this topic, the fix still works, fixing it manually does not break anything, this topic is expected to lose any stickiness well before the general entropic failure of the universe though no specific date has been set. In general though, those principles are essentially sound.

For example, this thread. Apparently the problem has been solved by the portage devs, so why keep this post sticky?

In part because it appears as though that does [post=5361020]not[/post] always succeed, as such there is still more value in keeping this topic sticky than there is in it not being sticky.

There are too many sticky threads in the world today!

We try to manage their populations, it is a delicate operation as their population tends to destabilize at both high and low population thresholds.

[Solour]

Hi,

I got a problem.
I had the USE flags kerberos krb5 krb4 globally in my make.conf
I had app-crypt/mit-krb5-1.6.3-r1 installed.

I executed the fix in the first post but I get the following build error.

Code: Select all

 *
 * ERROR: sys-fs/e2fsprogs-1.41.3 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2398:  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/tmp/portage/sys-fs/e2fsprogs-1.41.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/e2fsprogs-1.41.3/temp/environment'.
 *

I have tried to restore my old system by reinstalling the exact same versions I just removed
emerge =sys-fs/e2fsprogs-1.40.9 =sys-libs/com_err-1.40.9 =sys-libs/ss-1.40.9
however I get the following build error:

Code: Select all

 make[2]: Entering directory `/var/tmp/portage/sys-fs/e2fsprogs-1.40.9/work/e2fsprogs-1.40.9/e2fsck'
        CC dict.c
        COMPILE_ET prof_err.et
        CC unix.c
unix.c: In function ‘PRS’:
unix.c:614: error: ‘et_ext2_error_table’ undeclared (first use in this function)
unix.c:614: error: (Each undeclared identifier is reported only once
unix.c:614: error: for each function it appears in.)
unix.c:615: error: ‘et_prof_error_table’ undeclared (first use in this function)
unix.c: In function ‘main’:
unix.c:1400: error: ‘et_ext2_error_table’ undeclared (first use in this function)
unix.c:1401: error: ‘et_prof_error_table’ undeclared (first use in this function)
make[2]: *** [unix.o] Error 1
make[2]: Leaving directory `/var/tmp/portage/sys-fs/e2fsprogs-1.40.9/work/e2fsprogs-1.40.9/e2fsck'
make[1]: *** [all-progs-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/sys-fs/e2fsprogs-1.40.9/work/e2fsprogs-1.40.9'
make: *** [all] Error 2
 *
 * ERROR: sys-fs/e2fsprogs-1.40.9 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2373:  Called die
 * The specific snippet of code:
 *       emake -j1 COMPILE_ET=compile_et || 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/tmp/portage/sys-fs/e2fsprogs-1.40.9/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/e2fsprogs-1.40.9/temp/environment'.
 *

The other two packages ss and com_err can be emerged though.

Then I removed kerberos from my system and removed the useflags from the make.conf but that did not help either.

How can I restore my system?

Thanks a lot!!

ps: my emerge --info

Code: Select all

Portage 2.1.6.4 (default/linux/x86/2008.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.26-gentoo-r4 i686)
=================================================================
System uname: Linux-2.6.26-gentoo-r4-i686-Intel-R-_Core-TM-2_Duo_CPU_T9300_@_2.50GHz-with-glibc2.0
Timestamp of tree: Mon, 05 Jan 2009 17:45:01 +0000
app-shells/bash:     3.2_p39
dev-java/java-config: 1.3.7-r1, 2.1.6-r1
dev-lang/python:     2.4.4-r13, 2.5.2-r7
dev-python/pycrypto: 2.0.1-r6
dev-util/cmake:      2.4.6-r1
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.13, 2.63
sys-devel/automake:  1.7.9-r1, 1.9.6-r2, 1.10.2
sys-devel/binutils:  2.18-r3
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.26
virtual/os-headers:  2.6.27-r2
ACCEPT_KEYWORDS="x86"
CBUILD="i486-pc-linux-gnu"
CFLAGS="-O2 -mtune=i686 -pipe"
CHOST="i486-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d"
CXXFLAGS="-O2 -mtune=i686 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache collision-protect distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="ftp://ftp.tu-clausthal.de/pub/linux/gentoo ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo http://linux.rz.ruhr-uni-bochum.de/download/genoo-mirror/ ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo"
LANG="en_GB.UTF-8"
LDFLAGS="-Wl,-O1"
LINGUAS="de en"
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="X a52 aac accessibility acl afs alsa arts audiofile bash-completion berkdb bzip2 cdr cli cracklib crypt cups dbus dri dvd esd ffmpeg firefox flash fortran gdbm gif gpm gtk2 iconv ipv6 isdnlog java javascript jpeg jpeg2k kde kpathsea latex mad midi mozilla mp2 mp3 mudflap mule ncurses nls nptl nptlonly nsplugin ogg oggvorbis opengl openmp openssl oss pam pcre pdf perl png ppds pppd python qt qt3 qt4 readline reflection session spl ssl static symlink sysfs tcpd tetex tiff unicode usb utempter vorbis win32codecs x86 xinerama xorg xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="mouse keyboard synaptics evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de en" USERLAND="GNU" VIDEO_CARDS="nvidia vesa"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY

[Solour]

I have also tried to unmask e2fsprogs ~x86 in my package.keywords but

[ebuild N ] sys-fs/e2fsprogs-1.41.3-r1 USE="nls" 0 kB

fails with the same error

Code: Select all

 *
 * ERROR: sys-fs/e2fsprogs-1.41.3-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2398:  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/tmp/portage/sys-fs/e2fsprogs-1.41.3-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/e2fsprogs-1.41.3-r1/temp/environment'.
 *

I found this bug http://bugs.gentoo.org/210232 but I can't get any useful information out of it..

Using this version I do have the compile.et file and I can generate that file ext2_err.h without any failures.

[richard.scott]

How come your using that version of e2fsprogs?

Mine is only 1.41.2?

[Solour]

Good point.
I had it blocked in package.mask because kerberos did not work with it.

Removing this and emerging this version directly does not work though.
Same error as above .

I guess that I have tried all available versions in portage now?
Could I post any more information, like other installed packages?

Still. Thanks a lot for the help!

[richard.scott]

This problem isn't linked to my original thread..... but perhaps you could try masking anything above these:

Code: Select all

# equery list e2fsprogs
[ Searching for package 'e2fsprogs' in all categories among: ]
 * installed packages
[I--] [  ] sys-fs/e2fsprogs-1.41.2 (0)
[I--] [  ] sys-libs/e2fsprogs-libs-1.41.2 (0)

To see if you can actually install them as they work on my system.
Make sure you "emerge --sync" before hand and perhaps update portage too if one is available.

[donjames]

Hi,

I am working on a new install of Gentoo.

I updated portage to the latest version and now I have no blocks with:

Code: Select all

emerge -uDv world

I just thought someone would like to know.

Sincerely,

Don James
Henderson, Texas USA

[richard.scott]

I updated portage to the latest version and now I have no blocks with:

That's greate news. Looks like the latest portage is up to the task of dealing with this one

[Solour]

Just before I unmerged the mentioned packages I performed
emerge --sync
and
update portage
successfully.

My portage version is currently:
app-portage/portage-utils-0.1.29
sys-apps/portage-2.1.6.4

which is according to http://gentoo-portage.com/sys-apps/portage the most current (not hard masked) version

In my case the blockings were present, thus portage is not entirely able to deal with this issue.

I masked these versions in package.mask and tried to emerge them.
The libs were successfully installed but e2fsprogs itself produced the same error again.
Actually on my other laptop I have version 1.40.9 installed.

Should I try to reemerge some other package?
Could something be broken due to the unmerge?

Any help is really appreciated since my system remains quite unusable...

[richard.scott]

On my system e2fsprogs-1.41.2 is the latest stable package.
Are you trying to install the unstable version?

[Solour]

I have tried to install the following versions (all producing (almost) the same error)
1.40.9
1.41.2
1.41.3
1.41.3-r1

So I have tried to reinstall 1.40.9 because it worked prior to its unmerging
I would be fine with any recent version of e2fsprogs compiling..

So yes. I have also tried unstable versions.

[Solour]

finally. after hours...

equery b /usr/local/bin/compile_et
and then (since it did not belong to something)
rm /usr/local/bin/compile_et

afterwards I could install 1.41.2

[richard.scott]

The one I have is:

Code: Select all

# equery b compile_et
[ Searching for file(s) compile_et in *... ]
sys-libs/e2fsprogs-libs-1.41.2 (/usr/bin/compile_et)

I wonder why it got placed in /usr/local/bin?
Well done for finding it

[jorisbeld]

Followed the four lines, as adviced in the first post, but emerge e2fsprogs does fail.

Somebody an idea how to fix the following error:

Code: Select all

>>> Failed to emerge sys-libs/e2fsprogs-libs-1.41.3-r1, Log file:

>>>  '/var/tmp/portage/sys-libs/e2fsprogs-libs-1.41.3-r1/temp/build.log'

 * Messages for package sys-libs/e2fsprogs-libs-1.41.3-r1:

 *
 * ERROR: sys-libs/e2fsprogs-libs-1.41.3-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2340:  Called die
 * The specific snippet of code:
 *       emake STRIP=/bin/true || die
 *  The die message:
 *   (no error message)

[tryn]

Followed the four lines, as adviced in the first post, but emerge e2fsprogs does fail.

Somebody an idea how to fix the following error:

There were 5 lines in the first post did you miss one of them??

Code: Select all

# echo "<=app-crypt/mit-krb5-1.6.3-r2" >> /etc/portage/package.keywords
# emerge --sync
# emerge -f e2fsprogs e2fsprogs-libs
# emerge --unmerge ss com_err e2fsprogs
# emerge e2fsprogs e2fsprogs-libs

[richard.scott]

Followed the four lines, as adviced in the first post, but emerge e2fsprogs does fail.

Somebody an idea how to fix the following error:

Code: Select all

>>> Failed to emerge sys-libs/e2fsprogs-libs-1.41.3-r1, Log file:

>>>  '/var/tmp/portage/sys-libs/e2fsprogs-libs-1.41.3-r1/temp/build.log'

 * Messages for package sys-libs/e2fsprogs-libs-1.41.3-r1:

 *
 * ERROR: sys-libs/e2fsprogs-libs-1.41.3-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2340:  Called die
 * The specific snippet of code:
 *       emake STRIP=/bin/true || die
 *  The die message:
 *   (no error message)

What kernel are you running? There are issues with some of the hardened-source kernels what will stop emerges with a segfault.

AFAIK hardened-sources-2.6.25-r13 is the latest known good kernel.

Also, don't forget to upgrade portage first as this helps too.

Rich

[jorisbeld]

Running Gentoo 2.6.20-gentoo-r7. Is that problematic in this case?

I did update portage first and emerge --sync, before following the instructions above.

Hmmm, the strange thing is that i also cannot emerge cups, also giving an emake error, suggesting that something more fundamental is wrong.

Anyway, thanks for the suggestions.

Best,
Joris

[richard.scott]

Running Gentoo 2.6.20-gentoo-r7. Is that problematic in this case?

Nope, as far as I know its just the hardened-sources that have issues.

[chrisstankevitz]

I recommend the mods un-stick this topic add a sticky topic for the qt conflict.

[NTwoO]

I recommend the mods un-stick this topic add a sticky topic for the qt conflict.

Then, I think the install procedure for a new system needs an update, since this block is still encountered when installing a new system. The stage3-2008.0 can not handle an

Code: Select all

emerge --sync; emerge -vuD world 

without returning with a glazed look. Until this problem is fixed in a clean install, I think the suggestion of updating the first post in the sticky is a groovy solution.

[richard.scott]

During the installation your requested to upgrade portage if one is available. This happens just after your very first "emerge --sync".
AFAIK The latest portage should handle this blocker on its own?