632271 – emerge --onlydeps <PKG> still prompts for unmasking/keywording of <PKG> even though it won't be installed.

Bug 632271 - emerge --onlydeps <PKG> still prompts for unmasking/keywording of <PKG> even though it won't be installed.

Summary: emerge --onlydeps <PKG> still prompts for unmasking/keywording of <PKG> even ...

Status:	CONFIRMED

Alias:	None

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

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	autounmask
	Show dependency tree

Reported:	2017-09-28 18:02 UTC by lperkins
Modified:	2017-11-04 22:00 UTC (History)
CC List:	2 users (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 lperkins 2017-09-28 18:02:46 UTC

Given masked/keyworded package <FOO> where all of its dependencies have no mask or keyword restrictions:

Running:  emerge -av --onlydeps <FOO>

results in being prompted to autounmask <FOO>, despite the fact that <FOO> is not in the list of packages to be installed.

Comment 1 Zac Medico gentoo-dev

2017-09-30 18:15:00 UTC

Yeah, we could discard these config changes for --onlydeps packages.