This is a re-hashing of the seperate bug, #41124, to track all the bugs that form indirectly from this problem. The general problem is: X -> intltool -> dev-perl/XML-Parser -> perl As per the lengthy description in the similar bug, #592880 1. Perl upgrades 2. XML-Parser enters a "broken state" which is equivalent to "missing" from perl's perspective 3. Portage does not recognize that XML-Parser is now "missing" 4. Portage assumes intltool still works 5. Portage tries to compile something using intltool, and dies because XML-Parser is missing. The death path is usually either in per-dependent configure stage via intltools '.m4' /usr/share/aclocal/intltool.m4: AC_MSG_CHECKING([for XML::Parser]) /usr/share/aclocal/intltool.m4: if `$INTLTOOL_PERL -e "require XML::Parser" 2>/dev/null`; then /usr/share/aclocal/intltool.m4: AC_MSG_ERROR([XML::Parser perl module is required for intltool]) Or via invoking intltool and having it fail: /usr/bin/intltool-merge: my $ret = eval 'require XML::Parser'; /usr/bin/intltool-merge: die "You must have XML::Parser installed to run $0\n\n"; /usr/bin/intltool-extract: my $ret = eval 'require XML::Parser'; /usr/bin/intltool-extract: die "You must have XML::Parser installed to run $0\n\n"; intltool's dependencies are already correct: - Perl is in both DEPEND and RDEPEND - XML-Parser is in both DEPEND and RDEPEND - intltool does not itself link against perl.so or contain any libraries with perl-ABI-version specific paths, so subslot deps are not warranted. The only solution left that we know of is for portage to work out how to pull this dependency when it should, and encourage all users experiencing this issue to sprinkle --with-bdeps=y into their stuff judiciously.
*** Bug 596640 has been marked as a duplicate of this bug. ***
*** Bug 584848 has been marked as a duplicate of this bug. ***
*** Bug 570460 has been marked as a duplicate of this bug. ***
*** Bug 563810 has been marked as a duplicate of this bug. ***
(In reply to Kent Fredric (IRC: kent\n) from comment #0) [...] > 1. Perl upgrades > 2. XML-Parser enters a "broken state" which is equivalent to "missing" from > perl's perspective > 3. Portage does not recognize that XML-Parser is now "missing" > 4. Portage assumes intltool still works > 5. Portage tries to compile something using intltool, and dies because > XML-Parser is missing. Shouldn't portage try to rebuild as soon as possible xml-parser (listed as RDEPEND in intltool) to try to solve the breakage as soon as possible? :/
It (In reply to Pacho Ramos from comment #5) > (In reply to Kent Fredric (IRC: kent\n) from comment #0) > [...] > > 1. Perl upgrades > > 2. XML-Parser enters a "broken state" which is equivalent to "missing" from > > perl's perspective > > 3. Portage does not recognize that XML-Parser is now "missing" > > 4. Portage assumes intltool still works > > 5. Portage tries to compile something using intltool, and dies because > > XML-Parser is missing. > > Shouldn't portage try to rebuild as soon as possible xml-parser (listed as > RDEPEND in intltool) to try to solve the breakage as soon as possible? :/ It *should*, but it doesn't. Bug #463976 and bug #199856 are portage bugs for things we *believe* resolution of will mitigate this problem, but we won't know for sure until that happens. When you read those bugs, the broad nature of this problem is uh, rather scary. Its really surprising we didn't note this sooner.
Though I'm having a hard time identifying the cycle (if any) that is causing this issue. The only possible cycle I see so far is: intltool -> XML-Parser -> perl -> sys-libs/db -> virtual/jdk -> icedtea-bin -> dev-java/icedtea-sound -> media-sound/pulseaudio -> intltool And I *really* doubt that's what's tripping portage.
*** Bug 611224 has been marked as a duplicate of this bug. ***
*** Bug 612512 has been marked as a duplicate of this bug. ***
*** Bug 616822 has been marked as a duplicate of this bug. ***
*** Bug 620870 has been marked as a duplicate of this bug. ***
*** Bug 628982 has been marked as a duplicate of this bug. ***
*** Bug 629220 has been marked as a duplicate of this bug. ***
*** Bug 629218 has been marked as a duplicate of this bug. ***
*** Bug 629216 has been marked as a duplicate of this bug. ***
(In reply to Kent Fredric (IRC: kent\n) from comment #7) > Though I'm having a hard time identifying the cycle (if any) that is causing > this issue. > > The only possible cycle I see so far is: > > intltool -> XML-Parser -> perl -> sys-libs/db -> virtual/jdk -> icedtea-bin > -> dev-java/icedtea-sound -> media-sound/pulseaudio -> intltool > > And I *really* doubt that's what's tripping portage. That sounds a likely candidate as I only recall hitting this problem on systems with icedtea-bin installed. It may be unrelated but I have seen other weirdness around Portage's handling of virtual/jdk before.
*** Bug 628988 has been marked as a duplicate of this bug. ***
*** Bug 637396 has been marked as a duplicate of this bug. ***
FWIW I did no longer hit this at my tinderbox so I removed a special quirk for this bug for now from teh script.
*** Bug 655998 has been marked as a duplicate of this bug. ***
*** Bug 660352 has been marked as a duplicate of this bug. ***
*** Bug 667886 has been marked as a duplicate of this bug. ***
(In reply to Toralf Förster from comment #19) > FWIW I did no longer hit this at my tinderbox so I removed a special quirk > for this bug for now from teh script. happened again today at 17.1_systemd-libressl-20190919-191611- re-adding the quirk: checking for perl >= 5.8.1... 5.30.0 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.10-r1/work/shared-mime-info-1.10/config.log for x11-misc/shared-mime-info-1.10-r1
*** Bug 704078 has been marked as a duplicate of this bug. ***
*** Bug 708610 has been marked as a duplicate of this bug. ***
*** Bug 704080 has been marked as a duplicate of this bug. ***
*** Bug 754432 has been marked as a duplicate of this bug. ***
*** Bug 796716 has been marked as a duplicate of this bug. ***
*** Bug 800188 has been marked as a duplicate of this bug. ***
*** Bug 828114 has been marked as a duplicate of this bug. ***
*** Bug 832333 has been marked as a duplicate of this bug. ***
*** Bug 838112 has been marked as a duplicate of this bug. ***
seems still be the case: checking for perl >= 5.8.1... 5.36.0 checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool
*** Bug 835794 has been marked as a duplicate of this bug. ***
*** Bug 854693 has been marked as a duplicate of this bug. ***
*** Bug 787383 has been marked as a duplicate of this bug. ***
*** Bug 504480 has been marked as a duplicate of this bug. ***
*** Bug 870052 has been marked as a duplicate of this bug. ***
Is it possible to add dev-perl/XML-Parser as a dependency ? In the ebuilds where it requires it like in libxfce4uitl where the installation completely breaks, obviously we can emerge dev-perl/XML-Parser and then emerge anything that needs it.
(In reply to Sid from comment #39) > Is it possible to add dev-perl/XML-Parser as a dependency ? In the ebuilds > where it requires it like in libxfce4uitl where the installation completely > breaks, obviously we can emerge dev-perl/XML-Parser and then emerge anything > that needs it. All the relevant packages do depend on it, though. Adding a redundant dependency is unlikely to help.
