31653 – Updating Portage cache of "emerge rsync" fails with traceback.

Bug 31653 - Updating Portage cache of "emerge rsync" fails with traceback.

Summary: Updating Portage cache of "emerge rsync" fails with traceback.

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All Linux

Importance:	High major (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-10-21 00:29 UTC by Thomas Preissler
Modified:	2011-10-30 22:21 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Traceback of "emerge rsync" (traceback,460 bytes, text/plain) 2003-10-21 00:29 UTC, Thomas Preissler	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Thomas Preissler 2003-10-21 00:29:20 UTC

Every "emerge rsync" (it does not depend on the mirror) fails with traceback 
while update portage cache. 

Reproducible: Always
Steps to Reproduce:
1.emerge rsync 
Actual Results:  
Updating Portage cache fails with the attached traceback 

Expected Results:  
Hm, successfull update of the Portage cache as with portage 
<portage-2.0.49-r13. 

Portage 2.0.49-r13-2 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.19) 
================================================================= 
System uname: 2.4.19 i686 AMD Duron(tm) Processor  
Gentoo Base System version 1.4.3.10 
ccache version 2.2 [enabled] 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-O2 -mcpu=i686 -pipe" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config 
/usr/kde/3/share/config /var/bind /usr/X11R6/lib/X11/xkb 
/usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ 
/usr/share/texmf/tex/platex/config/ /usr/share/config" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" 
CXXFLAGS="-O2 -mcpu=i686 -pipe" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="autoaddcvs sandbox ccache digest keepwork fixpackages" 
GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/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="x86 oss apm avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod 
mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib 
directfb gtkhtml alsa gdbm berkdb slang readline arts tetex aalib nas bonobo 
svga ggi tcltk java guile mysql X sdl gpm tcpd pam libwww ssl perl python esd 
imlib oggvorbis gnome gtk qt kde motif opengl mozilla ldap cdr scanner acpi 
activefilter curl dvb dvd evo fbcon flash gb gd gd-external imap innodb ipv6 
jikes mbox mcal memlimit pic postgres samba sasl snmp socks5 tiff xchattext 
xml"

Comment 1 Thomas Preissler 2003-10-21 00:29:50 UTC

Created attachment 19570 [details]
Traceback of "emerge rsync"

Comment 2 SpanKY gentoo-dev

2003-10-21 00:36:10 UTC

wtf is Portage 2.0.49-r13-2 ? :)

Comment 3 Thomas Preissler 2003-10-21 00:52:37 UTC

Oooops, interesting.

$ epm -qa | grep portage
portage-2.0.49-r13

$ emerge --info
Portage 2.0.49-r13-2 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.19)

$ emerge --version
Portage 2.0.49-r13-2 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.19)

I found in /usr/bin/emerge
VERSION_RELEASE=2

Comment 4 Marius Mauch (RETIRED) gentoo-dev

2003-10-21 10:49:12 UTC

Looks like a broken install, which python version do you have ?
See bug 31198 about the -r13-2 thing.

Comment 5 Thomas Preissler 2003-10-21 12:45:35 UTC

python-2.2.3-r1

I just remerged the actual portage portage-2.0.49-r13 (-2), and now - everything
works fine.

Wow, but I do not know, why.

Comment 6 Marius Mauch (RETIRED) gentoo-dev

2003-11-15 20:02:46 UTC

seems to be fixed.