Bug 2208360

Summary: /usr/lib/debug/usr/lib64/bfd-plugins/libdep.so-2.40-7.fc39.x86_64.debug incorrectly included in non-debuginfo package
Product: [Fedora] Fedora Reporter: Gursewak Singh <gurssing>
Component: binutilsAssignee: Nick Clifton <nickc>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: awilliam, bhe, dustymabe, dvlasenk, fweimer, jakub, mjw, nickc, ruyang, ryncsn, sipoyare, travier, yahmad
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-04 13:05:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gursewak Singh 2023-05-18 17:16:30 UTC
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

Comment 1 Timothée Ravier 2023-05-30 16:36:26 UTC
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

Comment 2 Nick Clifton 2023-05-31 15:50:26 UTC
Should be fixed in binutils-2.40-9.fc39

Comment 3 Dusty Mabe 2023-06-05 01:35:42 UTC
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

Comment 4 Nick Clifton 2023-06-05 10:25:00 UTC
(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 ...

Comment 5 Dusty Mabe 2023-06-06 13:48:48 UTC
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

Comment 6 Adam Williamson 2023-06-07 06:56:22 UTC
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).

Comment 7 Adam Williamson 2023-06-07 06:58:50 UTC
well, hmm, not actually sure exactly what happened now I look at it closer, but in any case, it's gone stable now...

Comment 8 Timothée Ravier 2023-07-04 13:05:00 UTC
Should be fixed now.