+++ This bug was initially created as a clone of Bug #199792 +++ I tried to emerge kdegraphics-3.5.9, but it failed to built with the error message "checking for poppler-qt >= 0.3.1... configure: error: --with-poppler was given, but test for poppler failed" After I emerged poppler-bindings-0.6.3 the configure script ran successfully. Before I had installed poppler-bindings-0.6.1. Shouldn't be the poppler-bindings get upgraded automatically, when poppler and therefore kdegraphics needs to be upgraded? I have attached the config.log
Created attachment 158019 [details] config.log of failed emerge of kdegraphics-3.5.9
Well, looks like I was a bit sloppy wrt. bug 199792. Your workaround is to do --deep updates. The dependency is correctly specified in the poppler-bindings ebuild. It's a dependency resolution deficiency in Portage. The problem here is, that Portage neither looks up, if an installed ebuilds dependency list conflicts with the updated poppler, nor checks if updating such a packages to a newer ebuild would remedy the situation. Portage devs, while the reverse dependency problem is of course a known one, I'm not quite sure about Portage's 2.2 reverse dependency resolution capabilities nor do I find an open bug blocking bug 155723, matching this problem. Please note that this is not a linking issue, but pkgconfig bailing out because of stricter requirements, than library versioning implies.
(In reply to comment #2) > Well, looks like I was a bit sloppy wrt. bug 199792. Your workaround is to do > --deep updates. The dependency is correctly specified in the poppler-bindings > ebuild. It's a dependency resolution deficiency in Portage. > > The problem here is, that Portage neither looks up, if an installed ebuilds > dependency list conflicts with the updated poppler, nor checks if updating such > a packages to a newer ebuild would remedy the situation. Could you elaborate on the conflict that you are you referring to? I'm not sure what it is, maybe it's something like bug 199856? > Portage devs, while the reverse dependency problem is of course a known one, > I'm not quite sure about Portage's 2.2 reverse dependency resolution > capabilities nor do I find an open bug blocking bug 155723, matching this > problem. Please note that this is not a linking issue, but pkgconfig bailing > out because of stricter requirements, than library versioning implies. In portage-2.2 there is a --complete-graph option which can be used to ensure that all dependencies are accounted for. It would be nice if we could enable it by default, but it consumes about 3x as much time for a small dep calculation (difference isn't noticeable for larger calculations).
kde-3 is no longer in portage
