Bug 1606827
| Summary: | m2crypto: FTBFS in Fedora rawhide | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mohan Boddu <mboddu> | ||||||||
| Component: | m2crypto | Assignee: | Neal Gompa <ngompa13> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 29 | CC: | fweimer, gholms, mhroncok, mitr, ngompa13, pviktori | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | m2crypto-0.35.2-1.fc30 m2crypto-0.35.2-1.fc29 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-06-26 04:07:02 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: | 1700317, 1602938, 1674516, 1686977, 1732841 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Mohan Boddu
2018-07-20 21:49:34 UTC
Created attachment 1469358 [details]
build.log
file build.log too big, will only attach last 32768 bytes
Created attachment 1469359 [details]
root.log
file root.log too big, will only attach last 32768 bytes
Created attachment 1469360 [details]
state.log
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. There's a PR to address this: https://src.fedoraproject.org/rpms/m2crypto/pull-request/2 m2crypto doesn't build with Python 3.8. Please merge that PR. Dear Maintainer, your package has not been built successfully in f30. 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 can be orphaned if this bug remains in NEW state more than 8 weeks. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ Please respond. asking again for a response Asking again for a response. Sorry about the late response; I only have very marginal time left for Fedora. I will be giving up the m2crypto package; Neil Gompa has offered to co-maintain it in https://src.fedoraproject.org/rpms/m2crypto/pull-request/2, so maybe he would be willing to own it. Unfortunately, there is another failure with Python 3.8: bz1715243 Dear Maintainer, your package has not been built successfully in f30. 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 can be orphaned if this bug remains in NEW state more than 8 weeks. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ It's being worked on... FEDORA-2019-79f7935107 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-79f7935107 m2crypto-0.35.2-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. m2crypto-0.35.2-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. |