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 1695953
Summary: | cloud-init-17.1-8.fc31 FTBFS (not only) with Python 3.8 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
Component: | cloud-init | Assignee: | Garrett Holmstrom <gholms> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | adimania, apevec, besser82, eterrell, fweimer, gholms, lars, shardy, s, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | cloud-init-17.1-10.fc31 cloud-init-17.1-9.fc30 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-04-23 19:27:52 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: | 1700317, 1675080, 1686977, 1732841 |
Description
Miro Hrončok
2019-04-03 23:35:33 UTC
CC'ing zbyszek about the %systemd_postun failure. My Copr still has systemd 241-4.gitcbf14c9.fc31, Koji has 242~rc2-1.fc31. And according to koschei, the tests are failing anyway since mid February https://apps.fedoraproject.org/koschei/package/cloud-init https://apps.fedoraproject.org/koschei/build/6037690 looks like bash update problem to me So this now has 3 levels of FTBFS: level 1) systemd macro problem with systemd 242 level 2) setup.py install platfrom.dist() problem with Python 3.8 level 3) %check failure anywhere caused by something that happened in February, maybe BASH 5 Seems like Bash 5 added EPOCHREALTIME env varibale and that's causing the tests to fail. https://lists.gnu.org/archive/html/bug-bash/2018-05/msg00068.html It's not a bug, it's a feature! $ fedpkg srpm && mock -n $(ls -t1r *.src.rpm|tail -n1) Downloading cloud-init-17.1.tar.gz ######################################################################## 100.0% error: This macro requires some arguments error: line 124: %systemd_postun As it says, this macro requires some arguments, most likely the same ones that are used for %systemd_post and %systemd_preun in the lines right above. Could you please try to fix this? Or should this be brought upstream? Please respond. Following with https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/5GEFZTPCOBKYY54KEHYSAYYMEYO7DI7Z/ https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ I'm not the maintainer of the package, but as a proven packager I have fixed the three issues mentioned in comment #2 since the maintainer was not replying. The package now builds fine on F30 and Rawhide (even with Python 3.8) again. I forgot to mention: To fix that issue with platform.dist, I needed to add (Build)Requires: python3-distro. Rawhide build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1253879 F30 build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1253877 cloud-init-17.1-9.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-67d7987a7b cloud-init-17.1-9.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-67d7987a7b cloud-init-17.1-9.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. |