902521 – sys-apps/portage-3.0.45.3: some emerge commands stop working with unreadable file in package.use

Bug 902521 - sys-apps/portage-3.0.45.3: some emerge commands stop working with unreadable file in package.use

Summary: sys-apps/portage-3.0.45.3: some emerge commands stop working with unreadable ...

Status:	RESOLVED INVALID

Alias:	None

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

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2023-03-21 10:03 UTC by tastytea
Modified:	2023-03-21 13:28 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 tastytea 2023-03-21 10:03:33 UTC

I made a file in /etc/portage/package.use/ unreadable to temporarily disable its effects.
`emerge -a sys-apps/portage` still works like before but `emerge -pv sys-apps/portage` exits with code 13 after printing:
> Permission denied: '/etc/portage/package.use/steam'

I think the behaviour should be consistent.

Comment 1 tastytea 2023-03-21 13:28:24 UTC

Ah, `emerge -a` did only work because it is run as root and root can read the file. 🤦

Closing this since it is consistent.