Bug 1033934

Summary:	duplicate directory between ruby-libs and rubygems
Product:	[Fedora] Fedora	Reporter:	Michael S. <misc>
Component:	ruby	Assignee:	Jeroen van Meeuwen <vanmeeuwen+fedora>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	bkabrda, mastahnke, mmorsi, mtasaka, ohadlevy, tagoh, vanmeeuwen+fedora, vondruch
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-01 16:44:33 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:

Description Michael S. 2013-11-24 13:46:10 UTC

Description of problem:

$ rpm -qf /usr/share/gems                                
ruby-libs-2.0.0.247-15.fc20.x86_64
rubygems-2.1.11-113.fc20.noarch

the directory should be in one of the rpm, if possible, but not both.
As rubygems requires ruby, who requires ruby-libs, I guess the ownership could/should be removed from this package.

Comment 1 Vít Ondruch 2014-01-06 12:24:03 UTC

Thank you for your report.

This is know issue. This was introduced intentionally in 405ae9bea21fa833. The directory should be owned by rubygems package, but we have to yet to figure out how to fix it ...

Comment 2 Fedora End Of Life 2015-05-29 09:50:23 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Michael S. 2015-06-01 16:44:33 UTC

Seems to have been fix, not sure when