Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 603132 - "disqualify" binpkg if ebuild is not available
Summary: "disqualify" binpkg if ebuild is not available
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 155723
  Show dependency tree
 
Reported: 2016-12-19 19:42 UTC by Rick Farina (Zero_Chaos)
Modified: 2017-03-09 00:49 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Farina (Zero_Chaos) gentoo-dev 2016-12-19 19:42:17 UTC
it is possible to end up in situations like this:

- dev-ruby/awesome_print-1.6.1::gentoo (masked by: use flag configuration mismatch)

when an old binpkg exists and no ebuild exists any longer.  It is a very confusing error message that basically boils down to "the binpkg is bad and we can't rebuild it" which would be much better served with an option to not consider the binpkg if it's out of date and cannot be rebuilt (in my opinion).

One possible solution to this (which may be insane) would be to calculate deps based on ebuilds only, and then see if binpkgs happen to be available which match.
Comment 1 Zac Medico gentoo-dev 2016-12-19 19:52:42 UTC
For the specific situation that you've encountered with the unsatisfied awesome_print dependency, I would expect the new output to be something like this:

 - dev-ruby/awesome_print-1.6.1::gentoo (masked by: corresponding ebuild is not available)

Sounds reasonable?