Description of problem: In Fedora CoreOS we have a CI test that runs: ``` rpm-ostree ex module install cri-o:1.22/default nginx:mainline ``` It's failing with: ``` Problem: package nginx-all-modules-1:1.21.6-2.module_f37+14558+cc7c60ae.noarch requires nginx-mod-http-perl = 1:1.21.6-2.module_f37+14558+cc7c60ae, but none of the providers can be installed - package nginx-mod-http-perl-1:1.21.6-2.module_f37+14558+cc7c60ae.x86_64 requires libperl.so.5.34()(64bit), but none of the providers can be installed - package nginx-mod-http-perl-1:1.21.6-2.module_f37+14558+cc7c60ae.x86_64 requires perl(:MODULE_COMPAT_5.34.1), but none of the providers can be installed - conflicting requests - package perl-libs-4:5.34.1-486.module_f37+14419+7d39a4ba.x86_64 is filtered out by modular filtering ``` Running via dnf in a container fails in a similar way: ``` [root@528d054ce93e /]# dnf module install nginx:mainline Last metadata expiration check: 0:00:39 ago on Tue Jun 14 13:44:41 2022. Error: Problem: package nginx-all-modules-1:1.21.6-2.module_f37+14558+cc7c60ae.noarch requires nginx-mod-http-perl = 1:1.21.6-2.module_f37+14558+cc7c60ae, but none of the providers can be installed - package nginx-mod-http-perl-1:1.21.6-2.module_f37+14558+cc7c60ae.x86_64 requires perl(:MODULE_COMPAT_5.34.1), but none of the providers can be installed - package nginx-mod-http-perl-1:1.21.6-2.module_f37+14558+cc7c60ae.x86_64 requires libperl.so.5.34()(64bit), but none of the providers can be installed - conflicting requests - package perl-libs-4:5.34.1-486.module_f37+14419+7d39a4ba.x86_64 is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages) ``` Version-Release number of selected component (if applicable): Fedora Rawhide on 20220614 How reproducible: - Always Steps to Reproduce: - See description. Actual results: - Failure Expected results: - Success Additional info:
I notice recent commits from Felix Kaechele so let's try to needinfo them. https://src.fedoraproject.org/modules/nginx/commits/mainline
corresponding Fedora CoreOS tracking issue: https://github.com/coreos/fedora-coreos-tracker/issues/1229
Thanks for reporting this. This may be fallout from my recent migration to the new modulemd-packager format. I will look into this today.
Looks like this somehow was built against perl 5.34 and not 5.36 (which is currently in rawhide) even though this was built a few days after 5.36 landing in rawhide. Thus the package tries to install perl 5.34 which is available as a module but since nginx:mainline doesn't have a module dependency on perl:5.34 it's throwing that error message that the perl 5.34 package is being filtered. I have triggered a rebuild but it seems that the modular build service has been stuck again since yesterday: https://release-engineering.github.io/mbs-ui/modules
Any updates here? Did the build ever make it through?
Unfortunately no. It seems to be stuck right before the nginx build. The Module Build Service tends to be rather temperamental. There is a ticket open with releng regarding this issue: https://pagure.io/releng/issue/10850 I have also pushed nginx 1.23.0 to the mainline branch yesterday but have so far refrained from triggering a module build due to the ongoing issues.
nginx-1.21.6-2.module_f37+14558+cc7c60ae was built against Perl 5.34 on 2022-06-03. perl-5.36.0 was built on 2022-05-30 into a side tag. Then the side tag was merged into rawhide on 2022-06-06 (koji list-history --build perl-5.36.0-488.fc37). That explains why nginx was built against Perl 5.34. Unfortunately Koji and MBS do not support building modules into a side tag. Hence affected modules needs to be rebuild separately after merging Perl into rawhide. I will suggest to Perl maintainers not to forget to rebuild affected modules after upgrading Perl.
There seem to be 7 streams in need of a rebuild <https://fedoraproject.org/wiki/Changes/perl5.36#Items_in_Progress>.