Bug 790362 - Move ruby libraries into vendor dir
Summary: Move ruby libraries into vendor dir
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: root
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mattias Ellert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-14 10:48 UTC by Vít Ondruch
Modified: 2012-02-28 10:38 UTC (History)
2 users (show)

Fixed In Version: root-5.32.00-2.fc17
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-28 10:38:27 UTC
Type: ---

Attachments (Terms of Use)
move lib into vendor dir (1.71 KB, patch)
2012-02-14 10:48 UTC, Vít Ondruch 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Vít Ondruch 2012-02-14 10:48:08 UTC 
Created attachment 561874 [details]
move lib into vendor dir

According to the new guidelines and new files layout of Ruby 1.9.3, please move the ruby libraries into the vendor dir instead of site dir. The attached patch should fix this issue. Thank you.
Comment 1 Fedora Update System 2012-02-15 04:37:23 UTC 
root-5.32.00-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/root-5.32.00-2.fc17
Comment 2 Fedora Update System 2012-02-16 01:56:21 UTC 
Package root-5.32.00-2.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing root-5.32.00-2.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1742/root-5.32.00-2.fc17
then log in and leave karma (feedback).
Comment 3 Fedora Update System 2012-02-28 10:38:27 UTC 
root-5.32.00-2.fc17 has been pushed to the Fedora 17 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.