Bug 24652 - Cannot install docker-compose
Summary: Cannot install docker-compose
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA6-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2019-04-11 20:00 CEST by Ian McDougall
Modified: 2019-09-06 23:10 CEST (History)
5 users (show)

See Also:
Source RPM: docker-compose-1.13.0-2.mga6.noarch
CVE:
Status comment:


Attachments

Description Ian McDougall 2019-04-11 20:00:44 CEST
Description of problem:
I cannot select docker-compose in the package manager (GUI). The error is

Sorry, the following package cannot be selected:
- docker-compose-1.13.0-2.mga6.noarch (due to unsatisfied pythongegg(2)(pyyaml)[< 4]

The problem occurs with or without python-yaml installed, but with it installed the error message omits the cause of the problem.

How reproducible:
100%

Steps to Reproduce:
1. Open GUI package manager
2. Attempt to check the box next to docker-compose
Comment 1 Lewis Smith 2019-04-11 21:30:04 CEST
I confirm this dependency problem:
 # urpmi docker-compose
 Nid oes modd gosod pecyn gofynnwyd amdani:
docker-compose-1.13.0-2.mga6.noarch (pythonegg(2)(pyyaml)[< 4] heb ei foddloni)
which is (believe me) what Ian reported.

I am baffled by the 'docker-compose' requires, which include:
 PyYAML
 pythonegg(2)(pyyaml)[>= 3.10]
 pythonegg(2)(pyyaml)[< 4]

'PyYAML' says there is no such package;
'python-yaml' is not mentioned; BUT 
 $ urpmq --whatrequires python-yaml
*does* include 'docker-compose'.
I get nowhere searching 'pythonegg', 'pythonegg(2)', 'pythonegg(2(pyyaml)';
nor 'pyyaml' 'pyYAML' (which I made up to try).

CC: (none) => lewyssmith
Assignee: bugsquad => bruno.cornec

Comment 2 Bruno Cornec 2019-09-04 11:52:23 CEST
I can confirm what I get on my Mageia 6 version:

$ LANG=C sudo urpmi docker-compose
The following package cannot be installed because it depends on packages
that are older than the installed ones:
docker-compose-1.13.0-2.mga6
Continue installation anyway? (Y/n) 
While some packages may have been installed, there were failures.
The following package cannot be installed because it depends on packages
that are older than the installed ones:
docker-compose-1.13.0-2.mga6
Continue installation anyway?

$ rpm -q python-yaml
python-yaml-5.1-1.1.mga6


What is also strange is that there is no version requirements around PyYAML in the spec file.

I'm pushing a rebuild to updates_testing as tag -3 to see whether just that helps.

CC: (none) => bruno
Status: NEW => ASSIGNED

Comment 3 Bruno Cornec 2019-09-04 16:26:38 CEST
Doesn't help. It seems there is a python module in the stack somewhere that requires python-yaml < 4, but I don't know which :-(

Will rebuild the latest mga7 docker-compose version to see if that works in my env, then if yes will upload it so you can test as well.
Comment 4 Thomas Backlund 2019-09-04 16:29:57 CEST
urpmi will help you with debug...

Try urpmi --debug docker-compose

And you will find info about what fails

CC: (none) => tmb

Comment 5 Bruno Cornec 2019-09-04 17:43:17 CEST
I uploaded docker-compose 1.14.0 instead which also require an update of python-docker to 2.3.0, both of them being in updates_testing. Works here for the install.
Comment 6 David Walser 2019-09-04 20:15:34 CEST
Make sure you provide an advisory and assign this to QA.
Comment 7 Bruno Cornec 2019-09-05 01:37:37 CEST
Uploaded for Mageia 6:
docker-compose-1.14.0-1.mga6
python-docker-2.3.0-1.mga6

This is fixing an installation issue with the python stack dependencies (python-yaml updated to 5.1)

Assignee: bruno.cornec => qa-bugs

Comment 8 Len Lawrence 2019-09-06 20:30:44 CEST
mga6, x86-64

Yes, installation failed before the update but worked fine after it.

CC: (none) => tarazed25
Whiteboard: (none) => MGA6-64-OK

Thomas Backlund 2019-09-06 20:42:02 CEST

Keywords: (none) => advisory, validated_update
CC: (none) => sysadmin-bugs

Comment 9 Mageia Robot 2019-09-06 23:10:40 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2019-0111.html

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


Note You need to log in before you can comment on or make changes to this bug.