http://bugzilla.opensuse.org/show_bug.cgi?id=1092148 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tchvatal@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1092148 http://bugzilla.opensuse.org/show_bug.cgi?id=1092148#c1 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Blocker|--- |Yes --- Comment #1 from Dominique Leuenberger --- This issue is what currently blocks TW snapshots from being released Reverting the source of python-docker to the previous ones is not a viable solution, as the previous sources actually failed to build already for a while. So just putting them back in place won't give us old binaries back. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1092148 http://bugzilla.opensuse.org/show_bug.cgi?id=1092148#c2 --- Comment #2 from Tomáš Chvátal --- I copied the docker-compose to devel:languages:python to update it. Things to do (tomorrow or thursday): 1) rename to python-docker-compose 2) add all missing test dependencies and properly state Requires 3) Make sure it works with current docker we ship (as some of the packages that this pulls in actually do not work with current docker). (all WIP packages are submitted to devel:languages:python (if building to Tumbleweed, otherwise pending fixes [see testsuite failures/missing packages]). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1092148 http://bugzilla.opensuse.org/show_bug.cgi?id=1092148#c3 --- Comment #3 from Tomáš Chvátal --- I've made the deps building and passing the integration tests. Also I have filled changedevel request to move it to devel:languages:python, this way we can reduce the errors like this in the future. Afterwards we can just sr to tumbleweed and everything should work again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1092148 http://bugzilla.opensuse.org/show_bug.cgi?id=1092148#c6 --- Comment #6 from Tomáš Chvátal --- scarabeus@bugaboo: ~ $ LC_ALL=C zypper in docker-compose Loading repository data... Reading installed packages... 'docker-compose' not found in package names. Trying capabilities. Resolving package dependencies... The following 19 NEW packages are going to be installed: catatonit containerd criu docker docker-bash-completion docker-libnetwork docker-runc docker-zsh-completion libnet9 python2-protobuf python3-cached-property python3-docker python3-docker-compose python3-docker-pycreds python3-dockerpty python3-docopt python3-jsonschema python3-texttable python3-websocket-client The following recommended package was automatically selected: criu 19 new packages to install. Overall download size: 19.9 MiB. Already cached: 0 B. After the operation, additional 96.0 MiB will be used. Continue? [y/n/...? shows all options] (y): Works here. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1092148 http://bugzilla.opensuse.org/show_bug.cgi?id=1092148#c8 --- Comment #8 from Mateusz Mikuła --- (In reply to Dominique Leuenberger from comment #7)

(In reply to Mateusz Mikuła from comment #5)

...

Problem: docker-compose-1.17.0-46.4.noarch requires python-docker >= 2.5.1, but this requirement cannot be provided not installable providers: python2-docker-3.3.0-2.1.noarch[http-download.opensuse.org-983229c6] python2-docker-3.3.0-2.1.noarch[repo-oss] Solution 1: do not install docker-compose-1.17.0-46.4.noarch Solution 2: break docker-compose-1.17.0-46.4.noarch by ignoring some of its dependencies

Check your repositories please. docker-compose is at version 1.21.2-2.1 in tumbleweed.

Sorry, you are right. I had repository Virtualization:containers enabled to install minikube. -- You are receiving this mail because: You are on the CC list for the bug.