Hello community,

here is the log from the commit of package fence-agents for openSUSE:Factory 
checked in at 2013-11-04 07:05:41
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/fence-agents (Old)
 and      /work/SRC/openSUSE:Factory/.fence-agents.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "fence-agents"

Changes:
--------
--- /work/SRC/openSUSE:Factory/fence-agents/fence-agents.changes        
2013-09-26 11:43:13.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.fence-agents.new/fence-agents.changes   
2013-11-04 07:05:42.000000000 +0100
@@ -1,0 +2,19 @@
+Thu Oct 31 13:55:12 UTC 2013 - [email protected]
+
+- Update to version 4.0.5
+
+  + fence agent for RSB now works correctly also with newer 
+    firmware
+
+  + fence agent for WTI now supports not only port numbers but also
+    named port groups 
+
+  + fence agent for VMWare SOAP now report if user does not have 
+    enough privileges 
+
+  + add a Relax NG for XML metadata of fence agents and require 
+    them to be correct in order to build a fence agent
+
+  + fix problems found thanks to previous Relax NG
+
+-------------------------------------------------------------------

Old:
----
  fence-agents-4.0.3.tar.xz

New:
----
  fence-agents-4.0.5.tar.xz

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

Other differences:
------------------
++++++ fence-agents.spec ++++++
--- /var/tmp/diff_new_pack.pBXvM1/_old  2013-11-04 07:05:43.000000000 +0100
+++ /var/tmp/diff_new_pack.pBXvM1/_new  2013-11-04 07:05:43.000000000 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package fence-agents
 #
-# Copyright (c) 2012 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -20,39 +20,45 @@
 
 Name:           fence-agents
 Summary:        Fence Agents for Pacemaker from RHCS
-Version:        4.0.3
-Release:        0
 License:        GPL-2.0 and LGPL-2.1
 Group:          Productivity/Clustering/HA
+Version:        4.0.5
+Release:        0
 Url:            http://git.fedorahosted.org/git/fence-agents.git
 Source0:        
https://fedorahosted.org/releases/f/e/fence-agents/%{name}-%{version}.tar.xz
 Patch1:         fence-agents-add-longdesc.patch
-Requires:       python-pexpect
 Requires:       python-curl
 Requires:       python-openssl
+Requires:       python-pexpect
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
-BuildRequires:  perl
 BuildRequires:  glibc-devel
+BuildRequires:  libxml2-tools
 BuildRequires:  libxslt
-BuildRequires:  python python-curl python-suds
-BuildRequires:  pkg-config python-xml xz
-BuildRequires:  mozilla-nspr-devel mozilla-nss-devel
-BuildRequires:  python-pexpect
+BuildRequires:  mozilla-nspr-devel
+BuildRequires:  mozilla-nss-devel
+BuildRequires:  perl
 BuildRequires:  perl-Net-Telnet
+BuildRequires:  pkg-config
+BuildRequires:  python
+BuildRequires:  python-curl
+BuildRequires:  python-pexpect
+BuildRequires:  python-suds
+BuildRequires:  python-xml
+BuildRequires:  xz
 
 %package -n fence-agents-unsupported
 Summary:        Fence Agents for Pacemaker from RHCS
-License:        GPL-2.0 and LGPL-2.1
 Group:          Productivity/Clustering/HA
 Requires:       %{name} = %{version}-%{release}
 # These are requirements of specific fencing agents; when moving the
 # agent over to the supported main package, make sure to also shift the
 # Requires if needed
-Requires:       sg3_utils telnet
 Requires:       net-snmp
-Requires:       perl-Net-Telnet
 Requires:       openssh
+Requires:       perl-Net-Telnet
+Requires:       sg3_utils
+Requires:       telnet
 # for fence_vmware_soap:
 Requires:       python-suds
 # This is required by fence_virsh. Per discussion on fedora-devel

++++++ fence-agents-4.0.3.tar.xz -> fence-agents-4.0.5.tar.xz ++++++
++++ 5207 lines of diff (skipped)

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

Reply via email to