Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 34691 - portage 2.0.49-r18 breaks itself (xpak module gone)
Summary: portage 2.0.49-r18 breaks itself (xpak module gone)
Status: RESOLVED INVALID
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: x86 Linux
: High critical
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-29 05:18 UTC by Manfred Stienstra
Modified: 2011-10-30 22:18 UTC (History)
1 user (show)

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

Attachments
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 Manfred Stienstra 2003-11-29 05:18:06 UTC 
After emerging portage-2.0.49-r18 I can't emerge anything because of the
following error:

Traceback (most recent call last):
  File "/usr/lib/portage/bin/xpak", line 6, in ?
    import xpak
ImportError: No module named xpak
tbz2tool: inf.xpak doesn't exist


Reproducible: Always
Steps to Reproduce:




Portage 2.0.49-r18 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r1, 2.4.22)
=================================================================
System uname: 2.4.22 i686 AMD Athlon(tm) XP 3200+
Gentoo Base System version 1.4.3.12
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=athlon-xp -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 /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-O3 -march=athlon-xp -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs buildpkg ccache sandbox"
GENTOO_MIRRORS="ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo
rsync://ftp.snt.utwente.nl/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="3dnow X aalib alsa apache2 apm avi berkdb cdr crypt cups encode foomaticdb
gdbm gif gnome gpm gtk gtk2 imlib joystick jpeg libg++ libwww mad matroska
mikmod mmx mozilla mpeg mysql ncurses oggvorbis opengl oss pam pdflib png python
quicktime readline sdl slang sse ssl svga tcpd truetype unicode vhost x86 xml
xml2 xmms xv zlib"
Comment 1 Masatomo Nakano (RETIRED) gentoo-dev 2003-11-29 06:01:28 UTC 
It works for me.
I'd like to know more infomation.

What did do you? emerge foo?

And please show us
# ls -l /usr/lib/portage/pym/
# ls -l /usr/lib/python2.2/site-packages/
# grep xpak /var/db/pkg/sys-apps/portage-2.0.49-r18/CONTENTS
# which xpak
# xpak

And what was the previous portage version in the machine. -r17 or -r16 or etc?
Comment 2 Manfred Stienstra 2003-11-29 06:48:39 UTC 
I copied xpak.py from the tarball to the right place and after emerging r15 and r18 again everything works again. I can't recreate te problem... Sorry.
Comment 3 Masatomo Nakano (RETIRED) gentoo-dev 2003-11-29 07:05:11 UTC 
OK. if the bug appears again, please reopen this bug.
Thanks
Comment 4 Philipp Kern 2003-12-12 04:59:11 UTC 
Using the "actual" (quite old) stage3 tarball reveals all the old problem.
Had the same here when used in conjunction with --buildpkg.
emerge failed in the same way.

It seems that after a re-emerge of portage all runs well again, which is strange as it got merged the first time.