Hello community,

here is the log from the commit of package yast2-nfs-client for 
openSUSE:Factory checked in at 2014-06-02 07:04:15
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-nfs-client (Old)
 and      /work/SRC/openSUSE:Factory/.yast2-nfs-client.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "yast2-nfs-client"

Changes:
--------
--- /work/SRC/openSUSE:Factory/yast2-nfs-client/yast2-nfs-client.changes        
2014-05-06 13:40:53.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-nfs-client.new/yast2-nfs-client.changes   
2014-06-02 07:04:17.000000000 +0200
@@ -1,0 +2,6 @@
+Wed May 21 09:41:45 UTC 2014 - [email protected]
+
+- Fix building with nfs-utils-1.3.0 (bnc#878875).
+- 3.1.5
+
+-------------------------------------------------------------------

Old:
----
  yast2-nfs-client-3.1.4.tar.bz2

New:
----
  yast2-nfs-client-3.1.5.tar.bz2

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

Other differences:
------------------
++++++ yast2-nfs-client.spec ++++++
--- /var/tmp/diff_new_pack.WOu0j6/_old  2014-06-02 07:04:18.000000000 +0200
+++ /var/tmp/diff_new_pack.WOu0j6/_new  2014-06-02 07:04:18.000000000 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           yast2-nfs-client
-Version:        3.1.4
+Version:        3.1.5
 Release:        0
 Url:            https://github.com/yast/yast-nfs-client
 
@@ -33,7 +33,11 @@
 # yast2-nfs-client depends on nfs-utils in term that edits nfs-utils' options.
 # Support was checked against nfs-utils 1.2.7.
 # As soon as nfs-utils reaches version 1.2.9 there should be another update.
-BuildRequires:  nfs-client < 1.2.9
+# FIXME: 1.3.0 works but adds these new options we need to handle:
+# - multiple "sec" with colons
+# - "migration"
+# - "v4.1" v4.x
+BuildRequires:  nfs-client < 1.3.1
 BuildRequires:  rubygem-rspec
 #ag_showexports moved to yast2 base
 # introduces extended IPv6 support.

++++++ yast2-nfs-client-3.1.4.tar.bz2 -> yast2-nfs-client-3.1.5.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-nfs-client-3.1.4/package/yast2-nfs-client.changes 
new/yast2-nfs-client-3.1.5/package/yast2-nfs-client.changes
--- old/yast2-nfs-client-3.1.4/package/yast2-nfs-client.changes 2014-05-05 
15:52:50.000000000 +0200
+++ new/yast2-nfs-client-3.1.5/package/yast2-nfs-client.changes 2014-05-21 
11:52:20.000000000 +0200
@@ -1,4 +1,10 @@
 -------------------------------------------------------------------
+Wed May 21 09:41:45 UTC 2014 - [email protected]
+
+- Fix building with nfs-utils-1.3.0 (bnc#878875).
+- 3.1.5
+
+-------------------------------------------------------------------
 Mon May  5 14:49:12 CEST 2014 - [email protected]
 
 - Obsolete Service.Status replaced with new Service.active?
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-nfs-client-3.1.4/package/yast2-nfs-client.spec 
new/yast2-nfs-client-3.1.5/package/yast2-nfs-client.spec
--- old/yast2-nfs-client-3.1.4/package/yast2-nfs-client.spec    2014-05-05 
15:52:50.000000000 +0200
+++ new/yast2-nfs-client-3.1.5/package/yast2-nfs-client.spec    2014-05-21 
11:52:20.000000000 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           yast2-nfs-client
-Version:        3.1.4
+Version:        3.1.5
 Release:        0
 Url:            https://github.com/yast/yast-nfs-client
 
@@ -33,7 +33,11 @@
 # yast2-nfs-client depends on nfs-utils in term that edits nfs-utils' options.
 # Support was checked against nfs-utils 1.2.7.
 # As soon as nfs-utils reaches version 1.2.9 there should be another update.
-BuildRequires:  nfs-client < 1.2.9
+# FIXME: 1.3.0 works but adds these new options we need to handle:
+# - multiple "sec" with colons
+# - "migration"
+# - "v4.1" v4.x
+BuildRequires:  nfs-client < 1.3.1
 BuildRequires:  rubygem-rspec
 #ag_showexports moved to yast2 base
 # introduces extended IPv6 support.

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

Reply via email to