Fedora Account System
Red Hat Associate
Red Hat Customer
As of git-2.51.0-1.fc44 and git-2.51.0-1.fc43 the git-core subpackage now depends on perl. I believe this was a mistake. CoreOS builds are failing with: ``` 06:01:37 Resolving dependencies...done 06:01:37 error: Installing packages: Could not depsolve transaction; 1 problem detected: 06:01:37 Problem: package git-core-2.51.0-1.fc44.x86_64 from fedora-rawhide requires /usr/bin/perl, but none of the providers can be installed 06:01:37 - conflicting requests 06:01:37 - package perl-interpreter-4:5.42.0-520.fc43.x86_64 from fedora-rawhide is filtered out by exclude filtering 06:01:37 failed to execute cmd-fetch: exit status 1 ``` Reproducible: Always
find templates -type f -name "*sample" | xargs chmod -x is enough to strip the perl dep. Personally I would have anything *.sample in docs and not the core package
Hah, hi Dusty, you win this round. :P openQA actually caught this, but I couldn't figure out what was going on and decided it was a blip - all I knew is that it pulled in the older git from the rawhide repo instead of the newer one from the advisory repo, it doesn't tell you *why* it does that and I couldn't work it out yesterday. Now we know! Indeed, all openQA Silverblue ostree build tests now fail on this, and all Atomic desktop builds in today's compose failed too - https://pagure.io/releng/failed-composes/issue/8538 .
Adding this to the spec fixes it: # Don't generate deps from the sample hooks (to avoid perl deps in core) %global __requires_exclude_from ^%{_datadir}/git-core/templates/hooks/.*sample$ that tells RPM to skip any files matching that regex when auto-generating requirements. See https://docs.fedoraproject.org/en-US/packaging-guidelines/AutoProvidesAndRequiresFiltering/ . Even if we do decide to move all the sample hooks to another package, I think it's a good idea to *also* add that line, as it doesn't seem right for *whichever* package they wind up in to have any deps which are *only* required to run sample hooks.
Fixed now, F43 and F44 updates are both stable. The bug never made it to F41 or F42.