[gentoo-user] x11-misc/shared-mime-info update problem...

[gentoo-user] x11-misc/shared-mime-info update problem...

[Jarry]

Hi Gentoo-users,

while trying to update my box I ran into some problem with
x11-misc/shared-mime-info (updating from 1.0 to 1.2-r1).
Maybe someone could help me to understand what the problem is.

I see it failed in config-phase with:
"error: XML::Parser perl module is required for intltool"

But why was XML::Parser not pulled as dependency, when it
is required? What ebuild is it in?

Jarry

_____________________________________________________________
 >>> Emerging (1 of 14) x11-misc/shared-mime-info-1.2-r1
  * shared-mime-info-1.2.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... 
   [ ok ]
 >>> Unpacking source...
 >>> Unpacking shared-mime-info-1.2.tar.xz to 
/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/work
 >>> Source unpacked in 
/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/work
 >>> Preparing source in 
/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/work/shared-mime-info-1.2 
...
  * Applying shared-mime-info-1.2-g_type_init.patch ... 
   [ ok ]
 >>> Source prepared.
 >>> Configuring source in 
/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/work/shared-mime-info-1.2 
...
./configure --prefix=/usr --build=x86_64-pc-linux-gnu 
--host=x86_64-pc-linux-gnu --mandir=/usr/share/man 
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc 
--localstatedir=/var/lib --libdir=/usr/lib64 --disable-silent-rules 
--disable-dependency-tracking --disable-default-make-check 
--disable-update-mimedb
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of x86_64-pc-linux-gnu-gcc... none
checking for an ANSI C-conforming const... yes
checking whether NLS is requested... yes
checking for intltool >= 0.35.0... 0.50.2 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/gmsgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.16.3
checking for XML::Parser... configure: error: XML::Parser perl module is 
required for intltool

!!! Please attach the following file when seeking support:
!!! 
/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/work/shared-mime-info-1.2/config.log
  * ERROR: x11-misc/shared-mime-info-1.2-r1::gentoo failed (configure 
phase):
  *   econf failed
  *
  * Call stack:
  *          ebuild.sh, line   93:  Called src_configure
  *        environment, line 2173:  Called econf 
'--disable-default-make-check' '--disable-update-mimedb'
  *   phase-helpers.sh, line  577:  Called die
  * The specific snippet of code:
  *                      die "econf failed"
  *
  * If you need support, post the output of `emerge --info 
'=x11-misc/shared-mime-info-1.2-r1::gentoo'`,
  * the complete build log and the output of `emerge -pqv 
'=x11-misc/shared-mime-info-1.2-r1::gentoo'`.
  * The complete build log is located at 
'/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/temp/build.log'.
  * The ebuild environment file is located at 
'/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/temp/environment'.
  * Working directory: 
'/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/work/shared-mime-info-1.2'
  * S: 
'/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/work/shared-mime-info-1.2'

 >>> Failed to emerge x11-misc/shared-mime-info-1.2-r1, Log file:

 >>>  '/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/temp/build.log'

  * Messages for package x11-misc/shared-mime-info-1.2-r1:

  * ERROR: x11-misc/shared-mime-info-1.2-r1::gentoo failed (configure 
phase):
  *   econf failed
  *
  * Call stack:
  *          ebuild.sh, line   93:  Called src_configure
  *        environment, line 2173:  Called econf 
'--disable-default-make-check' '--disable-update-mimedb'
  *   phase-helpers.sh, line  577:  Called die
  * The specific snippet of code:
  *                      die "econf failed"
  *
  * If you need support, post the output of `emerge --info 
'=x11-misc/shared-mime-info-1.2-r1::gentoo'`,
  * the complete build log and the output of `emerge -pqv 
'=x11-misc/shared-mime-info-1.2-r1::gentoo'`.
  * The complete build log is located at 
'/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/temp/build.log'.
  * The ebuild environment file is located at 
'/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/temp/environment'.
  * Working directory: 
'/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/work/shared-mime-info-1.2'
  * S: 
'/var/tmp/portage/x11-misc/shared-mime-info-1.2-r1/work/shared-mime-info-1.2'
#

-- 
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.

Re: [gentoo-user] x11-misc/shared-mime-info update problem...

[Pavel Kazakov]

