Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 2931 - emerge unable to mkdir. ACCESS DENIED
Summary: emerge unable to mkdir. ACCESS DENIED
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: x86 Linux
: High blocker (vote)
Assignee: Daniel Robbins (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-22 15:49 UTC by djorgensen@internap.com
Modified: 2011-10-30 22:20 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description djorgensen@internap.com 2002-05-22 15:49:26 UTC
Portage version 1.9.12.

emerge sys-apps/portage.

Updates to 1.9.13.

Fails on 

+ install -v -m0700 -d /var/tmp/portage/portage-1.9.13/work
ACCESS DENIED  mkdir:     /usr/var/tmp/portage/portage-1.9.13/work
install: cannot create directory `/var/tmp/portage/portage-1.9.13/work':
Permission denied

I have traced this call to /usr/sbin/ebuild.sh and the command "install -d
${WORKDIR}"

The install -d command works on the shell.  
If I do a mkdir in place of the install -d the directory is properly created.
But fails on the next attempt to call the command install -d.
I also tried dumping the command into another shell script and it ran fine there
as well.

I have looked at the sandbox-emerge.*.logs but they don't seem to elude to a
possible solution.

Emerge worked fine until I attempted to upgrade to the newer versions moving
from the release canidate to the 1.1 release.
Comment 1 Daniel Robbins (RETIRED) gentoo-dev 2002-06-19 12:44:14 UTC
Are you still having this issue?  Did you move /var to /usr/var?  I see /usr/var
down there, and it's possible that some changes you made caused the sandbox to
mess up (a bug, not your fault.)
Comment 2 Daniel Robbins (RETIRED) gentoo-dev 2002-07-11 03:13:23 UTC
OK, this was probably caused by either /var or /var/tmp being a symlink.  This
has been fixed in the sandbox code as of Portage 2.0.12