When I update glibc, a Python traceback and an error message from shell script appear on the screen between checking md5 and unpacking source. Reproducible: Always Steps to Reproduce: 1.have installed an older glibc which has revision (2.3.2-r10 for example) 2.emerge glibc-2.3.2-r11 Actual Results: Traceback (most recent call last): File "", line 1, in ? File "/usr/lib/portage/pym/portage.py", line 2817, in vercmp cmp2=relparse(val2[x]) File "/usr/lib/portage/pym/portage.py", line 2534, in relparse number=string.atof(myver) File "/usr/lib/python2.3/string.py", line 205, in atof return _float(s) ValueError: invalid literal for float(): r10 /usr/sbin/ebuild.sh: line 142: [: -lt: unary operator expected Expected Results: no error The problem is caused by wrong usage of portage.vercmp. The ebuild file has the following line: if [ `python -c "import portage; print int(portage.vercmp(\"${PV}\",\"$old_version\"))"` -lt 0 ]; then and $old_version contains the revision part, which must not pass to portage.vercmp. Actually, other versions of glibc ebuilds have the same problem.
Please post the output of emerge info as outlined in the Bug Reporting guidelines.
Portage 2.0.50-r9 (default-x86-1.4, gcc-3.3.3, glibc-2.3.2-r11, 2.4.25_pre7-gss-r2) ================================================================= System uname: 2.4.25_pre7-gss-r2 i586 AMD-K6(tm) 3D+ Processor Gentoo Base System version 1.5.2 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -mcpu=k6-3 -pipe" CHOST="i586-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/:/usr/share/config /var/bind:/usr/lib/mozilla/defaults/pref:/usr/X11R6/lib/X11/xkb:/opt/tomcat/conf:/usr/kde/3.1/share/config:/usr/share/texmf/tex/generic/config/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/gconf:/etc/terminfo /etc/env.d" CXXFLAGS="-O3 -mcpu=k6-3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache digest sandbox userpriv" GENTOO_MIRRORS="http://mirror.gentoo.gr.jp/ http://gentoo.oregonstate.edu/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /work/portagejp" SYNC="rsync://rsync.jp.gentoo.org/gentoo-portage/" USE="3dnow X apm arts avi berkdb cjk crypt cups doc emacs encode esd foomaticdb freewnn gcl gdbm gif gnome gpm gtk gtk2 imlib java jpeg leim libg++ libwww mad mikmod motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline ruby sdl slang spell ssl svga tcltk tcpd truetype x86 xml2 xmms xv zlib"
I have the same problem, slightly different scenario. I have glibc-2.3.3.20040420-r1 installed, and I'm trying to recompile it and get the exact same error. result: >>> emerge (1 of 1) sys-libs/glibc-2.3.3.20040420-r1 to / >>> md5 src_uri ;-) glibc-2.3.2.tar.bz2 >>> md5 src_uri ;-) glibc-linuxthreads-2.3.2.tar.bz2 >>> md5 src_uri ;-) glibc-2.3.3-branch-update-20040420.patch.bz2 Traceback (most recent call last): File "<string>", line 1, in ? File "/usr/lib/portage/pym/portage.py", line 2817, in vercmp cmp2=relparse(val2[x]) File "/usr/lib/portage/pym/portage.py", line 2534, in relparse number=string.atof(myver) File "/usr/lib/python2.3/string.py", line 205, in atof return _float(s) ValueError: invalid literal for float(): r1 /usr/sbin/ebuild.sh: line 144: [: -lt: unary operator expected emerge info: Portage 2.0.50-r9 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3.20040420-r1, 2.6.7-gentoo-r12) ================================================================= System uname: 2.6.7-gentoo-r12 i686 Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon-xp -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.ca.gentoo.org/gentoo-portage" USE="3dnow X aalib alsa apm audiofile avi berkdb cdparanoia cdr clamav crypt curl dillo directfb divx4linux doc dvd dvdr dvdread encode escreen esd fbcon flac flash gd gdbm ggi gif gnome gphoto2 gpm gtk gtk2 gtkhtml icq imagemagick imap imlib jack jpeg ldap libg++ libwww mad mcal memlimit mikmod mmx motif mozilla mpeg msn ncurses nls oci8 odbc oggvorbis opengl pam pdflib perl png ppds python quicktime readline sdl slang speex spell sse ssl svga tcltk tcpd tiff truetype usb x86 xface xml xml2 xmms xosd xv xvid yahoo yaz zlib"
I got the same error.... Im going from glibc-2.3.2-r9 to glibc-2.3.2-r10 ..
glibc-2.3.2-r11 is not the only one with this bug.
I am getting the same behavior as starfog. Here is my emerge info Portage 2.0.50-r10 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.4. 26) ================================================================= System uname: 2.4.26 i686 AMD Athlon(tm) XP 2400+ Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon-xp -O2 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/s hare/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/ dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/c onfig/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=athlon-xp -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox userpriv usersandbox" GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo ftp://csociety-ftp.ecn.pu rdue.edu/pub/gentoo/ ftp://lug.mtu.edu/gentoo/source ftp://ftp.ndlug.nd.edu/pub/ gentoo/ ftp://gentoo.chem.wisc.edu/gentoo/ http://mirror.datapipe.net/gentoo ftp ://ftp.ucsb.edu/pub/mirrors/linux/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d apache2 apm arts avi berkdb crypt cups debug doc dvd encode esd f77 foomaticdb gcj gd gdbm gif gpm gtk gtk2 imlib java jikes jpeg libg++ libwww mad mbox mcal mikmod mmx motif mpeg mpi mysql ncurses nls oggvorbis opengl oss pam pcmcia pdflib perl plotutils png python qt quicktime readline sdl slang spell ss e ssl svga tcltk tcpd tetex tiff truetype trusted usb x86 xfs xml xml2 xmms xv z eo zlib" Here is the first bit of output from an 'emerge glibc' 0 24 % sudo emerge glibc chrisg@nenya:/home/chrisg Calculating dependencies ...done! >>> emerge (1 of 1) sys-libs/glibc-2.3.3.20040420-r1 to / >>> md5 src_uri ;-) glibc-2.3.2.tar.bz2 >>> md5 src_uri ;-) glibc-linuxthreads-2.3.2.tar.bz2 >>> md5 src_uri ;-) glibc-2.3.3-branch-update-20040420.patch.bz2 Traceback (most recent call last): File "<string>", line 1, in ? File "/usr/lib/portage/pym/portage.py", line 2815, in vercmp cmp2=relparse(val2[x]) File "/usr/lib/portage/pym/portage.py", line 2532, in relparse number=string.atof(myver) File "/usr/lib/python2.3/string.py", line 205, in atof return _float(s) ValueError: invalid literal for float(): r1 /usr/sbin/ebuild.sh: line 144: [: -lt: unary operator expected Haven't gone any futher in troubleshooting. Cheers, Chris
This should be fixed now.
> This should be fixed now. AFAIK, the code block is removed from 2.3.4.*, commented out in 2.3.3.*, but still unchanged for 2.3.2-r11 and 2.2.5-r9. So, I think it should not be said to be fixed.
*** This bug has been marked as a duplicate of 59704 ***