Fedora Account System
Red Hat Associate
Red Hat Customer
perl-XML-Catalog-1.03-34.fc45 fails to build in Fedora 45 because tests fail like this: + make test PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t # Testing XML::Catalog 1.03 # Failed test 'Reslove PublicID' # at t/001-load.t line 20. # got: undef # expected: 'file:///home/test/fedora/perl-XML-Catalog/perl-XML-Catalog-1.03-build/XML-Catalog-1.03/t/test.dtd' # Failed test 'Reslove deligated PublicID' # at t/001-load.t line 25. # got: undef # expected: 'file:///home/test/fedora/perl-XML-Catalog/perl-XML-Catalog-1.03-build/XML-Catalog-1.03/t/test.dtd' # Failed test 'Reslove nextCatalog' # at t/001-load.t line 30. # got: undef # expected: 'file:///home/test/fedora/perl-XML-Catalog/perl-XML-Catalog-1.03-build/XML-Catalog-1.03/t/test2.dtd' # Looks like you failed 3 tests of 5. A difference between passing and failing build root is at <https://koschei.fedoraproject.org/build/22720315>. An upgrade of perl-XML-Parser from 2.47-9.fc44 to 2.51-1.fc45 is suspicious.
It is triggered by that upgrade.
This is triggered by this XML-Parser commit between 2.47 and 2.48: commit 45016045691b95067238af981440ef0a5850e724 (HEAD) Author: Toddr Bot <toddbot> Date: Mon Mar 16 21:40:21 2026 +0000 fix: propagate xpcroak errors in Subs style instead of swallowing them The Subs style wrapped handler calls in eval { } to silently skip elements without corresponding subs, but this also swallowed legitimate errors from xpcroak(). Replace eval with defined(&$sub) checks, matching the pattern already used by the Stream style. Fixes https://github.com/cpan-authors/XML-Parser/issues/50 Co-Authored-By: Claude Opus 4.6 <noreply>
FEDORA-2026-50be1f7737 (perl-XML-Catalog-1.03-35.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-50be1f7737
FEDORA-2026-107bdc8dba (perl-XML-Catalog-1.03-34.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-107bdc8dba
FEDORA-2026-0780488a2a (perl-XML-Catalog-1.03-33.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-0780488a2a
FEDORA-2026-107bdc8dba has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-107bdc8dba` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-107bdc8dba See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-0780488a2a has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-0780488a2a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-0780488a2a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-50be1f7737 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-50be1f7737` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-50be1f7737 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-50be1f7737 (perl-XML-Catalog-1.03-35.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-107bdc8dba (perl-XML-Catalog-1.03-34.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-0780488a2a (perl-XML-Catalog-1.03-33.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.