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
signature.asc
Description: This is a digitally signed message part.
