365319 – permissions of emerge.log are hardcoded into emergelog.py - the user cannot influence them

Bug 365319 - permissions of emerge.log are hardcoded into emergelog.py - the user cannot influence them

Summary: permissions of emerge.log are hardcoded into emergelog.py - the user cannot i...

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Interface (emerge) (show other bugs)
Hardware:	All Linux

Importance:	Normal enhancement (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	InVCS

Depends on:
Blocks:	358927
	Show dependency tree

Reported:	2011-04-29 15:51 UTC by nuffigel
Modified:	2011-05-05 19:53 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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 emergelog.py, 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:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=a706f4489a017f2609b36acc50081e58e3a7e07f

Comment 2 Zac Medico gentoo-dev

2011-05-05 19:53:58 UTC

This is fixed in 2.1.9.47 and 2.2.0_alpha31.