Hello community,

here is the log from the commit of package yast2-cluster for openSUSE:Factory 
checked in at 2015-07-21 13:27:32
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-cluster (Old)
 and      /work/SRC/openSUSE:Factory/.yast2-cluster.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "yast2-cluster"

Changes:
--------
--- /work/SRC/openSUSE:Factory/yast2-cluster/yast2-cluster.changes      
2015-07-03 00:24:26.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-cluster.new/yast2-cluster.changes 
2015-07-21 13:29:08.000000000 +0200
@@ -1,0 +2,6 @@
+Mon Jul 20 06:51:20 UTC 2015 - nw...@suse.com
+
+- BSC#938325. Modify the not clear help and warning. 
+- Version 3.1.18
+
+-------------------------------------------------------------------

Old:
----
  yast2-cluster-3.1.17.tar.bz2

New:
----
  yast2-cluster-3.1.18.tar.bz2

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

Other differences:
------------------
++++++ yast2-cluster.spec ++++++
--- /var/tmp/diff_new_pack.kCWCqt/_old  2015-07-21 13:29:08.000000000 +0200
+++ /var/tmp/diff_new_pack.kCWCqt/_new  2015-07-21 13:29:08.000000000 +0200
@@ -18,7 +18,7 @@
 
 Name:           yast2-cluster
 %define _fwdefdir /etc/sysconfig/SuSEfirewall2.d/services
-Version:        3.1.17
+Version:        3.1.18
 Release:        0
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build

++++++ yast2-cluster-3.1.17.tar.bz2 -> yast2-cluster-3.1.18.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-cluster-3.1.17/package/yast2-cluster.changes 
new/yast2-cluster-3.1.18/package/yast2-cluster.changes
--- old/yast2-cluster-3.1.17/package/yast2-cluster.changes      2015-07-02 
09:21:37.000000000 +0200
+++ new/yast2-cluster-3.1.18/package/yast2-cluster.changes      2015-07-20 
08:56:38.000000000 +0200
@@ -1,4 +1,10 @@
 -------------------------------------------------------------------
+Mon Jul 20 06:51:20 UTC 2015 - nw...@suse.com
+
+- BSC#938325. Modify the not clear help and warning. 
+- Version 3.1.18
+
+-------------------------------------------------------------------
 Thu Jul  2 07:16:47 UTC 2015 - nw...@suse.com
 
 - FATE#318190. Add a warning in corosync.conf to warn users
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-cluster-3.1.17/package/yast2-cluster.spec 
new/yast2-cluster-3.1.18/package/yast2-cluster.spec
--- old/yast2-cluster-3.1.17/package/yast2-cluster.spec 2015-07-02 
09:21:37.000000000 +0200
+++ new/yast2-cluster-3.1.18/package/yast2-cluster.spec 2015-07-20 
08:56:38.000000000 +0200
@@ -18,7 +18,7 @@
 
 Name:           yast2-cluster
 %define _fwdefdir /etc/sysconfig/SuSEfirewall2.d/services
-Version:        3.1.17
+Version:        3.1.18
 Release:        0
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-cluster-3.1.17/src/include/cluster/dialogs.rb 
new/yast2-cluster-3.1.18/src/include/cluster/dialogs.rb
--- old/yast2-cluster-3.1.17/src/include/cluster/dialogs.rb     2015-07-02 
09:21:37.000000000 +0200
+++ new/yast2-cluster-3.1.18/src/include/cluster/dialogs.rb     2015-07-20 
08:56:38.000000000 +0200
@@ -217,7 +217,7 @@
       else
         #BNC#880242, expected_votes must have value when "udp"
         if UI.QueryWidget(Id(:expected_votes), :Value) == ""
-          Popup.Message(_("The Expected Votes has to be fulfilled when udp is 
configured"))
+          Popup.Message(_("The Expected Votes has to be fulfilled when 
multicast transport is configured"))
           UI.SetFocus(:expected_votes)
           return false
         end
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-cluster-3.1.17/src/include/cluster/helps.rb 
new/yast2-cluster-3.1.18/src/include/cluster/helps.rb
--- old/yast2-cluster-3.1.17/src/include/cluster/helps.rb       2015-07-02 
09:21:37.000000000 +0200
+++ new/yast2-cluster-3.1.18/src/include/cluster/helps.rb       2015-07-20 
08:56:38.000000000 +0200
@@ -39,7 +39,7 @@
             "<p><b><big>Member Address</big></b><br>This list specifies all 
the nodes in the cluster by IP address. This could be configurable when using 
udpu(Unicast). <br></p>\n" +
             "<p><b><big>Node ID</big></b><br>This  configuration  option  is  
optional  when  using  IPv4 and required when using IPv6.  This is a 32 bit 
value specifying the node identifier delivered to the cluster membership 
service.  If this is not specified with IPv4, the node id will be  determined 
from  the  32  bit  IP address the system to which the system is bound with 
ring identifier of 0.  The node identifier  value  of zero is reserved and 
should not be used.<br></p>\n" +
             "<p><b><big>rrp_mode</big></b><br>This specifies the mode of 
redundant ring, which  may  be  none, active,  or  passive.   Active 
replication offers slightly lower latency from transmit to delivery in faulty 
network environments but  with less performance.  Passive replication may 
nearly double the speed of the totem  protocol  if  the  protocol  doesn't 
become  cpu bound.  The final option is none, in which case only one network 
interface will be used to operate the  totem  protocol.  If  only one interface 
directive is specified, none is automatically chosen.  If multiple interface 
directives  are  specified, only active or passive may be chosen.<br></p>\n" +
-            "<p><b><big>Expected votes</big></b><br>Expect vote number for 
voting quorum.  Will be automatically calculated when the nodelist {} section 
is present in corosync.conf or can be specified in the quorum {} 
section.<br></p>\n" +
+            "<p><b><big>Expected votes</big></b><br>Expect vote number for 
voting quorum.  Will be automatically calculated when the nodelist {} section 
is present in corosync.conf (the list will be generated when using unicast 
transport) or can be specified in the quorum {} section (Expect votes should 
use the total node numble of the cluster). If Expected votes presents in 
unicast transport, the value will override the one automatically 
calculated.<br></p>\n" +
             "<p><b><big>Auto Generate Node ID</big></b><br>Nodeid is required 
when using IPv6. Auto node ID enabled will generate nodeid 
automatically.<br></p>\n"
         ),
         "security"      => _(


Reply via email to