Summary: | AttributeError: 'module' object has no attribute 'userpriv_groups' | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Noah McNallie <n0ah> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | rain |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | Sparc | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 335925 | ||
Attachments: | fix the AttributeError |
Description
Noah McNallie
2010-02-18 18:03:53 UTC
Created attachment 220205 [details, diff]
fix the AttributeError
Save as /tmp/userpriv_groups.patch and apply as follows:
patch /usr/lib/portage/pym/portage/data.py /tmp/userpriv_groups.patch
(In reply to comment #1) > Created an attachment (id=220205) [details] > fix the AttributeError > > Save as /tmp/userpriv_groups.patch and apply as follows: > > patch /usr/lib/portage/pym/portage/data.py /tmp/userpriv_groups.patch > now i get this, should i change it back and add the group or keep the patch (though the unmerge seems to be working in progress) -- BEGIN PORTAGE OUTPUT -- portage: 'portage' user or group missing. For the defaults, line 1 goes into passwd, and 2 into group. portage:x:250:250:portage:/var/tmp/portage:/bin/false portage::250:portage *** WARNING *** For security reasons, only system administrators should be *** WARNING *** allowed in the portage group. Untrusted users or processes *** WARNING *** can potentially exploit the portage group for attacks such as *** WARNING *** local privilege escalation. -- END PORTAGE OUTPUT -- why are all my groups missing? Maybe /etc/group got corrupted somehow? I bumped into this installing @system on a (very) bare system, basically from scratch. I verified that the patch indeed fixes it; Also, I'd like to note that merely remerging @system will reconstruct the most basic /etc/passwd and /etc/group contents, as part of the post-install functions of certain ebuilds (not sure which ones), in fact most of the basic /etc configs can be reconstructed this way, so it would seem to make sense to make portage immune to deficiency of those (or similar) seemingly vital files in general, setting up some sane defaults and carrying on. (which is what the patch does for /etc/group) Issues like this (including bug 330645) should be solved in 2.1.9 by these fixes: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=47b5490fe3f36afee860ecd62fb3052ee2a3b6d4 http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=a75c3cb55fd3a6f8a33a521c12f8d66649020ea8 |