First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 99120
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Portage team <dev-portage@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jeremy Barton <sixteen-gentoo@xyons.net>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
portage.py.unified.diff.patch patch of the /usr/lib/portage/pym/portage.py patch Jaroslav Henner 2005-08-04 13:54 0000 758 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 99120 depends on: Show dependency tree
Bug 99120 blocks: 108082
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-07-15 09:21 0000 
In combination with bug #99101, the ccache+userpriv permissions checking also
compares the directory UID with the portage GID.  While these are normally the
same it is not, in fact, what the code modifies.

Suggest changing it to either
mystat[stat.ST_UID] != portage_uid
or
mystat[stat.ST_GID] != portage_gid

probably the latter.


Reproducible: Always
Steps to Reproduce:
Code defect

------- Comment #1 From Jaroslav Henner 2005-08-04 13:54:20 0000 ------- 
Created an attachment (id=65095) [details]
patch of the /usr/lib/portage/pym/portage.py

------- Comment #2 From Alec Warner 2005-08-09 17:54:25 0000 ------- 
Looks good to me, if portage's GID is not equal to the UID then all kinds of 
permission changes get triggers, even through they aren't needed.  A quick check 
shows stable could use it.

------- Comment #3 From Jakub Moc (RETIRED) 2005-08-31 10:23:53 0000 ------- 
*** Bug 104392 has been marked as a duplicate of this bug. ***

------- Comment #4 From Jason Stubbs (RETIRED) 2005-10-04 23:39:13 0000 ------- 
Fixed in 2.0.53_rc3
First Last Prev Next    No search results available      Search page      Enter new bug