On Saturday 30 January 2010 12:01:57 you wrote: > On Friday 29 January 2010 22:04:44 Neil Bothwick wrote: > > On Fri, 29 Jan 2010 20:19:46 +0000, Mick wrote: > > > I checked another machine (of a similar build) which does not seem to > > > have app-text/poppler emerged (only app-text/poppler-data, > > > app-text/poppler-utils, dev-libs/poppler, dev-libs/poppler-qt4, > > > virtual/poppler, virtual/poppler-qt4, virtual/poppler-utils). > > > > What arch are you running on these machines? poppler recently moved from > > dev-libs to app-text on ~arch. This looks like you could be running the > > stable arch with a number of packages in portage.keywords? > > They are both running stable x86, with the only keyworded package being: > ~kde- misc/kim4-0.9.5 > > What's the right way to proceed here? I see that app-text/poppler > does not show the lcms flag until version 0.12.3-r2, which is currently in > testing. I take it that app-text/poppler is not a dependency because it > would have been pulled in when I emerged whichever meta package brought in > Dophin/Konqueror. Is it that in time dev-libs/poppler will be deprecated > and app-text/poppler will be pulled in then?
To answer my own question: the right way to proceed was to wait for the mirrors to be updated and then portage unmerged/emerged the right packages. revdep-rebuild then partially fixed it. I had to emerge kde-base/kdegraphics- meta and kde-base/okular which did fix it. For some reason xpdf now won't remerge. Time for a new thread. Thanks for the pointer, lcms and app-text/poppler was the solution. :-) -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
