Hello community,

here is the log from the commit of package kipi-plugins for openSUSE:Factory
checked in at Wed Aug 3 10:59:59 CEST 2011.



--------
--- KDE/kipi-plugins/kipi-plugins.changes       2011-07-28 11:41:36.000000000 
+0200
+++ /mounts/work_src_done/STABLE/kipi-plugins/kipi-plugins.changes      
2011-08-03 09:38:49.000000000 +0200
@@ -1,0 +2,5 @@
+Tue Aug  2 12:06:35 UTC 2011 - [email protected]
+
+- Strictly require libkdcraw-devel >= 4.7.0 
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


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

Other differences:
------------------
++++++ kipi-plugins.spec ++++++
--- /var/tmp/diff_new_pack.5iNeGj/_old  2011-08-03 10:59:40.000000000 +0200
+++ /var/tmp/diff_new_pack.5iNeGj/_new  2011-08-03 10:59:40.000000000 +0200
@@ -19,7 +19,7 @@
 
 Name:           kipi-plugins
 Version:        2.0.0
-Release:        1
+Release:        3
 License:        BSD3c(or similar) ; GPLv2+ ; LGPLv2.1+ ; MIT License (or 
similar)
 Summary:        KDE Plug-Ins for Image Manipulation
 Url:            http://www.kipi-plugins.org/
@@ -36,7 +36,7 @@
 BuildRequires:  libgphoto2-devel
 BuildRequires:  libgpod-devel
 BuildRequires:  libjasper-devel
-BuildRequires:  libkdcraw-devel
+BuildRequires:  libkdcraw-devel >= 4.7.0
 BuildRequires:  libkdepimlibs4-devel
 BuildRequires:  libkexiv2-devel
 BuildRequires:  libkipi-devel
@@ -97,7 +97,7 @@
 %patch
 # Remove build time references so build-compare can do its work
 FAKE_BUILDDATE=$(LC_ALL=C date -r %{_sourcedir}/%{name}.changes '+%b %e %Y')
-sed -i "s/__DATE__/\"$FAKE_BUILDDATE\"/" 
common/libkipiplugins/pluginsversion.h.cmake
+sed -i "s/__DATE__/\"$FAKE_BUILDDATE\"/g" 
common/libkipiplugins/pluginsversion.h.cmake
 
 # Add docs & translations
 echo "add_subdirectory( doc )" >> CMakeLists.txt


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



Remember to have fun...

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

Reply via email to