Description of problem: Ah....... %%gem_extdir_mri should be %%{_libdir}/gems/exts/%%{gem_name}-%%{version} on F-18 and below, not %%{_libdir}/gems/ruby/%%{gem_name}-%%{version} Version-Release number of selected component (if applicable): rubygems-1.8.25-5.fc18 Additional info: Affects: $ repoquery --disablerepo=\* --enablerepo=updates-testing --enablerepo=updates --whatprovides '/usr/lib/gems/ruby/*' Skipping unreadable repository '///etc/yum.repos.d/LOCAL.repo' rubygem-rsvg2-0:1.2.3-1.fc18.i686 rubygem-atk-0:1.2.3-1.fc18.i686 rubygem-goocanvas-0:1.2.3-1.fc18.i686 rubygem-glib2-0:1.2.3-1.fc18.i686 rubygem-gtksourceview2-0:1.2.3-1.fc18.i686 rubygem-gstreamer-0:1.2.3-1.fc18.i686 rubygem-vte-0:1.2.3-1.fc18.i686 rubygem-gdk_pixbuf2-0:1.2.3-1.fc18.i686 rubygem-poppler-0:1.2.3-1.fc18.i686 rubygem-qpid_proton-0:0.4-2.1.fc18.i686 rubygem-pango-0:1.2.3-1.fc18.i686 rubygem-gtk2-0:1.2.3-1.fc18.i686 rubygem-gobject-introspection-0:1.2.3-1.fc18.i686 rubygem-cairo-0:1.12.4-1.fc18.i686 rubygem-gio2-0:1.2.3-1.fc18.i686 ]$ repoquery --disablerepo=\* --releasever=17 --enablerepo=updates-testing --enablerepo=updates --whatprovides '/usr/lib/gems/ruby/*' Skipping unreadable repository '///etc/yum.repos.d/LOCAL.repo' rubygem-rsvg2-0:1.2.3-1.fc17.i686 rubygem-goocanvas-0:1.2.3-1.fc17.i686 rubygem-qpid_messaging-0:0.20.2-1.fc17.i686 rubygem-poppler-0:1.2.3-1.fc17.i686 rubygem-pango-0:1.2.3-1.fc17.i686 rubygem-gio2-0:1.2.3-1.fc17.i686 rubygem-gdk_pixbuf2-0:1.2.3-1.fc17.i686 rubygem-gstreamer-0:1.2.3-1.fc17.i686 rubygem-atk-0:1.2.3-1.fc17.i686 rubygem-gtksourceview2-0:1.2.3-1.fc17.i686 rubygem-qpid_proton-0:0.4-2.1.fc17.i686 rubygem-glib2-0:1.2.3-1.fc17.i686 rubygem-gtk2-0:1.2.3-1.fc17.i686 rubygem-gobject-introspection-0:1.2.3-1.fc17.i686 rubygem-vte-0:1.2.3-1.fc17.i686 rubygem-cairo-0:1.12.4-1.fc17.i686
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).