Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1799202
Summary: | bwa: FTBFS in Fedora rawhide/f32 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
Component: | bwa | Assignee: | Jun Aruga <jaruga> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 32 | CC: | bloch, jaruga | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | bwa-0.7.17-1.fc33.src.rpm bwa-0.7.17-1.fc32 | Doc Type: | If docs needed, set a value | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2020-04-25 02:24:53 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: | 1750908 | ||||||||||
Attachments: |
|
Description
Fedora Release Engineering
2020-02-06 16:10:40 UTC
Created attachment 1658541 [details]
build.log
Created attachment 1658542 [details]
root.log
file root.log too big, will only attach last 32768 bytes
Created attachment 1658543 [details]
state.log
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32. Dear Maintainer, your package has not been built successfully in 32. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 33 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 31 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/33/Schedule Dear Maintainer, your package has not been built successfully in 32. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 33 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 31 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/33/Schedule Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 32. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (that's on 2020-04-02). A week before the mass branching of Fedora 33 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 31 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html Seeing the bwa Koschei log. https://koschei.fedoraproject.org/package/bwa The build failure started after gcc version was upgraded from 9 to 10. I reported the issue to the upstream here. https://github.com/lh3/bwa/issues/275 I sent PR to Fedora bwa repository here. https://src.fedoraproject.org/rpms/bwa/pull-request/1 Note 1: I assigned myself, because of following context. But feel free to take it to assign yourself when you work for this issue. > Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (that's on 2020-04-02). You need to build bwa to f32 too, as the build is failed too. https://koji.fedoraproject.org/koji/packageinfo?packageID=10451 Note 2: I created "biology" group in Koschei to manage biology, bioinformatics packages. bwa is included in the list. https://koschei.fedoraproject.org/groups/biology It is linked from following Fedora Medical SIG page. https://fedoraproject.org/wiki/SIGs/Medical > I sent PR to Fedora bwa repository here.
> https://src.fedoraproject.org/rpms/bwa/pull-request/1
As I am not sure that my pull-request will be merged, or I can have a permission for that, I will remove my assignment changing the status to NEW again. Maybe it's better.
As I got the permission for the repository, I assign myself again to prevent bwa to be orphaned. Thanks, Adam! FEDORA-2020-ee194c5ad2 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ee194c5ad2 FEDORA-2020-ee194c5ad2 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ee194c5ad2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ee194c5ad2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-ee194c5ad2 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |