Bug 378605

Summary:	Emerge suggests user to disable USE flag which is no longer relevant
Product:	Portage Development	Reporter:	Michał Górny <mgorny>
Component:	Core - Interface (emerge)	Assignee:	Portage team <dev-portage>
Status:	RESOLVED INVALID
Severity:	minor
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	300071

Description Michał Górny archtester

2011-08-10 07:33:28 UTC

Consider the following.

Package A-1 had 'python' USEflag when it was installed. The flag was enabled and thus vardb now has A[python].

Now package A-1 has been modified and it no longer has 'python' USEflag. No packages matching A have 'python' in IUSE.

Package B-1 depends on A[-python]. Because A in vardb has 'python' in USE, emerge suggests user to disable that flag through package.use. But in fact, it is enough just to rebuild A as it no longer carries that flag, and package.use change is irrelevant then.

Comment 1 Sebastian Luther (few) 2011-08-10 11:09:56 UTC

Your description is missing something. With the steps you descried, B cannot be installed.

If B deps on A[-python], then B cannot be installed.
 - the installed A has USE="python"
 - the ebuilds for A don't satisfy B's dependencies because they don't have 'python' in IUSE.

emerge correctly detects this and errors out.

Comment 2 Michał Górny archtester

2011-08-10 11:54:07 UTC

And if I used the EAPI4 magical (-) use, wouldn't portage behave the same? :P

Comment 3 Sebastian Luther (few) 2011-08-10 12:52:23 UTC

(In reply to comment #2)
> And if I used the EAPI4 magical (-) use, wouldn't portage behave the same? :P

If B depends on A[-python(-)] then it re-installs A and merges B after that.

Comment 4 Michał Górny archtester

2011-08-11 19:11:41 UTC

Ok, after using a real test case the issue is invalid indeed. Forgive me.