Description of problem: With the upgrade of kexec-tools 2.0.26-3.fc38 -> 2.0.26-4.fc39, we are seeing that the symlink to /usr/lib/debug/usr/lib64/bfd-plugins/libdep.so-2.40-7.fc39.x86_64.debug cannot be validated. /usr/lib/debug/.build-id/36/96626d3b4b74691ca6d10f86971e546755f6ba.debug symlink to /usr/lib/debug/usr/lib64/bfd-plugins/libdep.so-2.40-7.fc39.x86_64.debug which does not exist Pinning the package to kexec-tools 2.0.26-3.fc38 in FCOS solves the issue. Version-Release number of selected component (if applicable): 2.0.26-4.fc39 How reproducible: Everytime. Actual results: The symlink to /usr/lib/debug/usr/lib64/bfd-plugins/libdep.so-2.40-7.fc39.x86_64.debug is broken Expected results: The symlink to /usr/lib/debug/usr/lib64/bfd-plugins/libdep.so-2.40-7.fc39.x86_64.debug should exist Additional info: Feel free to update this issue if this was purposefully done
binutils-2.40-7.fc39.x86_64.rpm includes the following files: https://koji.fedoraproject.org/koji/rpminfo?fileStart=50&rpmID=34277234&fileOrder=name&buildrootOrder=-id&buildrootStart=0#filelist: ``` /usr/lib/debug/.build-id/36/96626d3b4b74691ca6d10f86971e546755f6ba /usr/lib/debug/.build-id/36/96626d3b4b74691ca6d10f86971e546755f6ba.debug ``` That should instead be part of binutils-debuginfo-2.40-7.fc39.x86_64.rpm: https://koji.fedoraproject.org/koji/rpminfo?fileStart=100&rpmID=34277231&fileOrder=name&buildrootOrder=-id&buildrootStart=0#filelist See also: https://github.com/coreos/fedora-coreos-tracker/issues/1496
Should be fixed in binutils-2.40-9.fc39
Thanks for the build. Looks like it failed tests and got gated in Bodhi so it never made it into a rawhide compose. Can we unblock it somehow? https://bodhi.fedoraproject.org/updates/FEDORA-2023-2944964c27
(In reply to Dusty Mabe from comment #3) > Thanks for the build. Looks like it failed tests and got gated in Bodhi so > it never made it into a rawhide compose. Can we unblock it somehow? I have waived the gating issues, so the new build should now be in the buildroot. One of the gating problems is rather ironic - it is complaining about the presence of suspicious unicode characters in the annobin sources. The problem is that these characters are in the testsuite where it checks that annocheck can detect and report suspicious unicode characters ...
The build still didn't make it into the rawhide compose last night. The update still shows it as `testing` for F39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-2944964c27
After waiving test results you should also do a manual push to stable to get it to go immediately. It won't get automatically resubmitted immediately (it does get done after some time, as in this case).
well, hmm, not actually sure exactly what happened now I look at it closer, but in any case, it's gone stable now...
Should be fixed now.