Hello community,

here is the log from the commit of package libotr for openSUSE:Factory checked 
in at 2011-11-21 15:47:20
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libotr (Old)
 and      /work/SRC/openSUSE:Factory/.libotr.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

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

Changes:
--------
--- /work/SRC/openSUSE:Factory/libotr/libotr.changes    2011-09-23 
02:09:13.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.libotr.new/libotr.changes       2011-11-21 
15:47:23.000000000 +0100
@@ -1,0 +2,5 @@
+Sun Nov 20 06:17:12 UTC 2011 - [email protected]
+
+- add libtool as buildrequire to avoid implicit dependency
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ libotr.spec ++++++
--- /var/tmp/diff_new_pack.pep2LH/_old  2011-11-21 15:47:24.000000000 +0100
+++ /var/tmp/diff_new_pack.pep2LH/_new  2011-11-21 15:47:24.000000000 +0100
@@ -1,7 +1,7 @@
 #
-# spec file for package libotr (Version 3.2.0)
+# spec file for package libotr
 #
-# Copyright (c) 2008 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
@@ -19,7 +19,7 @@
 
 
 Name:           libotr
-BuildRequires:  libgcrypt-devel
+BuildRequires:  libgcrypt-devel libtool
 Version:        3.2.0
 Release:        1
 Url:            http://www.cypherpunks.ca/otr/
@@ -27,7 +27,6 @@
 License:        LGPL v2.1 or later
 Summary:        "Off The Record" messaging library toolkit
 Source:         http://www.cypherpunks.ca/otr/%{name}-%{version}.tar.bz2
-AutoReqProv:    on
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 
 %description

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

Reply via email to