Re: [SOLVED] [gentoo-user] poppler-0.32.0 - error

[Fernando Rodriguez <frodriguez.developer@outlook.com>]

On Saturday, September 05, 2015 12:46:02 PM thelma@sys-concept.com wrote:
> On 09/05/2015 12:23 PM, Alan McKinnon wrote:
> > On 05/09/2015 20:17, thelma@sys-concept.com wrote:
> >> I'm trying to re-emerge  poppler but I'm getting error message
> >> Here is the message log: 
> >> http://pastebin.com/Q5EKLW8U
> > 
> > Don't use pastebin here. It's considered rude.
> > Post the relevant portion of the error.
> 
> Apology about it. I was under impression it might look cleaner (less
> clapper if I post a link to complete log).
> 
> > I did look at it though, and it's full of jpeg errors. So you need to go
> > back to your very first post on this subject about a week ago and follow
> > the advice there, not some other variant of your own invention.
> 
> Yes, that was correct hint.
> Fernando was correct, running:
> media-libs/tiff
> perl-cleaner --all

I was right that rebuilding libtiff (not perl-cleaner) will get you past that 
ebuild, but my advice was the same you just received, go back to the *VERY 
FIRST* post on the subject and fix the root of the problem. You will see that 
error again (or worse runtime errors) until you fix it.

Hint: It was Alan that gave you the solution. You chose to fix it by installing 
an incompatible jpeg implementation. That needs to be undone.

> seem to solve this problem.
> 
> > 
> > 
> >>
> >> I've tried to run: 
> >> perl-cleaner --all (but that did not solve anything)
> >>
> >>  * Finding left over modules and header
> >>
> >>  * The following files remain. These were either installed by hand
> >>  * or edited. This script cannot deal with them.
> >>
> >> /usr/lib64/perl5/5.12.4/x86_64-linux/Encode/ConfigLocal.pm
> >> /usr/lib64/perl5/vendor_perl/5.12.4/XML/SAX/ParserDetails.ini
> >> /usr/lib64/perl5/vendor_perl/5.18.2/XML/SAX/ParserDetails.ini
> >> /usr/lib64/perl5/vendor_perl/5.16.3/XML/SAX/ParserDetails.ini
> > 
> > Read the message. Either you put them there yourself (using cpan or
> > such), or the files were edited since being installed. Either way, the
> > script is refusing to touch them (wisely)
> > 
> > Those files are ancient and not needed. Delete them, and all empty
> > parent directories
> 
> I'll look into it.
> 
> Thelma
> 

-- 
Fernando Rodriguez