Hello community,

here is the log from the commit of package libbitmask for openSUSE:Factory 
checked in at 2011-11-14 11:58:58
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libbitmask (Old)
 and      /work/SRC/openSUSE:Factory/.libbitmask.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libbitmask", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/libbitmask/libbitmask.changes    2011-09-23 
02:07:51.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.libbitmask.new/libbitmask.changes       
2011-11-14 11:58:59.000000000 +0100
@@ -1,0 +2,5 @@
+Sun Nov 13 09:13:50 UTC 2011 - [email protected]
+
+- add libtool as explicit buildrequire to avoid implicit dependency from 
prjconf
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ libbitmask.spec ++++++
--- /var/tmp/diff_new_pack.WIui9k/_old  2011-11-14 11:59:00.000000000 +0100
+++ /var/tmp/diff_new_pack.WIui9k/_new  2011-11-14 11:59:00.000000000 +0100
@@ -1,7 +1,7 @@
 #
-# spec file for package libbitmask (Version 2.0)
+# spec file for package libbitmask
 #
-# Copyright (c) 2009 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2011 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
@@ -24,9 +24,9 @@
 Summary:        Multi-word bitmask abstract data type (used by cpusets)
 Version:        2.0
 Release:        5
-AutoReqProv:    on
 Source:         libbitmask-%{version}.tar.bz2
 Group:          Development/Languages/C and C++
+BuildRequires:  libtool
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 %define debug_package_requires libbitmask1 = %{version}-%{release}
 

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

Reply via email to