Bug 1705955
| Summary: | docker-compose FTBFS with pytest 4 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> | ||||||
| Component: | docker-compose | Assignee: | Michael Hampton <error> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 31 | CC: | carl, error, lbalhar, releng, roman, ttomecek | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | docker-compose-1.24.1-3.fc31 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2019-10-26 17:23:15 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, 1671167, 1686977, 1732841 | ||||||||
| Attachments: |
|
||||||||
|
Description
Miro Hrončok
2019-05-03 09:46:14 UTC
Created attachment 1562281 [details]
root.log from Koji
Please respond. This issue has now been reported upstream. https://github.com/docker/compose/issues/6796 *** Bug 1735097 has been marked as a duplicate of this bug. *** This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'. This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31. The coordinated rebuild of Python 3.8 has started in the `f32-python` side tag.
If you figure out how to rebuild this package, please don't rebuild it in regular rawhide, but use the side tag instead:
on branch master:
$ fedpkg build --target=f32-python
To wait for a build to show up in the side tag, do:
$ koji wait-repo f32-python --build=<nvr>
Where <nvr> is name-version-release of the source package, e.g. python-foo-1.1-2.fc32.
An updated mock config is posted at:
http://copr.fedorainfracloud.org/coprs/g/python/python3.8/
Note that it will take a while before the essential packages are rebuilt, so don't expect all your dependencies to be available right away.
Thanks. Let us know if you need up to date info, or if you have any questions.
PS this message is mass posted to all the bugs that block the PYTHON38 bug. If this is also a Fedora 31 FTBFS bug and you manage to fix it, you can do a f31 build as usual:
on branch f31:
$ fedpkg build
I've proposed a solution in the upstream issue. If there is no response from an upstream maintainer and this will block us, I can prepare a downstream patch. The f32-python side tag has been merged. In order to rebuild the package, do it in regular rawhide, but please wait until python3-3.8 is tagged: $ koji wait-repo f32-build --build python3-3.8.0~b3-3.fc32 If your built already started in f32-python, after it is finished, please tag it to rawhide with: $ koji tag-build f32-pending <nvr> For example: $ koji tag-build f32-pending libreoffice-6.3.0.4-3.fc32 Thanks! (This comment is mass posted to all bugzillas blocking the PYTHON38 tracking bug.) (Python 3.8 has landed in the rawhide buildroot.) (In reply to Lumír Balhar from comment #8) > I've proposed a solution in the upstream issue. If there is no response from > an upstream maintainer and this will block us, I can prepare a downstream > patch. I would be most happy to receive a patch. I tried to hack this myself but could not quite figure it out. This is already blocked in f31 and in danger of being orphaned so not waiting for upstream is definitely better. (In reply to Michael Hampton from comment #11) > (In reply to Lumír Balhar from comment #8) > > I've proposed a solution in the upstream issue. If there is no response from > > an upstream maintainer and this will block us, I can prepare a downstream > > patch. > > I would be most happy to receive a patch. I tried to hack this myself but > could not quite figure it out. This is already blocked in f31 and in danger > of being orphaned so not waiting for upstream is definitely better. I can prepare a patch and put it into the package and also create a PR upstream but the risk here is that they'll prefer a different approach than me when they get to fix this issue in a future release. Do you think that it's worth to prepare a patch instead of skipping those ~11 tests and waiting for upstream? (In reply to Lumír Balhar from comment #12) > I can prepare a patch and put it into the package and also create a PR > upstream but the risk here is that they'll prefer a different approach than > me when they get to fix this issue in a future release. > > Do you think that it's worth to prepare a patch instead of skipping those > ~11 tests and waiting for upstream? How much work is it? If upstream rejects a PR and does something else, then we can just drop the patch. But disabling 11 or 12 tests makes me nervous as we wouldn't be able to say for sure that those tests would pass otherwise. I've created an upstream PR to fix pytest compatibility: https://github.com/docker/compose/pull/6873 You can use the patch in RPM to solve this bug. FEDORA-2019-de4581d1b3 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-de4581d1b3 docker-compose-1.24.1-1.fc31 has been pushed to the Fedora 31 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-de4581d1b3 FEDORA-2019-75607f2722 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-75607f2722 docker-compose-1.24.1-3.fc31 has been pushed to the Fedora 31 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-75607f2722 docker-compose-1.24.1-3.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. |