On 01/05/2014 04:32 AM, Jarry wrote:
> Hi Gentoo-users,
>
> while trying to update my box I ran into some problem with
> x11-misc/shared-mime-info (updating from 1.0 to 1.2-r1).
> Maybe someone could help me to understand what the problem is.
>
> I see it failed in config-phase with:
> "error: XML::Parser perl module is required for intltool"
>
> But why was XML::Parser not pulled as dependency, when it
> is required? What ebuild is it in?
>
> Jarry

The proper dependency should be pulled in (x11-misc/shared-mime-info
depends on dev-util/intltool, which depends on dev-perl/XML-Parser).

My guess is that you recently upgraded perl, which might require you to
rebuild the perl modules. You can try rebuilding just
dev-perl/XML-Parser, but I recommend using perl-cleaner [1] to rebuild
all the modules:
    perl-cleaner --allmodules -v

And then try to rebuild shared-mime-info.

Regards,
Pavel

[1] http://www.gentoo.org/proj/en/perl/perl-cleaner.xml

Re: [gentoo-user] x11-misc/shared-mime-info update problem...

[Jarry]

On 05-Jan-14 13:48, Pavel Kazakov wrote:
> On 01/05/2014 04:32 AM, Jarry wrote:
>>  ...
>> I see it failed in config-phase with:
>> "error: XML::Parser perl module is required for intltool"
>
> The proper dependency should be pulled in (x11-misc/shared-mime-info
> depends on dev-util/intltool, which depends on dev-perl/XML-Parser).
>
> My guess is that you recently upgraded perl, which might require you to
> rebuild the perl modules. You can try rebuilding just
> dev-perl/XML-Parser, but I recommend using perl-cleaner [1] to rebuild
> all the modules:
>      perl-cleaner --allmodules -v
>
> And then try to rebuild shared-mime-info.

You are right and this fixed my problem. Thanks! I really updated
perl recently but I did not know I had to run perl-cleaner. Never
heard of it. Should not it be done automaticaly, always after new
perl version has been installed?

Jarry

-- 
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.

Re: [gentoo-user] x11-misc/shared-mime-info update problem...

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

On Sun, 05 Jan 2014 14:06:31 +0100, Jarry wrote:

> You are right and this fixed my problem. Thanks! I really updated
> perl recently but I did not know I had to run perl-cleaner. Never
> heard of it. Should not it be done automaticaly, always after new
> perl version has been installed?

Did ou not see this n the elog message from Perl?

UPDATE THE PERL MODULES:
After updating dev-lang/perl you must reinstall
the installed perl modules.
Use: perl-cleaner --all


-- 
Neil Bothwick

Reboot America.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] x11-misc/shared-mime-info update problem...

[Jarry]

On 05-Jan-14 15:02, Neil Bothwick wrote:
> On Sun, 05 Jan 2014 14:06:31 +0100, Jarry wrote:
>
>> You are right and this fixed my problem. Thanks! I really updated
>> perl recently but I did not know I had to run perl-cleaner. Never
>> heard of it. Should not it be done automaticaly, always after new
>> perl version has been installed?
>
> Did ou not see this n the elog message from Perl?
>
> UPDATE THE PERL MODULES:
> After updating dev-lang/perl you must reinstall
> the installed perl modules.
> Use: perl-cleaner --all

Well, I tested it on another computer and the problem is
perl and shared-mime-info are updated at the same update-run.
So I can find this message *after* update of shared-mime-info
already crashed. And I have to scroll way back to see any
perl-related messages...

Jarry


-- 
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.

Re: [gentoo-user] x11-misc/shared-mime-info update problem...

[Tanstaafl]

On 2014-01-05 9:24 AM, Jarry <mr.jarry@gmail.com> wrote:
> Well, I tested it on another computer and the problem is
> perl and shared-mime-info are updated at the same update-run.
> So I can find this message *after* update of shared-mime-info
> already crashed. And I have to scroll way back to see any
> perl-related messages..

You don't email yourself all of the emerge logs, so you don't have to 
worry about missing these kinds of messages?

I honestly can't see how anyone can reliably keep a gentoo system up to 
date without doing that...

Re: [gentoo-user] x11-misc/shared-mime-info update problem...

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 717 bytes --]

On Sun, 05 Jan 2014 15:24:49 +0100, Jarry wrote:

> > Did you not see this n the elog message from Perl?
> >
> > UPDATE THE PERL MODULES:
> > After updating dev-lang/perl you must reinstall
> > the installed perl modules.
> > Use: perl-cleaner --all  
> 
> Well, I tested it on another computer and the problem is
> perl and shared-mime-info are updated at the same update-run.
> So I can find this message *after* update of shared-mime-info
> already crashed. And I have to scroll way back to see any
> perl-related messages...

