Bug 1067588 - Cannot install docker-compose package.
Summary: Cannot install docker-compose package.
Status: RESOLVED DUPLICATE of bug 1062084
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Virtualization:Tools (show other bugs)
Version: Current
Hardware: 64bit Other
: P3 - Medium : Normal (vote)
Target Milestone: Current
Assignee: virt-bugs list
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-10 09:00 UTC by Athanasios Zorbas
Modified: 2017-11-10 12:10 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Athanasios Zorbas 2017-11-10 09:00:03 UTC
when installing docker-compose using zypper or yast it complains about
unmet requirement  python-docker >= 1.10.3 


# cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20171108"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="20171108"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20171108"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"



Reproducible: Always

Steps to Reproduce:
1.sudo zypper install docker-compose
2.
3.

Actual Results:

zypper in docker-compose
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: docker-compose-1.8.1-2.1.noarch requires python-docker >= 1.10.3, but this requirement cannot be provided
  uninstallable providers: python2-docker-2.5.1-1.1.noarch[repo-oss]
 Solution 1: do not install docker-compose-1.8.1-2.1.noarch
 Solution 2: break docker-compose-1.8.1-2.1.noarch by ignoring some of its dependencies
Comment 1 Dominique Leuenberger 2017-11-10 12:10:29 UTC
Dear Reporter,

Thank you for taking the time to report this bug and helping to make openSUSE
better.

This specific bug had already been reported and is being worked on.

*** This bug has been marked as a duplicate of bug 1062084 ***