Bug 1075779 - file conflict with rubygem-openshift-origin-common
Summary: file conflict with rubygem-openshift-origin-common
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openshift-origin-broker
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Troy Dawson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-12 19:28 UTC by Michael Haller
Modified: 2014-03-15 15:09 UTC (History)
5 users (show)

Fixed In Version: rubygem-openshift-origin-common-1.18.0.2-2.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of: 1033928
Environment:
Last Closed: 2014-03-15 15:09:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michael Haller 2014-03-12 19:28:15 UTC
+++ This bug was initially created as a clone of Bug #1033928 +++

Description of problem:
on Fedora 20, trying to install openshift-origin-broker result in :

Transaction check error:
  file /etc/openshift/plugins.d conflicts between attempted installs of openshift-origin-broker-1.10.2.1-1.fc20.noarch and rubygem-openshift-origin-common-1.13.0.1-1.fc20.noarch

--- Additional comment from Troy Dawson on 2013-11-25 10:36:48 EST ---

I have fixed rubygem-openshift-origin-common, because that is where this was fixed upstream.

Although I am fixing this, I am a little confused.  In both packages, /etc/openshift/plugins.d is marked as a directory.  You can (or could) have multiple packages owning the same directory.

Is this conflict a "feature" that is coming in F20?  Or is this a bug in rpm?

If this is a new "feature", I would like to see the argument for it.  I currently don't agree with it.

--- Additional comment from Fedora Update System on 2013-11-25 11:18:20 EST ---

rubygem-openshift-origin-common-1.13.0.1-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/rubygem-openshift-origin-common-1.13.0.1-2.fc20

--- Additional comment from Michael Scherer on 2013-11-25 11:28:56 EST ---

It could just be that the files are not identical in both rpm, because that's the main problem when you do that. IE, any file owner, group or permission change must be coordinated between the rpm, and this is not really sustainable. 

SO I would still recommend to avoid double ownership if it can be avoided.

--- Additional comment from Troy Dawson on 2013-11-25 12:28:47 EST ---

Aha, you are correct.  One has the directory owned by root, and one has it owned by apache.
I do agree with you that is possible, that directory ownership should be consolidated, which openshift upstream as been trying to do.  I was just concerned that there was a change in F20 rpm I wasn't aware of.
There have been so many other changes recently that I guess I'm a little gunshy.

--- Additional comment from Fedora Update System on 2013-11-25 23:03:44 EST ---

Package rubygem-openshift-origin-common-1.13.0.1-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rubygem-openshift-origin-common-1.13.0.1-2.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-22101/rubygem-openshift-origin-common-1.13.0.1-2.fc20
then log in and leave karma (feedback).

--- Additional comment from Fedora Update System on 2013-12-13 21:43:48 EST ---

rubygem-openshift-origin-common-1.13.0.1-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

--- Additional comment from Michael Haller on 2014-03-12 15:17:57 EDT ---

The issue seems to be occurring again with bumped versions of both packages:

Transaction check error:
  file /etc/openshift/plugins.d from install of openshift-origin-broker-1.15.1.2-1.fc20.noarch conflicts with file from package rubygem-openshift-origin-common-1.18.0.2-1.fc20.noarch

Comment 1 Troy Dawson 2014-03-13 14:32:17 UTC
This has been fixed upstream already.
The problem came about because they fixed it opposite of how I fixed it, and I had forgotten about the bug and my solution.  So I pulled in their solution (have broker own the directory because only broker uses it) but forgot to remove my solution (have common own the directory because I thought both broker and node used it)

An updated rubygem-openshift-origin-common is on it's way.

Comment 2 Fedora Update System 2014-03-13 14:45:46 UTC
rubygem-openshift-origin-common-1.18.0.2-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/rubygem-openshift-origin-common-1.18.0.2-2.fc20

Comment 3 Fedora Update System 2014-03-15 15:09:44 UTC
rubygem-openshift-origin-common-1.18.0.2-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


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