#451 rpmdeplint test for F39 failed because an F40 (Rawhide) package would upgrade it
Opened by adamwill. Modified

This result seems weird: https://artifacts.dev.testing-farm.io/b70ebdb9-9b37-4404-abe5-882a40d8602b/ (from https://bodhi.fedoraproject.org/updates/FEDORA-2023-6f9de4d282 ).

The errors are:

Upgrade problems:
python3-sqlalchemy_schemadisplay-1.4.dev0-6.fc39.noarch would be upgraded by python3-sqlalchemy_schemadisplay-1.4.dev0-6.fc40.noarch from repo fedora-buildroot-40-x86_64

and:

Undeclared file conflicts:
python3-sqlalchemy_schemadisplay-1.4.dev0-6.fc39.noarch provides /usr/lib/python3.12/site-packages/sqlalchemy_schemadisplay-1.4.dev0.dist-info/WHEEL which is also provided by python3-sqlalchemy_schemadisplay-1.4.dev0-6.fc40.noarch

why is it including a repo with F40 (Rawhide) packages in it when testing an F39 update? Is there a "version XX is Rawhide" check somewhere which was never updated when F39 branched?


Another instance with perl-XS-Parse-Keyword-0.39-2.fc39 https://artifacts.dev.testing-farm.io/b0a58244-432a-4ed7-9517-c2f88f807ded/:

Upgrade problems:
perl-XS-Parse-Keyword-Builder-0.39-2.fc39.x86_64 would be upgraded by perl-XS-Parse-Keyword-Builder-0.39-2.fc40.x86_64 from repo fedora-buildroot-40-x86_64
perl-XS-Parse-Keyword-tests-0.39-2.fc39.x86_64 would be upgraded by perl-XS-Parse-Keyword-tests-0.39-2.fc40.x86_64 from repo fedora-buildroot-40-x86_64
perl-XS-Parse-Keyword-0.39-2.fc39.x86_64 would be upgraded by perl-XS-Parse-Keyword-0.39-2.fc40.x86_64 from repo fedora-buildroot-40-x86_64

This happens for F38 updates too https://bodhi.fedoraproject.org/updates/FEDORA-2024-b9de8240fb:

Upgrade problems:
perl-URI-NamespaceMap-1.12-1.fc38.noarch would be upgraded by perl-URI-NamespaceMap-1.12-1.fc40.noarch from repo fedora-buildroot-40-x86_64
perl-URI-NamespaceMap-tests-1.12-1.fc38.noarch would be upgraded by perl-URI-NamespaceMap-tests-1.12-1.fc40.noarch from repo fedora-buildroot-40-x86_64

The test isn't ready for non-Rawhide releases.

Reverted: https://github.com/fedora-ci/rpmdeplint-trigger/pull/4

Thanks :(

Is the rpmdeplint issue tracked somwhere?

Metadata