Summary: | poppler has unresolved blocks | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stan Sander <stsander> |
Component: | [OLD] Library | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | loki_val |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stan Sander
2009-04-17 16:00:44 UTC
This is invalid. dev-libs/poppler is app-text/poppler without a few utils (provided now by a separate package) and app-text/poppler-bindings were split. So you need to unmerge those old versions manually, portage doesn't handle these kinds of blocks automatically (and it probably shouldn't). (In reply to comment #1) > This is invalid. > dev-libs/poppler is app-text/poppler without a few utils > (provided now by a separate package) > and app-text/poppler-bindings were split. > So you need to unmerge those old versions manually, > portage doesn't handle these kinds of blocks automatically > (and it probably shouldn't). Actually it should, as long as neither app-text/poppler or app-text/poppler-bindings are in @world. In this case it's app-text/poppler-bindings. emerge -C app-text/poppler{,-bindings} should put you on the right track. ( I actually tweaked this quite a bit so that as long as you have neither app-text/poppler nor app-text/poppler-bindings in @world, it should Just Work. ) Confirmed. emerge -C app-text/poppler{,-bindings} took care of the issue. |