From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [SOLVED] [gentoo-user] poppler-0.32.0 - error
Date: Sat, 5 Sep 2015 21:57:26 +0200 [thread overview]
Message-ID: <55EB4926.1070402@gmail.com> (raw)
In-Reply-To: <55EB386A.8020401@sys-concept.com>
On 05/09/2015 20:46, 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
>
> 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.
There's nothing to look into. There are no perl versions earlier than
2.20 in the tree so those files can never be used. They are old cruft.
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2015-09-05 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 18:17 [gentoo-user] poppler-0.32.0 - error thelma
2015-09-05 18:23 ` Alan McKinnon
2015-09-05 18:46 ` thelma
2015-09-05 19:57 ` Alan McKinnon [this message]
2015-09-05 20:30 ` [SOLVED] " Fernando Rodriguez
2015-09-05 20:52 ` thelma
2015-09-05 21:19 ` Fernando Rodriguez
2015-09-06 18:21 ` thelma
2015-09-06 19:40 ` Fernando Rodriguez
2015-09-06 20:08 ` Fernando Rodriguez
2015-09-07 0:14 ` thelma
2015-09-07 1:18 ` Fernando Rodriguez
2015-09-07 0:25 ` thelma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55EB4926.1070402@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox