1 |
On Saturday, September 05, 2015 2:52:03 PM thelma@×××××××××××.com wrote: |
2 |
> On 09/05/2015 02:30 PM, Fernando Rodriguez wrote: |
3 |
> > On Saturday, September 05, 2015 12:46:02 PM thelma@×××××××××××.com wrote: |
4 |
> >> On 09/05/2015 12:23 PM, Alan McKinnon wrote: |
5 |
> >>> On 05/09/2015 20:17, thelma@×××××××××××.com wrote: |
6 |
> >>>> I'm trying to re-emerge poppler but I'm getting error message |
7 |
> >>>> Here is the message log: |
8 |
> >>>> http://pastebin.com/Q5EKLW8U |
9 |
> >>> |
10 |
> >>> Don't use pastebin here. It's considered rude. |
11 |
> >>> Post the relevant portion of the error. |
12 |
> >> |
13 |
> >> Apology about it. I was under impression it might look cleaner (less |
14 |
> >> clapper if I post a link to complete log). |
15 |
> >> |
16 |
> >>> I did look at it though, and it's full of jpeg errors. So you need to go |
17 |
> >>> back to your very first post on this subject about a week ago and follow |
18 |
> >>> the advice there, not some other variant of your own invention. |
19 |
> >> |
20 |
> >> Yes, that was correct hint. |
21 |
> >> Fernando was correct, running: |
22 |
> >> media-libs/tiff |
23 |
> >> perl-cleaner --all |
24 |
> > |
25 |
> > I was right that rebuilding libtiff (not perl-cleaner) will get you past |
26 |
that |
27 |
> > ebuild, but my advice was the same you just received, go back to the *VERY |
28 |
> > FIRST* post on the subject and fix the root of the problem. You will see |
29 |
that |
30 |
> > error again (or worse runtime errors) until you fix it. |
31 |
> > |
32 |
> > Hint: It was Alan that gave you the solution. You chose to fix it by |
33 |
installing |
34 |
> > an incompatible jpeg implementation. That needs to be undone. |
35 |
> |
36 |
> It seems to me Alan solution: |
37 |
> emerge -avC libjpeg-turbo |
38 |
> emerge -av1 media-libs/jpeg:0 media-libs/jpeg:62 |
39 |
> |
40 |
> It will come to hunt me. It allow me to keep going with upgrades as I |
41 |
> couldn't find any better solution. |
42 |
> |
43 |
> Currently I have media-libs/jpeg installed in two slots: |
44 |
> media-libs/jpeg-6b-r12:62 |
45 |
> media-libs/jpeg-8d-r1:0 |
46 |
> |
47 |
> I can not get rid of "media-libs/jpeg-6b-r12" due to dependency |
48 |
> net-misc/nxclient-3.5.0.7 (=media-libs/jpeg-6*) |
49 |
> |
50 |
> I need "nxclient" for now until I find better solution. |
51 |
> |
52 |
> According to: equery d media-libs/jpeg-8d-r1 |
53 |
> * These packages depend on media-libs/jpeg-8d-r1: |
54 |
> virtual/jpeg-0-r2 (>=media-libs/jpeg-8d-r1:0 |
55 |
> |
56 |
> Maybe I could uninstall jpeg-8d-r1 as only "virtual/jpeg-0-r2" depends |
57 |
> on it. |
58 |
> |
59 |
> Thelma |
60 |
> |
61 |
|
62 |
That was your own solution. You have a few ways to solve it. |
63 |
|
64 |
1. Grab the last version of nxclient from the gentoo attic (or from |
65 |
/var/db/pkg/net-misc/nxclient if it doesn't need any files to build) change the |
66 |
dependency to virtual/jpeg, put it on a local overlay and re-emerge it (after |
67 |
replacing libjpeg with libjpeg-turbo again) |
68 |
|
69 |
2. Rebuild everything that depends on libjpeg on the right order. Something |
70 |
like (I have not tested this command, but it may build stuff you don't have |
71 |
installed, hence the --depclean, maybe somebody can give you a better one): |
72 |
|
73 |
# emerge --oneshot `equery depends virtual/jpeg` |
74 |
# emerge --depclean --ask |
75 |
|
76 |
3. This is a hack and I've never done it. In /var/db/pkg/net-misc/nxclient |
77 |
update all media-libs/jpeg to the virtual/jpeg. Then unmerge all media- |
78 |
libs/jpeg slots and emerge libjpeg turbo. This should work because anything |
79 |
linked against jpeg *should* work with jpeg-turbo but not the other way |
80 |
around. |
81 |
|
82 |
-- |
83 |
Fernando Rodriguez |