Hello community,

here is the log from the commit of package audit-visualize for openSUSE:Factory
checked in at Wed Sep 28 17:41:06 CEST 2011.



--------
--- audit-visualize/audit-visualize.changes     2007-05-06 17:09:46.000000000 
+0200
+++ /mounts/work_src_done/STABLE/audit-visualize/audit-visualize.changes        
2011-09-17 15:39:34.000000000 +0200
@@ -1,0 +2,5 @@
+Sat Sep 17 13:39:23 UTC 2011 - [email protected]
+
+- Remove redundant tags/sections from specfile
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


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

Other differences:
------------------
++++++ audit-visualize.spec ++++++
--- /var/tmp/diff_new_pack.tziuzQ/_old  2011-09-28 17:40:40.000000000 +0200
+++ /var/tmp/diff_new_pack.tziuzQ/_new  2011-09-28 17:40:40.000000000 +0200
@@ -1,7 +1,7 @@
 #
-# spec file for package audit-visualize (Version 1.5.2)
+# spec file for package audit-visualize
 #
-# 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
@@ -15,7 +15,6 @@
 # Please submit bugfixes or comments via http://bugs.opensuse.org/
 #
 
-# norootforbuild
 
 
 Name:           audit-visualize
@@ -36,22 +35,15 @@
 The audit-visualize package contains scripts to produce flow graphs and
 bar charts from audit data.
 
-
-
-Authors:
---------
-    [email protected]
-
 %prep
 %setup -q -n audit-visualize
 
+%build
+
 %install
 mkdir -p $RPM_BUILD_ROOT/%_prefix/lib/%_name/visualize
 mv README mkbar mkgraph $RPM_BUILD_ROOT/%_prefix/lib/%_name/visualize
 
-%clean
-rm -rf $RPM_BUILD_ROOT
-
 %files
 %defattr(-,root,root,-)
 %dir %attr(755,root,root) %_prefix/lib/%_name


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



Remember to have fun...

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

Reply via email to