Hello community,

here is the log from the commit of package xorg-x11-libxcb for openSUSE:Factory 
checked in at 2011-11-23 19:38:40
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/xorg-x11-libxcb (Old)
 and      /work/SRC/openSUSE:Factory/.xorg-x11-libxcb.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "xorg-x11-libxcb", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/xorg-x11-libxcb/xorg-x11-libxcb.changes  
2011-09-23 12:52:36.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.xorg-x11-libxcb.new/xorg-x11-libxcb.changes     
2011-11-23 19:39:28.000000000 +0100
@@ -1,0 +2,5 @@
+Sun Nov 20 06:49:34 UTC 2011 - [email protected]
+
+- add libtool as buildrequire to avoid implicit dependency
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ xorg-x11-libxcb.spec ++++++
--- /var/tmp/diff_new_pack.DYnKy3/_old  2011-11-23 19:39:30.000000000 +0100
+++ /var/tmp/diff_new_pack.DYnKy3/_new  2011-11-23 19:39:30.000000000 +0100
@@ -1,7 +1,7 @@
 #
-# spec file for package xorg-x11-libxcb (Version 7.6_1.7)
+# spec file for package xorg-x11-libxcb
 #
-# Copyright (c) 2010 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
@@ -20,7 +20,7 @@
 
 Name:           xorg-x11-libxcb
 %define dirsuffix 1.7
-BuildRequires:  libxslt pkgconfig python-base python-xml xorg-x11-libXau-devel 
xorg-x11-proto-devel
+BuildRequires:  libtool libxslt pkgconfig python-base python-xml 
xorg-x11-libXau-devel xorg-x11-proto-devel
 #%ifarch ppc64 s390x x86_64
 #Provides:       libxcb-xlib.so.0()(64bit)
 #%else


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

Reply via email to