The only version of Xpdf (app-text/xpdf-3.02-r4) was removed from the stable and made testing. Please move it back to stable (without waiting for 1 month etc. since it was there already). emerge -uDNpv --autounmask=n world ... !!! Problems have been detected with your world file !!! Please run emaint --check world !!! Ebuilds for the following packages are either all !!! masked or don't exist: app-text/xpdf ...
18 Oct 2011; Andreas K. Huettel <dilfridge@gentoo.org> xpdf-3.02-r4.ebuild: Drop to ~arch so we can get rid of poppler-0.14; probably this is not one of the most popular packages anymore.
(In reply to comment #1) > 18 Oct 2011; Andreas K. Huettel <dilfridge@gentoo.org> xpdf-3.02-r4.ebuild: > Drop to ~arch so we can get rid of poppler-0.14; probably this is not one of > the most popular packages anymore. Indeed... this was a deliberate decision. It's not frequent that something drops out of the stable set (and we dont even have official procedures for it, I asked), but poppler-0.14 was becoming unmaintainable, poppler-0.16 (current stable) does not work with xpdf, and poppler-0.18 (which works again) is still very much testing. If you want to keep using xpdf, please add poppler-0.18 and xpdf to your package.keywords file(s). Note that you will have to run revdep-rebuild after a poppler upgrade. We may re-add xpdf to the stable set once the poppler-0.18 series is stabilized.
I understand that this was a though situation. But the stable xpdf-3.02-r4 worked with stable poppler-0.16.7. According to the comment in the ebuild it was moved to testing because printing does not work. Not all users prints from xpdf so I think that this should be solved by recommending affected users (those who prints) to install testing poppler rather than affecting _all_ xpdf users by removing it from stable. Removing the only stable version of a package really should not happen at all (that's why there is no guide for it, right? ;-) ).
