View previous topic :: View next topic |
Author |
Message |
BlackSwan n00b
Joined: 16 May 2008 Posts: 14 Location: Toronto, Canada
|
Posted: Sun Nov 09, 2008 11:18 pm Post subject: Portage-2.2_rc13 'permission denied' annoyance [SOLVED] |
|
|
I just upgraded to Portage 2.2 (which is necessary e.g. for Compiz-Fusion 0.7.8 and KDE 4.1). It works great, but there is one tiny annoyance: using 'emerge -p [package_name]' as a regular user produces 8 extra lines of permission complaints. For example:
$ emerge -pv latexsuite
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] app-vim/latexsuite-1.5.20060325 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
* error scanning '/etc': find: `/etc/cron.weekly': Permission denied
find: `/etc/cron.monthly': Permission denied
find: `/etc/skel/.ssh': Permission denied
find: `/etc/fcron': Permission denied
find: `/etc/cron.hourly': Permission denied
find: `/etc/ssl/private': Permission denied
find: `/etc/portage/-': Permission denied
find: `/etc/cron.daily': Permission denied
$
I realize that Portage 2.2 is still considered unstable, and that this is a pretty trivial issue. Still, I use emerge --pretend as a regular user quite frequently, so if there's a simple fix, I'd love to hear about it.
Thanks!
Last edited by BlackSwan on Thu Nov 13, 2008 7:31 pm; edited 1 time in total |
|
Back to top |
|
|
kevstar31 Guru
Joined: 22 Nov 2006 Posts: 449 Location: Ohio
|
Posted: Mon Nov 10, 2008 2:25 am Post subject: |
|
|
Is your user in the portage group? _________________ while(true) std::cout << "Jesus I trust in you." << std::endl;
My Political Compass |
|
Back to top |
|
|
BlackSwan n00b
Joined: 16 May 2008 Posts: 14 Location: Toronto, Canada
|
Posted: Mon Nov 10, 2008 2:38 pm Post subject: |
|
|
kevstar31 wrote: | Is your user in the portage group? |
Yes. |
|
Back to top |
|
|
padoor Advocate
Joined: 30 Dec 2005 Posts: 4185 Location: india
|
Posted: Mon Nov 10, 2008 2:40 pm Post subject: |
|
|
try shutdown -F now
after fsck it may become ok. _________________ reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name) |
|
Back to top |
|
|
BlackSwan n00b
Joined: 16 May 2008 Posts: 14 Location: Toronto, Canada
|
Posted: Mon Nov 10, 2008 3:11 pm Post subject: |
|
|
padoor wrote: | try shutdown -F now
after fsck it may become ok. |
Didn't help. |
|
Back to top |
|
|
BlackSwan n00b
Joined: 16 May 2008 Posts: 14 Location: Toronto, Canada
|
Posted: Tue Nov 11, 2008 10:34 pm Post subject: |
|
|
If no one has any other ideas, is it appropriate to submit a bug report? Or is this issue too minor? |
|
Back to top |
|
|
padoor Advocate
Joined: 30 Dec 2005 Posts: 4185 Location: india
|
Posted: Thu Nov 13, 2008 5:09 pm Post subject: |
|
|
emerge -pv latexsuite
try emerge with su and passwd.
#emerge -pv latexsuite
if it works we can see about emerging pamagain. _________________ reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name) |
|
Back to top |
|
|
BlackSwan n00b
Joined: 16 May 2008 Posts: 14 Location: Toronto, Canada
|
Posted: Thu Nov 13, 2008 6:29 pm Post subject: |
|
|
padoor wrote: | emerge -pv latexsuite
try emerge with su and passwd.
#emerge -pv latexsuite
if it works we can see about emerging pamagain. |
Running emerge --pretend as the superuser does not produce these extra lines. Is that what you mean? Should I try remerging pam? |
|
Back to top |
|
|
BlackSwan n00b
Joined: 16 May 2008 Posts: 14 Location: Toronto, Canada
|
Posted: Thu Nov 13, 2008 7:31 pm Post subject: |
|
|
I just emerged the new release candidate (rc14) for Portage 2.2, which solved the problem. Thanks to the Portage development team for doing such a great job! |
|
Back to top |
|
|
|