Summary: | emerge -pv shows different output as root and normal user | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Rieder <bugzilla> |
Component: | New packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | minor | CC: | x11 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Rieder
2004-07-05 16:04:59 UTC
I think this is a portage problem. permissions on /var/cache/edb, specifically the file virtuals. You're right, chmod 644 /var/cache/edb/virtuals helps. BTW: What's /var/cache/edb/config for? I checked another box with a more recent Gentoo installation and /var/cache/edb/* was world readable, though I haven't touched /var/cache on either machine. I tried deleting /var/cache/edb and after running emerge once, /var/cache/edb/virtuals and /var/cache/edb/world have the right permissions, but are empty, which leads to even more problems. (BTW: /var/cache/edb/config is still not world readable.) Don't know what to say about the permissions issue. If it can be duplicated please let me know and we'll track down what causes it. config is for remembering which config files can be ignored when merging new files into CONFIG_PROTECT locations. Saves some of the repeated updates people may have to perform. Deleting virtuals isn't a good idea. 2.0.51 doesn't use that file, so you might consider using it instead. There is no cache yet, so it will complain a lot toward the end of sync. 2.0.51 also moves all state files out of /var/cache so you don't delete them by accident. |