Summary: | portage-2.1.10.47 - IOError: [Errno 13] Permission denied: '/var/log/portage/elog/app-emulation:vmware-workstation-8.0.2.591240:20120218-170233.log' | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Nikos Chantziaras <realnc> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Nikos Chantziaras
2012-02-18 17:06:54 UTC
Please post the output of the following command: ls -ld /var/log/portage /var/log/portage/elog (In reply to comment #1) > Please post the output of the following command: > > ls -ld /var/log/portage /var/log/portage/elog drwxr-xr-x 3 root root 4096 Aug 26 2009 /var/log/portage drwxrws--- 2 portage root 106496 Feb 18 20:25 /var/log/portage/elog Somehow you got the wrong permissions. This will fix it: chown portage:portage /var/log/portage /var/log/portage/elog chmod g+ws /var/log/portage /var/log/portage/elog I don't know how you got the wrong permissions. Portage doesn't change the permissions automatically, in order to respect the permissions that the administrator may have set. As long as the stage3 tarball contains the correct permissions, and portage sets the permissions correctly if it has to create the directory, then we can close this bug as RESOLVED:WORKSFORME. I installed Gentoo on this machine in 2006. I've never reinstalled again after that. At some point, I stopped being able to use "elogv" as a normal user (the user is in the "portage" group). I do not remember when that happened, but I am absolutely sure that I never changed the permissions of that directory myself. I suppose an ebuild did this (perhaps in an attempt to update the system to new directory permissions or something,) but I guess we'll never know which one. So I'm closing this, since it seems I'm the only one who has this problem. Should I investigate further though? I could post a message on the users mailing list and ask if anyone out there has the same permission problem. (In reply to comment #4) > Should I investigate further though? No, if it's not reproducible then it's not worth investigating. One possible cause is that you upgraded to portage-2.1.10.11 before I added the permission tweaks to the ebuild for bug 377177. |