Hello community,

here is the log from the commit of package brp-check-suse for openSUSE:Factory
checked in at Mon May 2 14:39:21 CEST 2011.



--------
--- brp-check-suse/brp-check-suse.changes       2011-03-04 19:41:26.000000000 
+0100
+++ /mounts/work_src_done/STABLE/brp-check-suse/brp-check-suse.changes  
2011-04-29 01:48:29.000000000 +0200
@@ -1,0 +2,5 @@
+Fri Apr 29 01:48:13 CEST 2011 - [email protected]
+
+- try to make sure it really is a libtool file before taking any action
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


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

Other differences:
------------------
++++++ brp-check-suse.spec ++++++
--- /var/tmp/diff_new_pack.azqoRt/_old  2011-05-02 14:38:20.000000000 +0200
+++ /var/tmp/diff_new_pack.azqoRt/_new  2011-05-02 14:38:20.000000000 +0200
@@ -24,7 +24,7 @@
 AutoReqProv:    off
 Summary:        build root policy check scripts
 Version:        1.0
-Release:        39
+Release:        40
 Source0:        %{name}-%{version}.tar.bz2
 BuildArch:      noarch
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build

++++++ brp-check-suse-1.0.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/brp-check-suse-1.0/brp-check-la 
new/brp-check-suse-1.0/brp-check-la
--- old/brp-check-suse-1.0/brp-check-la 2011-01-13 14:25:30.000000000 +0100
+++ new/brp-check-suse-1.0/brp-check-la 2011-04-29 01:47:19.000000000 +0200
@@ -6,6 +6,9 @@
 
 MASTER_ERROR_CODE=0
 for f in `find $RPM_BUILD_ROOT -type f -name "*.la" ` ; do
+   # first try to see if this really looks like a libtool file
+   grep -q "libdir=" $f || continue
+   grep -q "library_names=" $f || continue
    ERROR_CODE=0
    grep -q  "libdir=.*$RPM_BUILD_ROOT" $f && ERROR_CODE=1
    grep -q "libdir=.*/usr/src/packages/BUILD/" $f && ERROR_CODE=2


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



Remember to have fun...

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

Reply via email to