Bug 20944

Summary:	docker-compose has conflicting packages in its requirements
Product:	Mageia	Reporter:	Levi Ramsey <leviable>
Component:	RPM Packages	Assignee:	Bruno Cornec <bruno>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Levi Ramsey 2017-05-26 15:55:27 CEST

Description of problem:

urpmi docker-compose pulls in both python-docker and python-docker-py as dependencies and these two dependencies have many file conflicts, which prevents an installation of docker-compose via urpmi.  

Packages and versions pulled in by urpmi docker-compose:
  docker                         17.03.1      2.mga6        x86_64  
  docker-compose                 1.13.0       1.mga6        noarch  
  docker-containerd              0.2.8        1.mga6        x86_64  
  python-docker                  2.2.1        2.mga6        noarch  
  python-docker-py               1.10.6       1.mga6        noarch  
  python-docker-pycreds          0.2.1        1.mga6        noarch  
  python-dockerpty               0.4.1        1.mga6        noarch  

How reproducible:

Every run of urpmi docker-compose

To reproduce:
1.  urpme python-docker-py python-docker docker-compose # to ensure a clean slate
2.  urpmi docker-compose
3.  see the failure:
Installation failed:	file /usr/lib/python2.7/site-packages/docker/__init__.py conflicts between attempted installs of python-docker-py-1.10.6-1.mga6.noarch and python-docker-2.2.1-2.mga6.noarch
	file /usr/lib/python2.7/site-packages/docker/__init__.pyc conflicts between attempted installs of python-docker-py-1.10.6-1.mga6.noarch and python-docker-2.2.1-2.mga6.noarch
	file /usr/lib/python2.7/site-packages/docker/__init__.pyo conflicts between attempted installs of python-docker-py-1.10.6-1.mga6.noarch and python-docker-2.2.1-2.mga6.noarch
	file /usr/lib/python2.7/site-packages/docker/api/__init__.py conflicts between attempted installs of python-docker-py-1.10.6-1.mga6.noarch and python-docker-2.2.1-2.mga6.noarch
	file /usr/lib/python2.7/site-packages/docker/api/__init__.pyc conflicts between attempted installs of python-docker-py-1.10.6-1.mga6.noarch and python-docker-2.2.1-2.mga6.noarch
	file /usr/lib/python2.7/site-packages/docker/api/__init__.pyo conflicts between attempted installs of python-docker-py-1.10.6-1.mga6.noarch and python-docker-2.2.1-2.mga6.noarch
	file /usr/lib/python2.7/site-packages/docker/api/build.py conflicts between attempted installs of python-docker-py-1.10.6-1.mga6.noarch and python-docker-2.2.1-2.mga6.noarch
	file /usr/lib/python2.7/site-packages/docker/api/build.pyc conflicts between attempted installs of python-docker-py-1.10.6-1.mga6.noarch and python-docker-2.2.1-2.mga6.noarch

(etc.)

Rémi Verschelde 2017-05-26 16:02:43 CEST

Assignee: bugsquad => bruno

Comment 1 Bruno Cornec 2017-05-29 00:50:21 CEST

I'm a bit puzzled by this as I'm not finding this dependency requirements in the spec files of the packages mentioned. I think that the python-docker package is useless, and will ask for removal.

Status: NEW => ASSIGNED

Comment 2 Bruno Cornec 2017-05-30 01:18:44 CEST

After talking to some colleagues, it seems that python-docker is the new version of python-docker-py. So I think we should remove that last one from the repos and update deps to point to the new one. Will look on the dev ML for recommendations.

Comment 3 Bruno Cornec 2017-06-02 02:45:42 CEST

Now fixed with docker-compose-1.13.0-2

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED