Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ Your package (docker-compose) Fails To Install in Fedora 38: can't install docker-compose: - nothing provides python3-dockerpty >= 0.4.1 needed by docker-compose-1.29.2-7.fc38.noarch - nothing provides python3.11dist(dockerpty) >= 0.4.1 needed by docker-compose-1.29.2-7.fc38.noarch If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock: $ mock -r fedora-38-x86_64 --config-opts mirrored=False install docker-compose P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
`python3-dockerpty` is now retired and no longer available in Fedora, hence this bugzilla is anyone still using this older python implementation of docker-compose? is there a value keeping this package alive? I will either pick up dockerpty or orphan/retire docker-compose: please provide feedback in this bugzilla.
*** Bug 2000794 has been marked as a duplicate of this bug. ***
Hello , we need docker-compose https://docs.docker.com/compose/ for docker eco system , but we need update it from version 1 to 2, and packaging changed from python to go , as maintainer of moby-engine I want keep , I'm proven packager but I'd like that you add me as admin of this package thank you
Thank you Sergio for your feedback, I'll add you. I'm curious if we should do all the changes in docker-compose (switch from 1 to 2), or have both implementations available: docker-compose would be 2, and docker-compose1 would be 1.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
If, as I understand it, you're kind of asking for "me too"s about this package being valued, I personally would much rather use docker-compose (ideally a recent version, sure) from official Fedora repositories than having to add third-party repositories, which I try to avoid as they often create complications when upgrading and otherwise.
The SSSD package is being tested using an environment that is setup using docker-compose. I think it's fine for us to use either of the two versions, but we'd at least need one of them. Taking into account that Fedora 38 is released tomorrow, do you have any plan to work on the fix?
This fell of my radar. I just requested unretiring dockerpty: https://pagure.io/releng/issue/11391 If you depend on this software, I welcome you as comaintainers. Both packages are no longer maintained upstream so this is about keeping them alive.
Which are the two packages that aren't maintained upstream? I'm don't have a great knowledge of docker-compose so I'm asking another question. Why is upstream releasing v2, and Fedora still keeps v1? Is there any problem with licenses? Or is it manpower shortage?
docker-compose was rewritten from Python to golang, see discussion above; packaging v2 is a colossal effort therefore docker-compose python v1 version is no longer maintained upstream the same for dockerpty (the low level lib that makes `exec` work), no commit in 5+ years
I see this isn't a small effort task and it will take a long time. Out of curiosity, do you know how difficult would it be to move away from docker-compose to podman-compose? I guess they follow a similar file structure and things should be quite straightforward.
please try run : go2rpm https://github.com/docker/compose spectool -g golang-github-docker-compose.spec fedpkg mockbuild you will see : No matching package to install: 'golang(github.com/compose-spec/compose-go/cli)' No matching package to install: 'golang(github.com/compose-spec/compose-go/errdefs)' No matching package to install: 'golang(github.com/compose-spec/compose-go/loader)' No matching package to install: 'golang(github.com/compose-spec/compose-go/types)' No matching package to install: 'golang(github.com/compose-spec/compose-go/utils)' No matching package to install: 'golang(github.com/docker/buildx/build)' No matching package to install: 'golang(github.com/docker/buildx/builder)' No matching package to install: 'golang(github.com/docker/buildx/driver)' No matching package to install: 'golang(github.com/docker/buildx/driver/docker)' No matching package to install: 'golang(github.com/docker/buildx/driver/docker-container)' No matching package to install: 'golang(github.com/docker/buildx/driver/kubernetes)' No matching package to install: 'golang(github.com/docker/buildx/driver/remote)' No matching package to install: 'golang(github.com/docker/buildx/store/storeutil)' No matching package to install: 'golang(github.com/docker/buildx/util/buildflags)' No matching package to install: 'golang(github.com/docker/buildx/util/dockerutil)' No matching package to install: 'golang(github.com/docker/buildx/util/imagetools)' No matching package to install: 'golang(github.com/docker/buildx/util/logutil)' No matching package to install: 'golang(github.com/docker/buildx/util/progress)' No matching package to install: 'golang(github.com/docker/cli-docs-tool)' No matching package to install: 'golang(github.com/tilt-dev/fsnotify)' we will need pack these packages compose-spec/compose-go , docker/buildx , docker/cli-docs-tool and tilt-dev/fsnotify
for docker-compose-2.17.2
I need docker-compose for my work. Is there a work-around till this package gets fixed?
I found a work-around to install the compose plugin manually: https://docs.docker.com/compose/install/linux/#install-the-plugin-manually
FEDORA-2023-dcf5ef9eda has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-dcf5ef9eda
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ All subpackages of a package against which this bug was filled are now installable or removed from Fedora 39. Thanks for taking care of it!
It's a bit late, but just for the record I need the docker-compose package in F38 for upstream podman CI testing.
FEDORA-2023-dcf5ef9eda has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-dcf5ef9eda` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-dcf5ef9eda See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-dcf5ef9eda has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.