Hello community,

here is the log from the commit of package lilypond for openSUSE:Factory 
checked in at 2014-01-03 14:49:05
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/lilypond (Old)
 and      /work/SRC/openSUSE:Factory/.lilypond.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "lilypond"

Changes:
--------
--- /work/SRC/openSUSE:Factory/lilypond/lilypond-doc.changes    2013-12-19 
12:48:19.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.lilypond.new/lilypond-doc.changes       
2014-01-03 14:49:07.000000000 +0100
@@ -1,0 +2,7 @@
+Thu Jan  2 12:13:55 UTC 2014 - [email protected]
+
+- updated to 2.18.0:
+  * final release, see changelogs for beta versions
+- dropped use-recommended-freetype-include.patch (upstreamed)
+
+-------------------------------------------------------------------
--- /work/SRC/openSUSE:Factory/lilypond/lilypond.changes        2013-12-19 
12:48:19.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.lilypond.new/lilypond.changes   2014-01-03 
14:49:07.000000000 +0100
@@ -1,0 +2,7 @@
+Thu Jan  2 11:44:55 UTC 2014 - [email protected]
+
+- updated to 2.18.0:
+  * final release, see changelogs for beta versions
+- dropped use-recommended-freetype-include.patch (upstreamed)
+
+-------------------------------------------------------------------

Old:
----
  lilypond-2.17.97.tar.gz
  use-recommended-freetype-include.patch

New:
----
  lilypond-2.18.0.tar.gz

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

Other differences:
------------------
++++++ lilypond-doc.spec ++++++
--- /var/tmp/diff_new_pack.gwvBp8/_old  2014-01-03 14:49:08.000000000 +0100
+++ /var/tmp/diff_new_pack.gwvBp8/_new  2014-01-03 14:49:08.000000000 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package lilypond-doc
 #
-# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2014 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,8 +19,8 @@
 #%%define info yes
 
 Name:           lilypond-doc
-%define ver     2.17
-%define plevel  97
+%define ver     2.18
+%define plevel  0
 Version:        %{ver}.%{plevel}
 Release:        0
 BuildRequires:  autoconf

++++++ lilypond.spec ++++++
--- /var/tmp/diff_new_pack.gwvBp8/_old  2014-01-03 14:49:08.000000000 +0100
+++ /var/tmp/diff_new_pack.gwvBp8/_new  2014-01-03 14:49:08.000000000 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package lilypond
 #
-# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2014 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
@@ -20,8 +20,8 @@
 %define ttfdir  %{fontdir}/truetype
 
 Name:           lilypond
-%define ver     2.17
-%define plevel  97
+%define ver     2.18
+%define plevel  0
 Version:        %{ver}.%{plevel}
 Release:        0
 Summary:        A typesetting system for music notation
@@ -30,9 +30,6 @@
 
 Url:            http://www.lilypond.org
 Source0:        
http://download.linuxaudio.org/lilypond/sources/v%{ver}/lilypond-%{version}.tar.gz
-# PATCH-FIX-UPSTREAM use-recommended-freetype-include.patch -- Freetype 
upstream recommends using their macros together with
-# ft2build include. Positive sideeffect is that this patch makes it build with 
both freetype2 2.5.1, and older versions
-Patch0:         use-recommended-freetype-include.patch
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 
 Requires:       ghostscript >= 8.15
@@ -119,7 +116,6 @@
 
 %prep
 %setup -q
-%patch0 -p1
 
 %build
 %configure --without-kpathsea --disable-checking \

++++++ lilypond-2.17.97.tar.gz -> lilypond-2.18.0.tar.gz ++++++
/work/SRC/openSUSE:Factory/lilypond/lilypond-2.17.97.tar.gz 
/work/SRC/openSUSE:Factory/.lilypond.new/lilypond-2.18.0.tar.gz differ: char 5, 
line 1

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

Reply via email to