Hello community,

here is the log from the commit of package yast2-sudo for openSUSE:Factory 
checked in at 2013-08-01 11:10:15
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-sudo (Old)
 and      /work/SRC/openSUSE:Factory/.yast2-sudo.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "yast2-sudo"

Changes:
--------
--- /work/SRC/openSUSE:Factory/yast2-sudo/yast2-sudo.changes    2013-05-27 
10:14:30.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-sudo.new/yast2-sudo.changes       
2013-08-01 11:10:16.000000000 +0200
@@ -1,0 +2,7 @@
+Wed Jul 31 08:42:46 UTC 2013 - [email protected]
+
+- converted from YCP to Ruby by YCP Killer
+  (https://github.com/yast/ycp-killer)
+- version 3.0.0
+
+-------------------------------------------------------------------

Old:
----
  yast2-sudo-2.24.0.tar.bz2

New:
----
  yast2-sudo-3.0.0.tar.bz2

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

Other differences:
------------------
++++++ yast2-sudo.spec ++++++
--- /var/tmp/diff_new_pack.qknyAj/_old  2013-08-01 11:10:17.000000000 +0200
+++ /var/tmp/diff_new_pack.qknyAj/_new  2013-08-01 11:10:17.000000000 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           yast2-sudo
-Version:        2.24.0
+Version:        3.0.0
 Release:        0
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
@@ -39,6 +39,8 @@
 
 BuildArch:      noarch
 
+Requires:       yast2-ruby-bindings >= 1.0.0
+
 Summary:        YaST2 - sudo configuration
 License:        GPL-2.0
 Group:          System/YaST
@@ -78,7 +80,7 @@
 %defattr(-,root,root)
 %dir /usr/share/YaST2/include/sudo
 /usr/share/YaST2/include/sudo/*
-/usr/share/YaST2/clients/sudo.ycp
+/usr/share/YaST2/clients/sudo.rb
 /usr/share/YaST2/modules/Sudo.*
 %{_prefix}/share/applications/YaST2/sudo.desktop
 /usr/share/YaST2/scrconf/sudo.scr

++++++ yast2-sudo-2.24.0.tar.bz2 -> yast2-sudo-3.0.0.tar.bz2 ++++++
++++ 7388 lines of diff (skipped)

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

Reply via email to