Hello community,

here is the log from the commit of package brltty for openSUSE:Factory
checked in at Wed May 25 09:28:59 CEST 2011.



--------
--- brltty/brltty.changes       2010-09-19 12:27:53.000000000 +0200
+++ /mounts/work_src_done/STABLE/brltty/brltty.changes  2011-05-24 
21:50:53.000000000 +0200
@@ -1,0 +2,5 @@
+Tue May 24 19:50:20 UTC 2011 - [email protected]
+
+- remove timestamps from binaries, breaks build-compare 
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


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

Other differences:
------------------
++++++ brltty.spec ++++++
--- /var/tmp/diff_new_pack.Tzidzw/_old  2011-05-25 09:26:39.000000000 +0200
+++ /var/tmp/diff_new_pack.Tzidzw/_new  2011-05-25 09:26:39.000000000 +0200
@@ -1,7 +1,7 @@
 #
-# spec file for package brltty (Version 4.2)
+# spec file for package brltty
 #
-# 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
@@ -19,7 +19,7 @@
 
 Name:           brltty
 Version:        4.2
-Release:        1
+Release:        10
 # FIXME tcl bindings: investigate how to not fail in brp-tcl
 # FIXME libbraille driver when libbraille is in factory
 License:        GPLv2+
@@ -279,6 +279,10 @@
 %patch2 -p1
 
 %build
+modified="$(sed -n '/^----/n;s/ - .*$//;p;q' "%{_sourcedir}/%{name}.changes")"
+DATE="\"$(date -d "${modified}" "+%%b %%e %%Y")\""
+TIME="\"$(date -d "${modified}" "+%%R")\""
+find . -type f -regex ".*\.c\|.*\.cpp\|.*\.h" -exec sed -i 
"s/__DATE__/${DATE}/g;s/__TIME__/${TIME}/g" {} +
 for i in -I%{_libdir}/jvm/java/include{,/linux}; do
       java_inc="$java_inc $i"
 done


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



Remember to have fun...

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

Reply via email to