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 1962465
Summary: | python-zeep: FTBFS in Fedora rawhide | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomáš Hrnčiar <thrnciar> |
Component: | python-zeep | Assignee: | Georg Sauthoff <fedora> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://koschei.fedoraproject.org/package/python-zeep | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-05-25 20:16: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: | |||
Bug Depends On: | |||
Bug Blocks: | 1890881, 1927309 |
Description
Tomáš Hrnčiar
2021-05-20 06:46:32 UTC
Hm, did a scratch build with a tiny extra bit of debugging and that succeeded in rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=68730632 A regular re-build succeeded as well: https://koji.fedoraproject.org/koji/taskinfo?taskID=68731214 Ok, so the build that failed ran on s390x, my scratch build ran on x86_64 and the other regular re-build ran on ppc64le. Thus, I submitted another scratch-build for s390x which succeeded as well: https://koji.fedoraproject.org/koji/taskinfo?taskID=68731775 So not another weird s390x issue, this time. Thus, I'm closing this issue, as it was likely caused by a dependency which was fixed since the last build failure. |