Bug 927471
Summary: | %%gem_extdir_mri wrong on F-18 and below | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mamoru TASAKA <mtasaka> |
Component: | rubygems | Assignee: | Mamoru TASAKA <mtasaka> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 18 | CC: | dpierce, mastahnke, mtasaka, vanmeeuwen+fedora, vondruch |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-05-29 02:55:40 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: | 927378 |
Description
Mamoru TASAKA
2013-03-26 02:16:44 UTC
rubygems-1.8.25-6.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-4208/rubygems-1.8.25-6.fc18 rubygems-1.8.25-6.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2013-4161/rubygems-1.8.25-6.fc17 rubygem-qpid_proton-0.4-2.1.fc18.1 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/rubygem-qpid_proton-0.4-2.1.fc18.1 rubygem-qpid_proton-0.4-2.1.fc17.1 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/rubygem-qpid_proton-0.4-2.1.fc17.1 rubygem-qpid_messaging-0.20.2-1.fc17.1 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/rubygem-qpid_messaging-0.20.2-1.fc17.1 Packages in updates/updates-testing with broken C native extension paths are all rebuilt. Package rubygems-1.8.25-6.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 rubygems-1.8.25-6.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4161/rubygems-1.8.25-6.fc17 then log in and leave karma (feedback). rubygem-qpid_proton-0.4-2.2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/rubygem-qpid_proton-0.4-2.2.fc18 rubygem-qpid_proton-0.4-2.2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/rubygem-qpid_proton-0.4-2.2.fc17 rubygems-1.8.25-6.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. rubygem-qpid_messaging-0.20.2-1.fc17.1 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. rubygems-1.8.25-6.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. rubygem-qpid_proton-0.4-2.2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. rubygem-qpid_proton-0.4-2.2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. For at least rubygem-qpid_messaging this update didn't fix the problem entirely. The specfile still needs to create the directory %{buildroot}%{gem_extdir_mri}/lib, otherwise the native library that was built does not get installed as a part of the RPM. The RPM finishes building but is broken as a result. The other RPMs need to be checked as well to ensure that the RPM created works correctly. I've already fixed rubygem-qpid_messaging and rubygem-qpid_proton and will push updates on them shortly. The rest should be checked by either the package owner(s) or the BZ assignee. (In reply to Darryl L. Pierce from comment #15) > For at least rubygem-qpid_messaging this update didn't fix the problem > entirely. The specfile still needs to create the directory > %{buildroot}%{gem_extdir_mri}/lib, otherwise the native library that was > built does not get installed as a part of the RPM. The RPM finishes building > but is broken as a result. This bug ticket is for %%gem_extdir_mri macro wrongly written in rubygems.spec, and when %%gem_extdir_mri is used like mv foo.so %buildroot%%gem_extdir_mri/lib , foo.so was installed into wrong directory. If rubygem-qpid_messaging needs to create %buildroot%%gem_extdir_mri/lib beforehand, it is different issue. (In reply to Mamoru TASAKA from comment #16) > (In reply to Darryl L. Pierce from comment #15) > > For at least rubygem-qpid_messaging this update didn't fix the problem > > entirely. The specfile still needs to create the directory > > %{buildroot}%{gem_extdir_mri}/lib, otherwise the native library that was > > built does not get installed as a part of the RPM. The RPM finishes building > > but is broken as a result. > > This bug ticket is for %%gem_extdir_mri macro wrongly written in > rubygems.spec, > and when %%gem_extdir_mri is used like > mv foo.so %buildroot%%gem_extdir_mri/lib , foo.so was installed into wrong > directory. If rubygem-qpid_messaging needs to create > %buildroot%%gem_extdir_mri/lib beforehand, it is different issue. Note that usually gems creating native C extension have to create %buildroot%%gem_extdir_mri/lib manually (as written in ruby packaging guideline). |