42969 – emerge --fetch and sync fails if running as a user in group "portage"

Bug 42969 - emerge --fetch and sync fails if running as a user in group "portage"

Summary: emerge --fetch and sync fails if running as a user in group "portage"

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	High normal
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-02-26 04:12 UTC by Spider (RETIRED)
Modified:	2005-07-28 20:53 UTC (History)
CC List:	1 user (show)

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 Spider (RETIRED) gentoo-dev

2004-02-26 04:12:14 UTC

Well, users in the group "portage" should be able to do emerge --fetch and "sync" actions, however there is an internal check in emerge that makes this fail.

ebuild foo.ebuild fetch, works, so why shouldn't emerge -f <package>  work?

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1 Brian Harring (RETIRED) gentoo-dev

2004-08-01 03:31:26 UTC

InCVS for fetch shortly.

Comment 2 Alec Warner (RETIRED) archtester

2005-07-28 20:53:59 UTC

emerge -f <pkg> Fixed on or before Portage 2.0.51.22-r2.

emerge sync is not planned for this because of security issues.  Users could 
sync with hostile ENV settings causing a privilage escalation if root was to 
install a package that was tampered with.