Bug 2113439
| Summary: | hackrf: FTBFS in Fedora rawhide/f37 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
| Component: | hackrf | Assignee: | Steven A. Falco <stevenfalco> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 37 | CC: | hobbes1069, jskarvad, logans, stevenfalco | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | hackrf-2018.01.1-12.fc37 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2022-11-26 02:12:06 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 2045102, 2117176 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Fedora Release Engineering
2022-08-01 23:48:10 UTC
Created attachment 1901742 [details]
build.log
Created attachment 1901743 [details]
root.log
file root.log too big, will only attach last 32768 bytes
Created attachment 1901744 [details]
state.log
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37. I tried a scratch build of this package and it built cleanly: https://koji.fedoraproject.org/koji/taskinfo?taskID=94253032 I think a simple rebuild should be sufficient. Please let me know if I can help - I'd be willing to be a co-maintainer if the current maintainers are too busy with other things. Since it appears to just need a rebuild I'll kick one off. I had to build for Rawhide first, but to be honest, this version is from 2018 and there is a 2022 version. You should start the non-responsive maintainer process as the maintainer obviously isn't interested in maintaining the package. FEDORA-2022-179cf029d6 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-179cf029d6 Thanks, Richard. I've tried to build with the 2022 version, but I haven't gotten the documentation to build - it now uses sphinx-build. I'll start the non-responsive maintainer process and I'll keep working on the 2022 version. FYI, I did a minimal update in Rawhide for the latest version, if you haven't cloned the repo make sure you do a pull first. I didn't worry about the documentation just fixed the glob for the existing docs. Great - thanks! That builds for me, and is certainly good enough for right now. I've opened bug 2143712 and we'll see where it goes. Richard, please take a look at bug 1941132. Apparently there are some dependent packages. I don't know if that means your rawhide build of 2022.09.01 will cause problems. I'll start some builds via copr, but I'm not a proven packager, so I doubt I can rebuild the dependent packages without help. FEDORA-2022-179cf029d6 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-179cf029d6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-179cf029d6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. I've tested the hackrf-2018.01.1 package on F37 and it works fine. I've added +1 karma in bodhi. I also tested the hackrf-2022.09.1 package on rawhide, and it works fine as well. FEDORA-2022-179cf029d6 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. |