Bug 1166497

Summary: docker-compose uninstallable on Leap 15.2
Product: [openSUSE] openSUSE Distribution Reporter: Guillaume GARDET <guillaume.gardet>
Component: ContainersAssignee: Containers Team <containers-bugowner>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P2 - High CC: dheidler, guillaume.gardet, lubos.kocman, mlin, tchvatal
Version: Leap 15.2   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on: 1165620, 1167529    
Bug Blocks:    

Description Guillaume GARDET 2020-03-12 13:08:10 UTC
docker-compose uninstallable on Leap 15.2 because python-PyYAML has been updated from 3.x to 5.x but docker-compose spec includes:
  Requires:       python-PyYAML           >= 3.11
  Conflicts:      python-PyYAML           >= 4

So, I guess docker-compose should be updated in Leap 15.2.
Comment 1 Max Lin 2020-03-15 01:07:20 UTC
Yes, I'm trying to get a docker-compose update from Factory(python-docker-compose, renamed) https://build.opensuse.org/project/show/openSUSE:Leap:15.2:Staging:adi:23 , we need to fix dep problem first to made it built first, I've talked to Tomas about that already.
Comment 2 Tomáš Chvátal 2020-03-24 08:28:23 UTC
The python-docker can be updated but the new version needs pytest >= 4 and that is currently being processed as an ECO.

When that is done we can proceed onwards with updating python-docker on SP2 and newer (I suppose we don't need ECO to keep just python-docker from SLE15:GA unforked).
Comment 3 Lubos Kocman 2020-04-06 09:24:55 UTC
Oky so keeping openned until we have a newer pytest. Any ETA for Leap Tomas?
I recall you've mentioned that this should be already done for TW.
Comment 4 Tomáš Chvátal 2020-04-06 09:27:24 UTC
https://smelt.suse.de/incident/14582/
Comment 9 Max Lin 2020-05-26 14:41:56 UTC
This should be fixed in Leap 15.2 already https://openqa.opensuse.org/tests/1278932#step/docker_compose/45 , we can close this bug.
Comment 10 Tomáš Chvátal 2020-05-27 07:13:22 UTC
Closing as we solved it as per previous comment.