Hello community,

here is the log from the commit of package libustr for openSUSE:Factory
checked in at Mon May 23 10:06:41 CEST 2011.



--------
--- libustr/libustr.changes     2010-04-30 20:09:45.000000000 +0200
+++ /mounts/work_src_done/STABLE/libustr/libustr.changes        2011-05-19 
14:21:58.000000000 +0200
@@ -1,0 +2,5 @@
+Thu May 19 12:21:41 UTC 2011 - [email protected]
+
+- add 32bit compat for libsemanage-32bit to use
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


New:
----
  baselibs.conf

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

Other differences:
------------------
++++++ libustr.spec ++++++
--- /var/tmp/diff_new_pack.znHYOG/_old  2011-05-23 10:05:55.000000000 +0200
+++ /var/tmp/diff_new_pack.znHYOG/_new  2011-05-23 10:05:55.000000000 +0200
@@ -1,7 +1,7 @@
 #
-# spec file for package libustr (Version 1.0.4)
+# spec file for package libustr
 #
-# 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,13 +20,14 @@
 
 Name:           libustr
 Version:        1.0.4
-Release:        6
+Release:        16
 Url:            http://www.and.org/ustr/
 License:        MIT or LGPLv2+ or BSD
 Group:          System/Libraries
 Summary:        String library, very low memory overhead, simple to import
 Source:         http://www.and.org/ustr/%{version}/ustr-%{version}.tar.bz2
 Source1:        rpmlintrc
+Source2:        baselibs.conf
 Patch0:         %{name}-%{version}-c99-inline.patch
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 BuildRequires:  pkg-config

++++++ baselibs.conf ++++++
libustr-1_0-1

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



Remember to have fun...

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

Reply via email to