Hello community,

here is the log from the commit of package rubygem-log4r for openSUSE:Factory 
checked in at 2014-02-25 07:37:08
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rubygem-log4r (Old)
 and      /work/SRC/openSUSE:Factory/.rubygem-log4r.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rubygem-log4r"

Changes:
--------
--- /work/SRC/openSUSE:Factory/rubygem-log4r/rubygem-log4r.changes      
2014-02-21 06:57:45.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.rubygem-log4r.new/rubygem-log4r.changes 
2014-02-25 07:37:09.000000000 +0100
@@ -1,0 +2,5 @@
+Sat Feb 22 06:25:43 UTC 2014 - [email protected]
+
+- use new macros
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ rubygem-log4r.spec ++++++
--- /var/tmp/diff_new_pack.F5bUZg/_old  2014-02-25 07:37:09.000000000 +0100
+++ /var/tmp/diff_new_pack.F5bUZg/_new  2014-02-25 07:37:09.000000000 +0100
@@ -23,7 +23,7 @@
 %define mod_full_name %{mod_name}-%{version}
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
-BuildRequires:  ruby-macros >= 1
+BuildRequires:  ruby-macros >= 3
 Url:            http://log4r.rubyforge.org
 Source:         http://rubygems.org/gems/%{mod_full_name}.gem
 Summary:        Log4r, logging framework for ruby
@@ -54,12 +54,12 @@
 
 %files
 %defattr(-,root,root,-)
-%{_libdir}/ruby/gems/%{rb_ver}/cache/%{mod_full_name}.gem
-%{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/
-%{_libdir}/ruby/gems/%{rb_ver}/specifications/%{mod_full_name}.gemspec
+%{gem_base}/cache/%{mod_full_name}.gem
+%{gem_base}/gems/%{mod_full_name}/
+%{gem_base}/specifications/%{mod_full_name}.gemspec
 
 %files doc
 %defattr(-,root,root,-)
-%doc %{_libdir}/ruby/gems/%{rb_ver}/doc/%{mod_full_name}/
+%doc %{gem_base}/doc
 
 %changelog


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

Reply via email to