I am chrooting into a gentoo environment through a Ubuntu Live Disk. http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?full=1&style=printable is the link I'm using to preform this gentoo install. "Code Listing 1.5: Chrooting into the new environment" is where this problem occurs. Normally env-update should say ">> Regenerating /etc/ld.so.cache..." but in this case it says:" Traceback (most recent call last): File "usr/sbin/env-update", line 27, in ? import portage File "/usr/lib/portage/pym/portage/__init__.py", line 48 except ImportError as e: ^ SyntaxError: invalid syntax Reproducible: Always Steps to Reproduce: 1.# mount -t proc none /mnt/gentoo/proc 2.# mount -o bind /dev /mnt/gentoo/dev 3.# chroot /mnt/gentoo /bin/bash 4.# env-update Actual Results: Normally env-update should say ">> Regenerating /etc/ld.so.cache..." but in this case it says:" Traceback (most recent call last): File "usr/sbin/env-update", line 27, in ? import portage File "/usr/lib/portage/pym/portage/__init__.py", line 48 except ImportError as e: ^ SyntaxError: invalid syntax Expected Results: #env-update >> Regenerating /etc/ld.so.cache...
try doing: env -i chroot /bin/bash -l
After running the suggested "env -i chroot /bin/bash -l" I got the read-out : "chroot: cannot change root directory to /bin/bash: Not a directory"
(In reply to comment #2) > After running the suggested "env -i chroot /bin/bash -l" I got the read-out : > "chroot: cannot change root directory to /bin/bash: Not a directory" Seems like you either forgot to mount the gentoo partitions or if this is a new install you forgot to unpack the stage3.
Yeah, I'm not too sure, but I can't check on that now. I downloaded a different version of the mirror and snapshot. When I did that env-update worked without a seconds hesitation. Now I have to fix the issues with connecting to the internet through chroot. =P
Alright, closing as invalid given the last comment.
Mmm... alright... But that's only because I picked an older version to compile. Which leads me to assume that between the second to latest version and the latest version, something happened that caused this error to occur in the first place. Right?
If you can duplicate this issue, feel free to reopen the bug.