[gentoo-user] poppler vs virtual/poppler eix-test-obsolete
Hi, Mostly in support of (I think) KDE I have poppler installed which seems to cause eix-test-obsolete a little indigestion. It sees virtual/poppler as installed but says they are not in the database. Do I have a problem here (eix-test-obsolete itself or my use of it, use flags, some sort of database problem, etc.) or is this some sort of ebuild problem that will likely get worked out over the next few weeks? Thanks, Mark firefly ~ # eix -Ic poppler [I] app-text/poppler (0.12.3...@02/14/10): PDF rendering library based on the xpdf-3.0 code base firefly ~ # equery depends =app-text/poppler-0.12.3-r3 [ Searching for packages depending on =app-text/poppler-0.12.3-r3... ] app-misc/strigi-0.7.0 (=app-text/poppler-0.12.3-r3[utils]) app-text/evince-2.26.2 (=app-text/poppler-0.12.3-r3[cairo]) kde-base/okular-4.3.3 (pdf? =app-text/poppler-0.12.3-r3[lcms,qt4]) net-print/cups-1.3.11-r1 (=app-text/poppler-0.12.3-r3[utils]) virtual/poppler-0.12.3-r1 (~app-text/poppler-0.12.3[lcms?,xpdf-headers]) virtual/poppler-glib-0.12.3-r2 (~app-text/poppler-0.12.3[cairo]) virtual/poppler-qt4-0.12.3-r1 (~app-text/poppler-0.12.3[qt4]) virtual/poppler-utils-0.12.3-r1 (~app-text/poppler-0.12.3[abiword?,png?,utils]) firefly ~ # eix-test-obsolete -d No non-matching entries in /etc/portage/package.keywords. No non-matching entries in /etc/portage/package.mask. No non-matching entries in /etc/portage/package.unmask. No non-matching or empty entries in /etc/portage/package.use. No non-matching or empty entries in /etc/portage/package.cflags. The following installed packages are not in the database: virtual/poppler virtual/poppler-glib virtual/poppler-qt4 virtual/poppler-utils -- No redundant entries in /etc/portage/package.keywords (or test switched off). No redundant entries in /etc/portage/package.mask (or test switched off). No redundant entries in /etc/portage/package.unmask (or test switched off). No redundant entries in /etc/portage/package.use (or test switched off). No redundant entries in /etc/portage/package.cflags (or test switched off). No uninstalled entries in /etc/portage/package.keywords (or test switched off). No uninstalled entries in /etc/portage/package.mask (or test switched off). No uninstalled entries in /etc/portage/package.unmask (or test switched off). No uninstalled entries in /etc/portage/package.use (or test switched off). No uninstalled entries in /etc/portage/package.cflags (or test switched off). All installed versions of packages are in the database. firefly ~ # firefly ~ # slocate poppler | grep virtual /var/db/pkg/virtual/poppler-0.12.3-r1 /var/db/pkg/virtual/poppler-0.12.3-r1/COUNTER /var/db/pkg/virtual/poppler-0.12.3-r1/KEYWORDS /var/db/pkg/virtual/poppler-0.12.3-r1/DEFINED_PHASES /var/db/pkg/virtual/poppler-0.12.3-r1/PF /var/db/pkg/virtual/poppler-0.12.3-r1/PROPERTIES /var/db/pkg/virtual/poppler-0.12.3-r1/DEPEND /var/db/pkg/virtual/poppler-0.12.3-r1/DESCRIPTION /var/db/pkg/virtual/poppler-0.12.3-r1/USE /var/db/pkg/virtual/poppler-0.12.3-r1/FEATURES /var/db/pkg/virtual/poppler-0.12.3-r1/SLOT /var/db/pkg/virtual/poppler-0.12.3-r1/RDEPEND /var/db/pkg/virtual/poppler-0.12.3-r1/SIZE /var/db/pkg/virtual/poppler-0.12.3-r1/IUSE /var/db/pkg/virtual/poppler-0.12.3-r1/poppler-0.12.3-r1.ebuild /var/db/pkg/virtual/poppler-0.12.3-r1/CFLAGS /var/db/pkg/virtual/poppler-0.12.3-r1/environment.bz2 /var/db/pkg/virtual/poppler-0.12.3-r1/repository /var/db/pkg/virtual/poppler-0.12.3-r1/LDFLAGS /var/db/pkg/virtual/poppler-0.12.3-r1/EAPI /var/db/pkg/virtual/poppler-0.12.3-r1/CATEGORY /var/db/pkg/virtual/poppler-0.12.3-r1/CBUILD /var/db/pkg/virtual/poppler-0.12.3-r1/CXXFLAGS /var/db/pkg/virtual/poppler-0.12.3-r1/CHOST /var/db/pkg/virtual/poppler-0.12.3-r1/CONTENTS /var/db/pkg/virtual/poppler-glib-0.12.3-r2 /var/db/pkg/virtual/poppler-glib-0.12.3-r2/COUNTER /var/db/pkg/virtual/poppler-glib-0.12.3-r2/KEYWORDS /var/db/pkg/virtual/poppler-glib-0.12.3-r2/DEFINED_PHASES /var/db/pkg/virtual/poppler-glib-0.12.3-r2/PF /var/db/pkg/virtual/poppler-glib-0.12.3-r2/PROPERTIES /var/db/pkg/virtual/poppler-glib-0.12.3-r2/DEPEND /var/db/pkg/virtual/poppler-glib-0.12.3-r2/DESCRIPTION /var/db/pkg/virtual/poppler-glib-0.12.3-r2/USE /var/db/pkg/virtual/poppler-glib-0.12.3-r2/poppler-glib-0.12.3-r2.ebuild /var/db/pkg/virtual/poppler-glib-0.12.3-r2/FEATURES /var/db/pkg/virtual/poppler-glib-0.12.3-r2/SLOT /var/db/pkg/virtual/poppler-glib-0.12.3-r2/RDEPEND /var/db/pkg/virtual/poppler-glib-0.12.3-r2/SIZE /var/db/pkg/virtual/poppler-glib-0.12.3-r2/IUSE /var/db/pkg/virtual/poppler-glib-0.12.3-r2/CFLAGS /var/db/pkg/virtual/poppler-glib-0.12.3-r2/environment.bz2 /var/db/pkg/virtual/poppler-glib-0.12.3-r2/repository /var/db/pkg/virtual/poppler-glib-0.12.3-r2/LDFLAGS /var/db/pkg/virtual/poppler-glib-0.12.3-r2/EAPI /var/db/pkg/virtual/poppler-glib-0.12.3-r2/CATEGORY /var/db/pkg/virtual/poppler-glib-0.12.3-r2/CBUILD /var/db/pkg/virtual/poppler-glib-0.12.3-r2/CXXFLAGS /var/db/pkg/virtual/poppler-glib-0.12.3-r2/CHOST
Re: [gentoo-user] poppler vs virtual/poppler eix-test-obsolete
On Sunday 14 February 2010 22:10:05 Mark Knecht wrote: Hi, Mostly in support of (I think) KDE I have poppler installed which seems to cause eix-test-obsolete a little indigestion. It sees virtual/poppler as installed but says they are not in the database. Do I have a problem here (eix-test-obsolete itself or my use of it, use flags, some sort of database problem, etc.) or is this some sort of ebuild problem that will likely get worked out over the next few weeks? I saw this a few days ago. virtual/poppler is not in portage anymore. We now just have regular poppler, xpdf, et al. Just remove poppler from world if you have it there - you shouldn't, it's a lib and should be pulled in by everything that DEPENDs on it. Latest masked portage deals with this kind of nonsense nicely. If you use an old portage, you may have to unmerge what you have and remerge the real one. FWIW, poppler is one of those packages seemingly run by an insane idiot. Every new minor point version seems to block the one before it, implying API/ABI breaks across minor versions. Which is thick beyond belief. It's a problematic package and one that I seemed to umerge/merge often in the pre-portage-2.2 days -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] poppler vs virtual/poppler eix-test-obsolete
On Sun, Feb 14, 2010 at 12:18 PM, Alan McKinnon alan.mckin...@gmail.com wrote: On Sunday 14 February 2010 22:10:05 Mark Knecht wrote: Hi, Mostly in support of (I think) KDE I have poppler installed which seems to cause eix-test-obsolete a little indigestion. It sees virtual/poppler as installed but says they are not in the database. Do I have a problem here (eix-test-obsolete itself or my use of it, use flags, some sort of database problem, etc.) or is this some sort of ebuild problem that will likely get worked out over the next few weeks? I saw this a few days ago. virtual/poppler is not in portage anymore. We now just have regular poppler, xpdf, et al. Just remove poppler from world if you have it there - you shouldn't, it's a lib and should be pulled in by everything that DEPENDs on it. Latest masked portage deals with this kind of nonsense nicely. If you use an old portage, you may have to unmerge what you have and remerge the real one. FWIW, poppler is one of those packages seemingly run by an insane idiot. Every new minor point version seems to block the one before it, implying API/ABI breaks across minor versions. Which is thick beyond belief. It's a problematic package and one that I seemed to umerge/merge often in the pre-portage-2.2 days -- alan dot mckinnon at gmail dot com Alan, poppler isn't in my world file: firefly ~ # cat /var/lib/portage/world | grep poppler firefly ~ # and I seem to be using the newest portage-2.2_rc62 although a slightly older portage-utils-0.2.1 Are you suggesting the I unmerge poppler and then do a revdep-rebuild (or emerge -DuN @world) to get it reinstalled without this problem? Easy enough if it works, but even if it works it seems something is brokern and before I destroy the symptom I thought I'd ask a couple of questions. I've read a couple of bug reports that echo your thoughts about the package. Thanks, Mark
Re: [gentoo-user] poppler vs virtual/poppler eix-test-obsolete
On 14 Feb 2010, at 20:31, Mark Knecht wrote: ... poppler isn't in my world file: ... Are you suggesting the I unmerge poppler and then do a revdep-rebuild (or emerge -DuN @world) to get it reinstalled without this problem? Yes. Stroller.
Re: [gentoo-user] poppler vs virtual/poppler eix-test-obsolete
On Sun, Feb 14, 2010 at 1:33 PM, Stroller strol...@stellar.eclipse.co.uk wrote: On 14 Feb 2010, at 20:31, Mark Knecht wrote: ... poppler isn't in my world file: ... Are you suggesting the I unmerge poppler and then do a revdep-rebuild (or emerge -DuN @world) to get it reinstalled without this problem? Yes. Stroller. Well, it's an interesting result, or I'm just getting tired. I really think that I tried emerge --depclean earlier and it didn't fix the problem. After emerge -C poppler/emerge poppler I was left with the same failure in eix-test-obsolete but this time emerge --depclean did get rid of the 4 virtuals. I don't know. I suspect now that I never did emerge --depclean. Thanks. It's fixed. Cheers, Mark
Re: [gentoo-user] poppler vs virtual/poppler eix-test-obsolete
On Monday 15 February 2010 00:04:21 Mark Knecht wrote: On Sun, Feb 14, 2010 at 1:33 PM, Stroller strol...@stellar.eclipse.co.uk wrote: On 14 Feb 2010, at 20:31, Mark Knecht wrote: ... poppler isn't in my world file: ... Are you suggesting the I unmerge poppler and then do a revdep-rebuild (or emerge -DuN @world) to get it reinstalled without this problem? Yes. Stroller. Well, it's an interesting result, or I'm just getting tired. I really think that I tried emerge --depclean earlier and it didn't fix the problem. After emerge -C poppler/emerge poppler I was left with the same failure in eix-test-obsolete but this time emerge --depclean did get rid of the 4 virtuals. I don't know. I suspect now that I never did emerge --depclean. Possibly. --depclean removed virtual/poppler here, leaving the real poppler package that was in place. FWIW, tinkering with poppler won't break anything much. It's just a pdf rendering library, not critical. If you remove it in error, emerge -1 will put it back :-) -- alan dot mckinnon at gmail dot com
