Bug 1008866 - /usr/share/gems/doc ownership
Summary: /usr/share/gems/doc ownership
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygems
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-17 08:57 UTC by Vít Ondruch
Modified: 2013-10-04 03:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-04 03:01:51 UTC
Type: Bug


Attachments (Terms of Use)

Description Vít Ondruch 2013-09-17 08:57:39 UTC
Description of problem:
rubygems has to own /usr/share/gems/doc

Version-Release number of selected component (if applicable):
$ rpm -q rubygems
rubygems-2.0.7-103.fc19.noarch


How reproducible:
Always


This regression was introduced by [1]. Originally reported at ruby-sig ML [2].


[1] http://pkgs.fedoraproject.org/cgit/rubygems.git/commit/?id=1d350ea912e72d30c7d079449db926ed4cb652a9
[2] https://lists.fedoraproject.org/pipermail/ruby-sig/2013-September/001426.html

Comment 1 Fedora Update System 2013-09-25 01:07:37 UTC
rubygems-2.0.10-106.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/rubygems-2.0.10-106.fc20

Comment 2 Fedora Update System 2013-09-25 01:07:55 UTC
rubygems-2.0.10-106.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/rubygems-2.0.10-106.fc19

Comment 3 Fedora Update System 2013-10-01 02:11:20 UTC
rubygems-2.0.10-106.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Fedora Update System 2013-10-04 02:00:57 UTC
rubygems-2.0.10-106.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Mamoru TASAKA 2013-10-04 03:01:51 UTC
Now closing.


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