I'm having some issues upgrading portage from 2.2.00.9468 to 2.2.00.9500
on my amd64-linux install (on Debian Etch, AMD64). I can re-emerge 9468,
but with 9500 (and also 9494) I get:


>>> Emerging (1 of 1) sys-apps/portage-2.2.00.9500 to /
* prefix-portage-2.2.00.9500.tar.bz2 RMD160 SHA1 SHA256 size ;-)
... [ ok ]
* checking ebuild checksums ;-)
... [ ok ]
* checking auxfile checksums ;-)
... [ ok ]
* checking miscfile checksums ;-)
... [ ok ]
* checking prefix-portage-2.2.00.9500.tar.bz2 ;-)
... [ ok ]

>>> Unpacking source...
>>> Unpacking prefix-portage-2.2.00.9500.tar.bz2 to
/opt/hwbp/var/tmp/portage/sys-apps/portage-2.2.00.9500/work

>>> Source unpacked.
>>> Compiling source in
/opt/hwbp/var/tmp/portage/sys-apps/portage-2.2.00.9500/work/prefix-portage-2.2.00.9500
...

Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named portage.const
* econf: updating prefix-portage-2.2.00.9500/config.guess with
/opt/hwbp/usr/share/gnuconfig/config.guess
* econf: updating prefix-portage-2.2.00.9500/config.sub with
/opt/hwbp/usr/share/gnuconfig/config.sub
./configure --prefix=/opt/hwbp/usr --host=x86_64-pc-linux-gnu
--mandir=/opt/hwbp/usr/share/man --infodir=/opt/hwbp/usr/share/info
--datadir=/opt/hwbp/usr/share --sysconfdir=/opt/hwbp/etc
--localstatedir=/opt/hwbp/var/lib --with-portage-user=root
--with-portage-group=root --with-root-user=
--with-offset-prefix=/opt/hwbp --with-default-path=/usr/bin:/bin
--libdir=/opt/hwbp/usr/lib64 --build=x86_64-pc-linux-gnu

checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
<snip>
checking for the *time fields in struct stat... st_*tim
checking if S_ISWHT can be used... no
checking if lchown exists... yes
configure: error: bad value for --with-root-user

!!! Please attach the following file when seeking support:
!!!
/opt/hwbp/var/tmp/portage/sys-apps/portage-2.2.00.9500/work/prefix-portage-2.2.00.9500/config.log



Any clues? I can send the config.log through if it helps. I didn't have
any issues installing 9500 on my Debian Etch/x86-linux install.


Matt.
--
gentoo-alt@lists.gentoo.org mailing list

Fabian Groffen wrote:

On 25-03-2008 11:12:36 +1100, Matt Michalowski wrote:

Compiling source in

/opt/hwbp/var/tmp/portage/sys-apps/portage-2.2.00.9500/work/prefix-portage-2.2.00.9500
...

Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named portage.const



Looks like python can't find Portage. That is at least "weird". Are
you sure Portage uses prefix python, and that prefix python was indeed
compiled by the ebuild?

I think you suffer from an old bug that aparently is still not yet fixed
properly. Or it just is there because you use a long living Prefix
install.

Check if your $EPREFIX/usr/lib and $EPREFIX/lib are symlinks pointing to
the lib64 variants. If you fix that, it may be that python suddenly can
find python again.


It's a reasonably long living install.

It turns out my $EPREFIX/usr/lib and $EPREFIX/usr/lib64 were different
directories. $EPREFIX/usr/lib had gcc, gentoolkit and portage
directories inside it, so I moved them all to $EPREFIX/usr/lib64,
removed the $EPREFIX/usr/lib directory and symlinked $EPREFIX/usr/lib64
to $EPREFIX/usr/lib.


Now all is well, and the upgrade to 9500 succeeded, thanks.

Matt.
--
gentoo-alt@lists.gentoo.org mailing list