| View previous topic :: View next topic |
| Author |
Message |
gemi
n00b
Joined: 10 Oct 2012
Posts: 31
|
 Posted: Wed Jul 24, 2013 6:58 am Post subject: broken emerge portage |
 |
|
I try to do a fresh install of gentoo with:
portage-latest.tar.bz2 and stage3-i486-20130528.tar.bz2
As soon as I want to emerge something it claims that portage needs an update. So I do emerge -av --oneshot portage
that results in the following error
| Code: |
/var/tmp/portage/sys-apps/portage-2.1.12.2/temp/environment: line 2336: /dev/fd/62: Not a directory
* ERROR: sys-apps/portage-2.1.12.2 failed (install phase):
* directory does not exist: /var/tmp/portage/sys-apps/portage-2.1.12.2/image/usr/lib/python3.2/site-packages
*
* Call stack:
* ebuild.sh, line 93: Called src_install
* environment, line 2363: Called python_compileall '/usr/lib/python3.2/site-packages'
* environment, line 2298: Called die
* The specific snippet of code:
* [[ -d ${d_image} ]] || die "directory does not exist: ${d_image}";
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.1.12.2'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.1.12.2'`.
* The complete build log is located at '/var/tmp/portage/sys-apps/portage-2.1.12.2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.1.12.2/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.1.12.2/work/portage-2.1.12.2'
* S: '/var/tmp/portage/sys-apps/portage-2.1.12.2/work/portage-2.1.12.2'
>>> Failed to emerge sys-apps/portage-2.1.12.2, Log file:
>>> '/var/tmp/portage/sys-apps/portage-2.1.12.2/temp/build.log'
* Messages for package sys-apps/portage-2.1.12.2:
* ERROR: sys-apps/portage-2.1.12.2 failed (install phase):
* directory does not exist: /var/tmp/portage/sys-apps/portage-2.1.12.2/image/usr/lib/python3.2/site-packages
*
* Call stack:
* ebuild.sh, line 93: Called src_install
* environment, line 2363: Called python_compileall '/usr/lib/python3.2/site-packages'
* environment, line 2298: Called die
* The specific snippet of code:
* [[ -d ${d_image} ]] || die "directory does not exist: ${d_image}";
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.1.12.2'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.1.12.2'`.
* The complete build log is located at '/var/tmp/portage/sys-apps/portage-2.1.12.2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.1.12.2/temp/environment'.
* Working directory: '/var/tmp/portage/sys-apps/portage-2.1.12.2/work/portage-2.1.12.2'
* S: '/var/tmp/portage/sys-apps/portage-2.1.12.2/work/portage-2.1.12.2'
|
any ideas of what I do wrong?
Cheers
gemi |
|
| Back to top |
|
 |
defer-
Tux's lil' helper
Joined: 11 Jun 2007
Posts: 140
Location: Finland
|
| Posted: Wed Jul 24, 2013 7:36 am Post subject: |
|
|
Try to run python-updater and paste the output of eselect python list.
_________________
https://github.com/defer- |
|
| Back to top |
|
|
gemi
n00b
Joined: 10 Oct 2012
Posts: 31
|
| Posted: Wed Jul 24, 2013 7:37 am Post subject: |
|
|
it looks like it has got something to do with correctly mounted /dev
I have to add that I am facing this problem in a chrooted environment with
| Code: |
mount -t proc none /var/os/proc
mount --rbind /sys /var/os/sys
mount --rbind /dev /var/os/dev
|
is there something wrong with that |
|
| Back to top |
|
|
gemi
n00b
Joined: 10 Oct 2012
Posts: 31
|
| Posted: Wed Jul 24, 2013 11:05 am Post subject: |
|
|
it seems to work now. I fixed one of my scripts that mounts /dev
| Code: | mount -t proc none ${DEST}/proc
mount --rbind /dev ${DEST}/dev |
|
|
| Back to top |
|
|
|
Installing Gentoo
