| Summary: | sys-apps/paludis-2.0.0 Internal error at void paludis::resolver::NAG::verify_edges() const at nag.cc:167 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Julian Ospald <hasufell> |
| Component: | Current packages | Assignee: | Michał Górny <mgorny> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | ciaran.mccreesh, mgorny |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | http://paludis.exherbo.org/trac/ticket/1227 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
paludis-internal-error.txt
paludis-internal-error.txt |
||
if you need more information, please say so, this is perfectly reproducible for me Created attachment 381742 [details]
paludis-internal-error.txt
http://paludis.exherbo.org/trac/ticket/1227 It's easy enough to work around... Trying to fix the bug made my head hurt last time I looked at it. this is caused by the following configuration in keywords.conf: =virtual/perl-Module-Build-0.420.0-r1 ~amd64 =perl-core/Module-Build-0.420.0 ~amd64 We've got a minimal test case. It's down to disappearing USE flags. (In reply to Ciaran McCreesh from comment #5) > We've got a minimal test case. It's down to disappearing USE flags. you mean in-place ebuild changes? Have a look at the linked ticket. As far as I know, it's a "can't display a decent error" problem, not a "can't work out a resolution when one is available" problem. Paludis has been removed from the tee. |
Created attachment 381740 [details] paludis-internal-error.txt issued command cave resolve -c dev-lang/perl -D perl current perl is stable 5.16.3, update to 5.18.2-r1 pending