The 0.12.3-r1 versions (contrary to the 0.12.3 versions) of virtual-poppler-{glib,qt4,utils} suddenly depend on ~app-text/poppler-${PV}[abiword?,png?,utils] but app-text/poppler-0.12.3 depend on those being NOT installed !dev-libs/poppler-glib etc That's broken! Reproducible: Always
Evince and tracker to longer compile /usr/include/poppler/glib/poppler.h:122:27: error: poppler-layer.h: No such file or directory. Until cups was rebuild all I have where unresolvable blockages
I have exactly same here. does poppler have to break dependencies every time it has any update?
Somehow poppler-layer.h does not get installed, even if it exists in poppler-0.12.3.tar.gz. Exract it to /usr/include/poppler/glib and you have a workaround
Helmut: you need to enable the glib useflag, and portage will then automatically handle the blockers. For your convenience I have enabled the glib useflag in app-text/poppler-0.12.3-r1 by default, as cairo and qt4 are already enabled by the desktop profile. The other issue with the missing header really should have been filed as a separate bug, but this is now also fixed in app-text/poppler-0.12.3-r1.
(In reply to comment #4) > Helmut: you need to enable the glib useflag, and portage will then > automatically handle the blockers. For your convenience I have enabled the glib > useflag in app-text/poppler-0.12.3-r1 by default, as cairo and qt4 are already > enabled by the desktop profile. I don't see how!!! emerge -vp app-text/poppler [ebuild N ] app-text/poppler-0.12.3-r2 USE="abiword cairo jpeg lcms png qt4 utils xpdf-headers -cjk -debug -doc -exceptions -jpeg2k" 0 kB [blocks B ] app-text/poppler ("app-text/poppler" is blocking app-text/poppler-utils-0.12.3, dev-libs/poppler-0.12.3, dev-libs/poppler-glib-0.12.3) [blocks B ] dev-libs/poppler ("dev-libs/poppler" is blocking app-text/poppler-0.12.3-r2) [blocks B ] dev-libs/poppler-qt4 ("dev-libs/poppler-qt4" is blocking app-text/poppler-0.12.3-r2) [blocks B ] app-text/poppler-utils ("app-text/poppler-utils" is blocking app-text/poppler-0.12.3-r2) [blocks B ] dev-libs/poppler-glib ("dev-libs/poppler-glib" is blocking app-text/poppler-0.12.3-r2) Total: 1 package (1 new), Size of downloads: 0 kB Conflict: 5 blocks (5 unsatisfied) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. ('ebuild', '/', 'app-text/poppler-0.12.3-r2', 'merge') pulled in by app-text/poppler ('installed', '/', 'app-text/poppler-utils-0.12.3', 'nomerge') pulled in by app-text/poppler-utils required by @selected ('installed', '/', 'dev-libs/poppler-0.12.3', 'nomerge') pulled in by dev-libs/poppler required by @selected ('installed', '/', 'dev-libs/poppler-qt4-0.12.3', 'nomerge') pulled in by dev-libs/poppler-qt4 required by @selected STILL app-text/poppler-0.12.3-r2.ebuild contains !dev-libs/poppler !dev-libs/poppler-glib !dev-libs/poppler-qt4 !app-text/poppler-utils on the other hand dev-libs/poppler-glib-0.12.3.ebuild and similarly virtual/poppler-glib-0.12.3-r2.ebuild and the -qt4 -utils versions, as well contains: RDEPEND=" ~dev-libs/poppler-${PV} emerge -vp virtual/poppler virtual/poppler-glib virtual/poppler-qt4 virtual/poppler-utils gives: [blocks B ] app-text/poppler ("app-text/poppler" is blocking app-text/poppler-utils-0.12.3, dev-libs/poppler-0.12.3, dev-libs/poppler-glib-0.12.3) [blocks B ] dev-libs/poppler ("dev-libs/poppler" is blocking app-text/poppler-0.12.3-r2) [blocks B ] dev-libs/poppler-qt4 ("dev-libs/poppler-qt4" is blocking app-text/poppler-0.12.3-r2) [blocks B ] app-text/poppler-utils ("app-text/poppler-utils" is blocking app-text/poppler-0.12.3-r2) [blocks B ] dev-libs/poppler-glib ("dev-libs/poppler-glib" is blocking app-text/poppler-0.12.3-r2) Total: 5 packages (4 upgrades, 1 new), Size of downloads: 0 kB Conflict: 5 blocks (5 unsatisfied) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. ('ebuild', '/', 'app-text/poppler-0.12.3-r2', 'merge') pulled in by ~app-text/poppler-0.12.3[utils,abiword,png] required by ('ebuild', '/', 'virtual/poppler-utils-0.12.3-r1', 'merge') ~app-text/poppler-0.12.3[xpdf-headers,lcms] required by ('ebuild', '/', 'virtual/poppler-0.12.3-r1', 'merge') ~app-text/poppler-0.12.3[cairo] required by ('ebuild', '/', 'virtual/poppler-glib-0.12.3-r2', 'merge') (and 1 more) ('installed', '/', 'app-text/poppler-utils-0.12.3', 'nomerge') pulled in by app-text/poppler-utils required by @selected ('installed', '/', 'dev-libs/poppler-0.12.3', 'nomerge') pulled in by dev-libs/poppler required by @selected ('installed', '/', 'dev-libs/poppler-qt4-0.12.3', 'nomerge') pulled in by dev-libs/poppler-qt4 required by @selected So, how to you get 'emerge' to proceed (This is portage-2.2_rc61)
It still doesn't work here (date 2010/01/25 8:15 GMT)
(In reply to comment #6) > It still doesn't work here (date 2010/01/25 8:15 GMT) > emerge --unmerge dev-libs/poppler dev-libs/poppler-qt4 dev-libs/poppler-glib app-text/poppler-utils followed by emerge virtual/poppler-glib virtual/poppler virtual/poppler-qt4 virtual/poppler-utils works. (It's just 9 month ago, when we had to unmerge app-text/poppler and emerge dev-libs/poppler-*) Let's see what comes in September.
In the meantime we've done several fixes, and the glib useflag has been dropped and cairo is used instead. I've dropped obsoleted versions and the current virtuals for version 0.12 all depend on app-text/poppler only.
*** Bug 302669 has been marked as a duplicate of this bug. ***
If you don't have any *poppler* entries in your world file and you useflags are correctly set (and if you are on stable you have all necessary entries in package.keywords) then there should be no problem upgrading. Feel free to reopen if you find that is not the case, and it is not user error.
(In reply to comment #10) > If you don't have any *poppler* entries in your world file and you useflags are > correctly set (and if you are on stable you have all necessary entries in ^^^^^^^^^^^^^^^^^^^^ very funny comment!!! If I were on stable I wouldn't have emerged poppler-0.12.3 at all. So, really, there wouldn't be any problem. Thanks for this joke! > package.keywords) then there should be no problem upgrading. Feel free to > reopen if you find that is not the case, and it is not user error. >
