emerge -pvuDN world gives different results if ran as a regular user than if ran as root. Reproducible: Always Steps to Reproduce: 1. Ensure you have some updates for emerge to process 2. Run "emerge -pvuDN world" as a regular user, view results. 3. Run "emerge -pvuDN world" as root or with sudo, view results. 4. Notice the difference. Actual Results: Not all packages are listed that will be re-emerged. Expected Results: All packages that will be re-emerged should be viewable. Here is an example: clinton@e521 ~ $ emerge -pvuDN world These are the packages that would be merged, in order: Calculating world dependencies... done! [ebuild U ] sys-apps/less-416 [409] USE="unicode" 288 kB Total: 1 package (1 upgrade), Size of downloads: 288 kB clinton@e521 ~ $ sudo emerge -pvuDN world Password: These are the packages that would be merged, in order: Calculating world dependencies... done! [ebuild U ] sys-apps/less-416 [409] USE="unicode" 288 kB [ebuild U ] media-libs/freetype-2.3.5-r2 [2.3.4-r2] USE="X doc -bindist -debug -utils% (-zlib%*)" 1,347 kB [ebuild U ] net-misc/neon-0.26.4 [0.26.3] USE="kerberos%* nls ssl zlib -expat -socks5" 776 kB [ebuild U ] net-www/netscape-flash-9.0.115.0 [9.0.48.0-r1] 2,962 kB Total: 4 packages (4 upgrades), Size of downloads: 5,371 kB clinton@e521 ~ $
check permissions of files in /etc/portage, /var/lib/portage and /var/db/pkg presumably some of them aren't readable by your user.
All files have user, group, and world permission for reading. The only oddity I could find was that /usr/lib/portage could not be cd'ed into, but the files /usr/lib/portage/world and /usr/lib/portage/config could still be read.
Created attachment 139874 [details, diff] raise PermissionDenied instead of ignoring permission errors With this patch applied, you should be notified of any config files that are unreadable due to permissions. If it's saved as /tmp/eaccess.patch then you can apply it as follows: patch /usr/lib/portage/pym/portage_util.py /tmp/eaccess.patch
Applied that patch. No change in behavior, no errors either.
It seems to matter whether the user is a member of the portage group. The handbook says to make a user a member of the portage group if he is going to use "emerge --pretend"
(In reply to comment #5) > It seems to matter whether the user is a member of the portage group. The > handbook says to make a user a member of the portage group if he is going to > use "emerge --pretend" That was necessary with older versions of portage but it shouldn't be anymore. Users in the portage group are capable of interfering with portage so having users in that group is a security risk.
(In reply to comment #0) > Steps to Reproduce: > 1. Ensure you have some updates for emerge to process > 2. Run "emerge -pvuDN world" as a regular user, view results. > 3. Run "emerge -pvuDN world" as root or with sudo, view results. > 4. Notice the difference. Please attach logs for #2 and #3 with --debug enabled.
Please reopen with logs requested in comment #7.
(In reply to comment #8) > Please reopen with logs requested in comment #7. > This bug has not re-occurred. If I ever do see it again I will attach logs. Marking as closed for the time being.
