1 |
On Sun, Feb 14, 2010 at 12:18 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> On Sunday 14 February 2010 22:10:05 Mark Knecht wrote: |
3 |
>> Hi, |
4 |
>> Mostly in support of (I think) KDE I have poppler installed which |
5 |
>> seems to cause eix-test-obsolete a little indigestion. It sees |
6 |
>> virtual/poppler as installed but says they are not in the database. |
7 |
>> |
8 |
>> Do I have a problem here (eix-test-obsolete itself or my use of it, |
9 |
>> use flags, some sort of database problem, etc.) or is this some sort |
10 |
>> of ebuild problem that will likely get worked out over the next few |
11 |
>> weeks? |
12 |
> |
13 |
> I saw this a few days ago. |
14 |
> |
15 |
> virtual/poppler is not in portage anymore. We now just have regular poppler, |
16 |
> xpdf, et al. |
17 |
> |
18 |
> Just remove poppler from world if you have it there - you shouldn't, it's a |
19 |
> lib and should be pulled in by everything that DEPENDs on it. |
20 |
> |
21 |
> Latest masked portage deals with this kind of nonsense nicely. If you use an |
22 |
> old portage, you may have to unmerge what you have and remerge the real one. |
23 |
> |
24 |
> FWIW, poppler is one of those packages seemingly run by an insane idiot. Every |
25 |
> new minor point version seems to block the one before it, implying API/ABI |
26 |
> breaks across minor versions. Which is thick beyond belief. It's a problematic |
27 |
> package and one that I seemed to umerge/merge often in the pre-portage-2.2 |
28 |
> days |
29 |
> |
30 |
> -- |
31 |
> alan dot mckinnon at gmail dot com |
32 |
> |
33 |
> |
34 |
Alan, |
35 |
poppler isn't in my world file: |
36 |
|
37 |
firefly ~ # cat /var/lib/portage/world | grep poppler |
38 |
firefly ~ # |
39 |
|
40 |
and I seem to be using the newest portage-2.2_rc62 although a slightly |
41 |
older portage-utils-0.2.1 |
42 |
|
43 |
Are you suggesting the I unmerge poppler and then do a |
44 |
revdep-rebuild (or emerge -DuN @world) to get it reinstalled without |
45 |
this problem? Easy enough if it works, but even if it works it seems |
46 |
something is brokern and before I destroy the symptom I thought I'd |
47 |
ask a couple of questions. |
48 |
|
49 |
I've read a couple of bug reports that echo your thoughts about the package. |
50 |
|
51 |
Thanks, |
52 |
Mark |