lines 72 and 75 in the latest portability.eclass use the '<<<' operator which is a new feature in bash 3.x. bash 2.x doesn't understand this operator and errors out, breaking emerge for all users of bash 2.x. Reproducible: Always Steps to Reproduce: 1.emerge bash 2.x 2.emerge sync to get latest portability.eclass 3.attempt to emerge anything and it will fail Actual Results: /usr/lib/portage/bin/ebuild.sh: /usr/portage/eclass/portability.eclass: line 72: syntax error near unexpected token `<<<$' /usr/lib/portage/bin/ebuild.sh: /usr/portage/eclass/portability.eclass: line 72: ` cut -d: -f9 <<<${ent}' !!! ERROR: www-client/mozilla-launcher-1.42 failed. !!! Function inherit, Line 97, Exitcode 1 !!! died sourcing /usr/portage/eclass/portability.eclass in inherit() !!! If you need support, post the topmost build error, NOT this status message.
Include your emerge info please... I'm specifically curious about the profile you're running, since people are poking about allowing/requiring for sourcing the tree, >=bash-3
we could start forcing bash-3 in profiles i think the only stable baselayout requires bash-3
Was it to fix the "pointless echo" ?
emerge info: Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.2, glibc-2.3.2-r9, 2.6.6 i686) ================================================================= System uname: 2.6.6 i686 AMD Duron(tm) Processor Gentoo Base System version 1.4.2.5 dev-lang/python: 2.2.2 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.58-r1 sys-devel/automake: 1.8.3 sys-devel/binutils: 2.14.90.0.8-r1 sys-devel/libtool: 1.4.1-r10 virtual/os-headers: 2.4.19 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-mcpu=athlon -march=athlon -O3 -pipe -mmmx -m3dnow" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb:/usr/kde/3.1/share/config: /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/gconf:/etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=athlon -march=athlon -O3 -pipe -mmmx -m3dnow" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio. org/pub/Linux/distributions/gentoo" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X acpi alsa apm arts avi berkdb bitmap-fonts cdr crypt cscope cups curl dvd eds emboss encode esd fam flac foomaticdb fortran gd gdbm gif gnome gphoto2 gpm gstreamer gtk gtk2 imagemagick imlib ipv6 jack java jpeg kde lame libg++ libwww mad mikmod mitshm mmx motif mp3 mpeg ncurses nls ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sdl slang spell ssl svga tcltk tcpd tiff truetype truetype-fonts type1-fonts vorbis x x86 xml xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
Chris when was the last time you did a " emerge world -uD " ?
I've never done that. Sounds like a lot of work fixing issues with new versions when the versions I have work fine. (Except for bash now)
I've got Bash 3.0 emerged now after overwriting my /usr/portage directory with an old snapshot 20050303. That made emerge function again so I could upgrade bash and now everything is cool. If new changes to eclasses or other portage scripts require software upgrades then a sync should not be allowed until the software upgrades are performed.
Okay sorry this slipped through my mind in the mean time. I've fixed it by using the "pointless echo"...
