Hello community,

here is the log from the commit of package rubygem-xmlhash for openSUSE:Factory 
checked in at 2013-07-22 14:07:41
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rubygem-xmlhash (Old)
 and      /work/SRC/openSUSE:Factory/.rubygem-xmlhash.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rubygem-xmlhash"

Changes:
--------
--- /work/SRC/openSUSE:Factory/rubygem-xmlhash/rubygem-xmlhash.changes  
2013-05-16 11:35:33.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.rubygem-xmlhash.new/rubygem-xmlhash.changes     
2013-07-22 14:07:42.000000000 +0200
@@ -1,0 +2,10 @@
+Sun Jul 21 19:06:07 UTC 2013 - [email protected]
+
+- fix update case with a %pre hack
+
+-------------------------------------------------------------------
+Thu Jun 27 07:52:17 UTC 2013 - [email protected]
+
+- do not break recent ruby with old workaround
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ rubygem-xmlhash.spec ++++++
--- /var/tmp/diff_new_pack.2stuiJ/_old  2013-07-22 14:07:42.000000000 +0200
+++ /var/tmp/diff_new_pack.2stuiJ/_new  2013-07-22 14:07:42.000000000 +0200
@@ -54,9 +54,18 @@
 %gem_install
 %gem_cleanup
 cd %{buildroot}%_libdir/ruby/gems/%{rb_ver}/gems/%{mod_full_name}
-mv lib/xmlhash lib/xmlhash.so
-mkdir lib/xmlhash
-mv lib/xmlhash.so lib/xmlhash/xmlhash.so
+# workaround
+if test -f lib/xmlhash; then
+  mv lib/xmlhash lib/xmlhash.so
+  mkdir lib/xmlhash
+  mv lib/xmlhash.so lib/xmlhash/xmlhash.so
+fi
+
+%pre
+# a .so directory is invalid, but rpm won't be able to move it to a file 
itself ;(
+if test -d 
%_libdir/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/lib/xmlhash/xmlhash.so; then
+  rm -rf 
%_libdir/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/lib/xmlhash/xmlhash.so
+fi
 
 %check
 cd %{mod_full_name}


-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to