Hello community,

here is the log from the commit of package rubygem-yast-rake for 
openSUSE:Factory checked in at 2014-06-17 11:22:51
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rubygem-yast-rake (Old)
 and      /work/SRC/openSUSE:Factory/.rubygem-yast-rake.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rubygem-yast-rake"

Changes:
--------
--- /work/SRC/openSUSE:Factory/rubygem-yast-rake/rubygem-yast-rake.changes      
2014-01-16 15:13:48.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.rubygem-yast-rake.new/rubygem-yast-rake.changes 
2014-06-17 11:22:57.000000000 +0200
@@ -1,0 +2,12 @@
+Mon Jun  9 07:38:51 UTC 2014 - [email protected]
+
+- install: Fix matching for autoyast-rnc directory
+- 0.1.8
+
+-------------------------------------------------------------------
+Fri Jun  6 13:41:03 CEST 2014 - [email protected]
+
+- Added support for Yast "data" directory
+- 0.1.7
+
+-------------------------------------------------------------------

Old:
----
  yast-rake-0.1.6.gem

New:
----
  yast-rake-0.1.8.gem

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

Other differences:
------------------
++++++ rubygem-yast-rake.spec ++++++
--- /var/tmp/diff_new_pack.9QCMiY/_old  2014-06-17 11:22:58.000000000 +0200
+++ /var/tmp/diff_new_pack.9QCMiY/_new  2014-06-17 11:22:58.000000000 +0200
@@ -17,14 +17,14 @@
 
 
 Name:           rubygem-yast-rake
-Version:        0.1.6
+Version:        0.1.8
 Release:        0
 %define mod_name yast-rake
 %define mod_full_name %{mod_name}-%{version}
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 BuildRequires:  ruby-macros >= 1
-Url:            http://github.org/openSUSE/yast-rake
+Url:            http://github.org/yast/yast-rake
 Source:         http://rubygems.org/gems/%{mod_full_name}.gem
 Summary:        Rake tasks providing basic work-flow for Yast development
 License:        LGPL-2.1

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

Reply via email to