Hello community,

here is the log from the commit of package planner for openSUSE:Factory checked 
in at 2013-12-17 10:02:42
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/planner (Old)
 and      /work/SRC/openSUSE:Factory/.planner.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "planner"

Changes:
--------
--- /work/SRC/openSUSE:Factory/planner/planner.changes  2013-03-15 
10:47:01.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.planner.new/planner.changes     2013-12-17 
10:02:43.000000000 +0100
@@ -1,0 +2,9 @@
+Mon Dec 16 18:33:17 UTC 2013 - [email protected]
+
+- Exchange scrollkeeper BuildRequires for
+  rarian-scrollkeeper-compat. Scrollkeeper was dropped from
+  distribution.
+- Stop rm -r %{buildroot}%{_localstatedir}/scrollkeeper, after the
+  switch to rarian-scrollkeper-compat it does not exist any more. 
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ planner.spec ++++++
--- /var/tmp/diff_new_pack.cVabCP/_old  2013-12-17 10:02:44.000000000 +0100
+++ /var/tmp/diff_new_pack.cVabCP/_new  2013-12-17 10:02:44.000000000 +0100
@@ -48,7 +48,7 @@
 BuildRequires:  libxslt-devel >= 1.1.23
 BuildRequires:  python-devel
 BuildRequires:  python-gtk-devel
-BuildRequires:  scrollkeeper
+BuildRequires:  rarian-scrollkeeper-compat
 # We need the %%mime_database_* macros
 BuildRequires:  shared-mime-info
 BuildRequires:  translation-update-upstream
@@ -124,8 +124,6 @@
 
 %install
 %makeinstall sqldocdir=%{_docdir}/%{name} sampledir=%{_docdir}/%{name}
-# --disable-scrollkeeper apparently doesn't work anymore
-rm -r %{buildroot}%{_localstatedir}/scrollkeeper
 find %{buildroot}%{_libdir} -name '*.la' -type f -delete -print
 cp AUTHORS COPYING ChangeLog NEWS README COPYING 
$RPM_BUILD_ROOT%{_docdir}/%{name}
 %find_lang %{name} %{?no_lang_C}

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

Reply via email to