Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 365319

Summary: permissions of emerge.log are hardcoded into - the user cannot influence them
Product: Portage Development Reporter: nuffigel <nuff.igel>
Component: Core - Interface (emerge)Assignee: Portage team <dev-portage>
Severity: enhancement Keywords: InVCS
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 358927    

Description nuffigel 2011-04-29 15:51:23 UTC
I want my users to be able to read emerge.log. The standard procedure to achieve this seems to be to place the user into the portage group. However, this gives the users more privileges than intended (e.g. allowing them to write to emerge.log).

Since the permissions of emerge.log (660) are hardcoded into, I have no way of influencing them (other than hacking the source files).

Reproducible: Always

Steps to Reproduce:
1. have a user run 'qlop -l'
Actual Results:  
lop: Could not open logfile '/var/log/emerge.log': Permission denied

Expected Results:  
show the merge history
Comment 1 Zac Medico gentoo-dev 2011-04-29 16:10:01 UTC
It's fixed to only set permissions when creating the log:;a=commit;h=a706f4489a017f2609b36acc50081e58e3a7e07f
Comment 2 Zac Medico gentoo-dev 2011-05-05 19:53:58 UTC
This is fixed in and 2.2.0_alpha31.