I never rely on seeing the messages in a termnal and always have elogs
mailed to me.


-- 
Neil Bothwick

The quickest way to a man's heart is through his sternum.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] x11-misc/shared-mime-info update problem...

[Alan McKinnon]

On 05/01/2014 16:24, Jarry wrote:
> On 05-Jan-14 15:02, Neil Bothwick wrote:
>> On Sun, 05 Jan 2014 14:06:31 +0100, Jarry wrote:
>>
>>> You are right and this fixed my problem. Thanks! I really updated
>>> perl recently but I did not know I had to run perl-cleaner. Never
>>> heard of it. Should not it be done automaticaly, always after new
>>> perl version has been installed?
>>
>> Did ou not see this n the elog message from Perl?
>>
>> UPDATE THE PERL MODULES:
>> After updating dev-lang/perl you must reinstall
>> the installed perl modules.
>> Use: perl-cleaner --all
> 
> Well, I tested it on another computer and the problem is
> perl and shared-mime-info are updated at the same update-run.
> So I can find this message *after* update of shared-mime-info
> already crashed. And I have to scroll way back to see any
> perl-related messages...


As Neil and Charles already said, mail the elogs to yourself. Or you can
adjust the various LOG settings in make.conf and view the entries with
elogv (cli app) or elogviewer (qt gui app) or just less them - they are
in /var/log/portage/elog/


But all of this is CLEARLY laid out in one of the most important man
files you have - man 5 make.conf. Why have you not read it?


Do yourself a big favour and before you touch anything else on a Gentoo
system, do this. It will save you heaps of pain:

man emerge
man 5 portage
man 5 ebuild
man 5 make.conf

make sure you understand everything in there.


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] x11-misc/shared-mime-info update problem...

[Alan McKinnon]

On 05/01/2014 15:06, Jarry wrote:
> On 05-Jan-14 13:48, Pavel Kazakov wrote:
>> On 01/05/2014 04:32 AM, Jarry wrote:
>>>  ...
>>> I see it failed in config-phase with:
>>> "error: XML::Parser perl module is required for intltool"
>>
>> The proper dependency should be pulled in (x11-misc/shared-mime-info
>> depends on dev-util/intltool, which depends on dev-perl/XML-Parser).
>>
>> My guess is that you recently upgraded perl, which might require you to
>> rebuild the perl modules. You can try rebuilding just
>> dev-perl/XML-Parser, but I recommend using perl-cleaner [1] to rebuild
>> all the modules:
>>      perl-cleaner --allmodules -v
>>
>> And then try to rebuild shared-mime-info.
> 
> You are right and this fixed my problem. Thanks! I really updated
> perl recently but I did not know I had to run perl-cleaner. Never
> heard of it. Should not it be done automaticaly, always after new
> perl version has been installed?
> 
> Jarry
> 



perl ebuilds up to and including 5.14.2 used to give you an ewarn() that
said to run perl-cleaner, and how to do it. I see it's missing from the
5.16 series of ebuilds.

I didn't look into it too closely, but I would consider this a bug.
There is no easy way to just quickly discover that a module is built for
a previously installed version of perl - you can poke around in
/usr/lib/perl5/<version>/XML/Parser but that's not exactly easy to use.
And the failures are mysterious and hard to understand.

You might want to file a bug at b.g.o. about the lack of messages at the
end of a perl install.

The reason it is not done automatically is that it's a huge job. the
scripts has to find every perl module it can, check the version it is
built against and decide if it needs to be rebuilt then emerge it. This
can easily be 50-100 packages or more and can take longer than to build
firefox. Portage can't figure this out when emerging perl that's why it
doesn't do it, it is left to you to do manually. Same with python.

Golden rule:

When updating perl or python and a version change occurs, take note and
always run perl-cleaner or python-updater afterwards.

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] x11-misc/shared-mime-info update problem...

[Peter Humphrey]

On Sunday 05 Jan 2014 16:15:31 Alan McKinnon wrote:

> Golden rule:
> 
> When updating perl or python and a version change occurs, take note and
> always run perl-cleaner or python-updater afterwards.

Sage advice indeed. And if you're really paranoid, run python-updater before 
perl-cleaner in case the way portage operates has been affected. Well, it may 
make no difference really but that's what I do.

-- 
Regards
Peter