Bug 1051236

Summary:	ruby-libvirt 0.5.2 ships prebuilt 64-bit binaries
Product:	[Fedora] Fedora	Reporter:	Ville Skyttä <ville.skytta>
Component:	ruby-libvirt	Assignee:	Chris Lalancette <clalancette>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	20	CC:	clalancette, mastahnke, virt-maint
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:	2014-10-11 04:17:38 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:	496968

Description Ville Skyttä 2014-01-09 21:55:50 UTC

ruby-libvirt 0.5.2 ships prebuilt 64-bit binaries on all arches and distros because the upstream tarball is dirty and contains them. One way to fix it:

diff --git a/ruby-libvirt.spec b/ruby-libvirt.spec
index b450aa4..c223ce9 100644
--- a/ruby-libvirt.spec
+++ b/ruby-libvirt.spec
@@ -24,2 +24,3 @@ Ruby bindings for libvirt.
 %setup -q
+rake clean # 0.5.2 tarball is unclean, contains *.o and *.so binaries

Comment 1 Chris Lalancette 2014-01-09 22:13:25 UTC

Bah humbug.  The tarball I checked into Fedora does have that junk in it, while the real upstream tarball (from libvirt.org/ruby) does not.  I'm not sure how I screwed that up.  I'll fix it.

Thanks for the report!

Comment 2 Michael Stahnke 2014-10-11 04:17:38 UTC

This appears to be fixed in F20 and EL6 which use 0.5.2. Closing.