Bug 1038102
| Summary: | Colision with docker-io | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pavel Mlčoch <pavkamlc> |
| Component: | docker | Assignee: | Andreas Bierfert <andreas.bierfert> |
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | andreas.bierfert, cfergeau, dmcf, dwalsh, mattdm |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-23 12:43:36 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1043676, 1051643 | ||
|
Description
Pavel Mlčoch
2013-12-04 12:31:49 UTC
*** Bug 1101123 has been marked as a duplicate of this bug. *** copied from dupe bug report: #1101123 dcorking 2014-05-26 04:10:13 EDT Description of problem: There is a file name conflict for /usr/bin/docker between 2 Fedora 20 packages. Version-Release number of selected component (if applicable): docker-1.5-10.fc20.x86_64 (f20 updates, a dockapp that provides a system tray for WindowMaker, XFCE etc.) docker-io-0.11.1-1.fc20.x86_64.rpm (f20 updates, a new Linux containerization app that has proven very popular) How reproducible: Consistent. Steps to Reproduce: 1. sudo yum install docker 2. sudo yum install docker-io Actual results: Transaction check error: file /usr/bin/docker from install of docker-io-0.11.1-1.fc20.x86_64 conflicts with file from package docker-1.5-10.fc20.x86_64 Expected results: All packages in F20 should be able to co-exist unless a conflict is documented in the RPM file. Since the conflict is only file naming, one of these packages could be patched to allow it to co-exist with the other. Additional info: Possible workaround that keeps docker working for me follows. (It allows docker-io to install, but I am not sure if docker-io is fully functioning.) #!/bin/bash sudo mv /usr/bin/docker /usr/bin/wmdocker # user must change dock icons that link to docker to point to wmdocker sudo yum install docker-io --downloadonly cd /var/cache/yum/x86_64/20/updates/packages/ sudo rpm -Uvf --force docker-io-0.11.1-1.fc20.x86_64.rpm The conflict probably also exists in rawhide. (unverified) The upstream binary in both packages is 'docker'. Debian/Ubuntu rename their binary to 'docker-io' to deal with the conflict. There is a plan to replace the 'docker' package with a renamed 'wmdocker' package in F21. (Bug # 1043676). However, that will take until F23 release to complete the Obsoletes/Expires process. In the meantime, any user with docker from F20 or rawhide will be unable to install docker-io, unless they use the workaround. Related issues: * https://fedorahosted.org/fpc/ticket/341 "How to replace "docker" package with an entirely different package of the same name?" * https://bugzilla.redhat.com/show_bug.cgi?id=1043676 "drop docker from rawhide (or redirect to wmdocker)" [reply] [−] Comment 1 Lokesh Mandvekar 2014-05-26 05:57:48 EDT I have no idea why the f20 build for wmdocker got deleted (or who did it for that matter). http://koji.fedoraproject.org/koji/packageinfo?packageID=17341 The install docs for fedora on docker.io do mention installing wmdocker to get around this problem: http://docs.docker.io/installation/fedora/ The best solution would be to rebuild and update wmdocker for f20 (since it already existed). Come f22, the current docker-io would go in as 'docker', while the current 'docker' would only exist as wmdocker. Andreas: any idea why the f20 wmdocker build got deleted? See also: https://bugzilla.redhat.com/show_bug.cgi?id=1005459 'Rename Review: wmdocker - KDE and GNOME2 system tray replacement docking application' I think this might have happened because of the attempted retiring of the package in rawhide? |