From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] how to tell catalyst to resolve dependency, dev-perl/xml-parser
Date: Sat, 28 Dec 2013 06:54:28 -0500 [thread overview]
Message-ID: <201312280654.29737.vapier@gentoo.org> (raw)
In-Reply-To: <1388211068.24088.3.camel@big_daddy.dol-sen.ca>
[-- Attachment #1: Type: Text/Plain, Size: 2042 bytes --]
On Saturday 28 December 2013 01:11:08 Brian Dolbec wrote:
> On Fri, 2013-12-27 at 21:37 -0500, Mike Frysinger wrote:
> > On Friday 27 December 2013 21:11:44 lin pro wrote:
> > > checking for XML::Parser... configure: error: XML::Parser perl module
> > > is required for intltool
> >
> > most likely the perl module is installed, but broken. it needs to be
> > rebuilt.
> >
> > look at the config.log file the log referred you to to see the exact error:
> > > !!! Please attach the following file when seeking support:
> > > !!!
> > > /var/tmp/portage/gnome-base/libgnomecanvas-2.30.3/work/libgnomecanvas-2
> > > .30 .3/config.log
>
> This exact breakage has been coming up in gentoo systems for the last
> few weeks. There was a perl upgrade or many that broke it. Running
> perl-cleaner --reallyall fixes it.
>
> I don't know if catalyst can do that or not and whether it can detect it
> to run perl-cleaner.
catalyst certainly could grow code for handling perl-cleaner & friends. but
i'm not sure if it makes sense. if stage3->stage4 is seeing a perl upgrade,
then it could be via different routes:
- your stage3 is outdated; solution: upgrade your stage3 to a recent one
- you're manually forcing a perl upgrade by modifying the list of accepted
keywords (either KEYOWRDS or package.keywords or something else)
- i don't think this comes up in the stage1->stage2->stage3 transition due to
how those each occur (a fresh ROOT build and then chroot and upgrade and such)
this second one is a reasonable use case, but detecting & supporting it might
be kind of pain w/out deploying specific checks. like doing a pretend emerge
and analyzing the resulting list of upgrades. is a perl upgrade found ? if
so, manually upgrade perl, then run perl-cleaner, then move on to the next
step. is a python upgrade found ? if so, manually upgrade python, then run
python-cleaner, then move on to the next step. all various upgrades run ? do
a general @world/@system update then.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-28 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 2:11 [gentoo-catalyst] how to tell catalyst to resolve dependency, dev-perl/xml-parser lin pro
2013-12-28 2:37 ` Mike Frysinger
2013-12-28 6:11 ` Brian Dolbec
2013-12-28 11:54 ` Mike Frysinger [this message]
2013-12-28 16:05 ` W. Trevor King
2013-12-28 17:00 ` Brian Dolbec
2013-12-30 0:12 ` lin pro
2013-12-30 7:42 ` Mike Frysinger
2013-12-28 2:44 ` W. Trevor King
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=201312280654.29737.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-catalyst@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