Hello community, here is the log from the commit of package lilypond for openSUSE:Factory checked in at 2013-08-23 11:07:42 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 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 2012-12-22 22:17:35.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.lilypond.new/lilypond-doc.changes 2013-08-23 11:07:44.000000000 +0200 @@ -1,0 +2,84 @@ +Tue Aug 6 13:56:19 UTC 2013 - [email protected] + +- updated to 2.17.23: + * bugfixes +- removed python26.patch and gcc44-relocate.patch + +------------------------------------------------------------------- +Wed Mar 27 12:36:28 UTC 2013 - [email protected] + +- updated to 2.17.14: + * The meaning of `instrumentTransposition' has been reversed. After + \set instrumentTransposition = #{ b #} + a written `c'' now sounds like `b'. Previously, this would have + been the other way round. This and the following change should + make dealing with transposing instruments more straightforward. + + * The music generated by `\set' and `\override' commands is no + longer affected by `\transpose'. The main consequence is that + `\transpose' will transpose audible/concert pitch and printed + pitch by the same amount even when the transposed music contains + `\transposition'. Previously, + \transpose c' f' \transposition bes' + was equivalent to `\transposition f''. Now it stays equivalent to + `\transposition bes''. + + * Tuplets are now created with the `\tuplet' command, which takes a + fraction `T/N' to specify that T notes are played in the time + usually allowed for N. One `\tuplet' command can create several + tuplet groups if their duration is typed after the fraction. + + \tuplet 3/2 { c8 d e } \tuplet 3/2 { f e d } c2 + \tuplet 3/2 4 { c8 d e f e d } c2 + [image of music] + + + The `\times' command with its inverted fraction order `N/T' is + still available. + etc. see NEWS.txt + +------------------------------------------------------------------- +Mon Dec 31 14:29:37 UTC 2012 - [email protected] + +- updated to version 2.17.9: + * The `\clef' command supports optional octavation: + + \clef "treble_(8)" + c2 c + \clef "bass^[15]" + c2 c + * The LilyPond syntax of dot-separated words `Voice.Accidental' has + been made interchangeable with `#'(Voice Accidental)', a Scheme + list of symbols. As one result, code like + \override Voice.TextSpanner #'(bound-details left text) = "rit." + is now equivalent to + \override Voice.TextSpanner bound-details.left.text = "rit." + or even + \override #'(Voice TextSpanner) bound-details.left.text = "rit." + * Grob and grob property path no longer need to be specified as two + separate arguments to commands like `\override' and `\revert', + allowing for the syntax + \override Voice.TextSpanner.bound-details.left.text = "rit." + Since complementary music functions like `\overrideProperty' + cannot support forms with and without separating space at the same + time, using a single dotted path is now the preferred form. + Specifying grob path and grob property path separately, currently + still supported with `\override' and `\revert' for compatibility + reasons, is deprecated. + * Due to words now being accepted as symbol function arguments, the + interfaces of `\accidentalStyle', `\alterBroken', `\footnote' and + `\tweak' had to be redesigned where optional symbol arguments were + involved. Please check the respective music function + documentation for details. + * Several commands now accept symbol lists (conveniently entered as + dot-separated words) for various kinds of arguments. These + include `\accidentalStyle', `\alterBroken', `\footnote', `\hide', + `\omit', `\overrideProperty', `\shape', and `\tweak'. + * The bar line user interface has changed. Bar glyphs now resemble + the appearance of the bar line, so a left repeat sign has to be + coded as `.|:'. The command `\defineBarLine' provides an easy way + to define additional bar line styles. + * Accidentals in the key signature may be printed in octaves other + than their traditional positions, or in multiple octaves. + +------------------------------------------------------------------- --- /work/SRC/openSUSE:Factory/lilypond/lilypond.changes 2012-12-05 13:59:08.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.lilypond.new/lilypond.changes 2013-08-23 11:07:44.000000000 +0200 @@ -1,0 +2,154 @@ +Tue Aug 13 07:52:45 UTC 2013 - [email protected] + +- updated to 2.17.24: + * bugfixes +- make doc do not crash anymore + + lilypond-make-doc-crash.patch + +------------------------------------------------------------------- +Tue Aug 6 13:35:41 UTC 2013 - [email protected] + +- updated to 2.17.23: + * bugfixes +- removed python26.patch and gcc44-relocate.patch + +------------------------------------------------------------------- +Wed Jun 12 09:22:56 UTC 2013 - [email protected] + +- updated to 2.17.20: + * Grob `OctavateEight' was renamed to `ClefModifier'. Related + context properties were renamed from `xxxOctavationyyy' to + `xxxTranspositionyyy'. + * There is a new `\absolute' command explicitly marking music as + being entered in absolute pitch. While this has been the default + previously, an explicit `\absolute' also prevents reinterpretation + when the passage is placed inside of `\relative': + + \relative c { c'4 \absolute { f'' g'' } c } + [image of music] + * When `\relative' is used without an explicit reference pitch, the + reference pitch now is the middle of the first octave, making the + first entered pitch indistinguishable from absolute pitch. + Previously, omitting the reference pitch would have lead to a + default of `c''. Since that choice was somewhat arbitrary, + recommended usage was to always specify the reference pitch. + * A new command `\single' can be used for converting a property + override into a tweak to be applied on a single music expression: + + <a \single\voiceTwoStyle e' a>1 + [image of music] + * Two ways of letting graphical objects not appear in the output are + overriding its `transparent' property with `#t' (retaining the + original spacing) or overriding its `stencil' property with `#f' + (not using any space at all). Those two operations now have the + shorthands `\hide' and `\omit', respectively. They can either be + given a music expression to tweak, or the name of a graphical + object for which an override should be created (for specifying + both, use `\single' on the override form): + + \new Staff \with { \omit Clef } + \relative c'' <a e' \hide a>1 + [image of music] + * A new command `\temporary' can be applied to overrides in order to + not have them replace previous property settings. If a `\revert' + is applied to the same property subsequently, the previous setting + reappears: + \override NoteHead.color = #red c4 + \override NoteHead.color = #green d + \revert NoteHead.color e2 + \override NoteHead.color = #red c4 + \temporary\override NoteHead.color = #green d + \revert NoteHead.color e + \revert NoteHead.color c + [image of music] + This is mainly useful for writing music functions that need to + have some property changed just for the duration of the function. + * `\tag', `\removeWithTag', and `\keepWithTag' can now accept a list + of symbols rather than just a single symbol for marking, removing, + and keeping music with any of multiple tags. This is particularly + important for `\keepWithTag' since one cannot achieve the same + effect by using multiple consecutive `\keepWithTag' commands. + * The `-d old-relative' option has been removed. Not actually + accessible from the command line any more, its remaining use was + for interpretating `\relative' in LilyPond files converted + automatically from version 1.8 or older. It is unclear how much + of this was actually still operative. + +------------------------------------------------------------------- +Wed Mar 27 10:51:23 UTC 2013 - [email protected] + +- updated to 2.17.14: + * The meaning of `instrumentTransposition' has been reversed. After + \set instrumentTransposition = #{ b #} + a written `c'' now sounds like `b'. Previously, this would have + been the other way round. This and the following change should + make dealing with transposing instruments more straightforward. + + * The music generated by `\set' and `\override' commands is no + longer affected by `\transpose'. The main consequence is that + `\transpose' will transpose audible/concert pitch and printed + pitch by the same amount even when the transposed music contains + `\transposition'. Previously, + \transpose c' f' \transposition bes' + was equivalent to `\transposition f''. Now it stays equivalent to + `\transposition bes''. + + * Tuplets are now created with the `\tuplet' command, which takes a + fraction `T/N' to specify that T notes are played in the time + usually allowed for N. One `\tuplet' command can create several + tuplet groups if their duration is typed after the fraction. + + \tuplet 3/2 { c8 d e } \tuplet 3/2 { f e d } c2 + \tuplet 3/2 4 { c8 d e f e d } c2 + [image of music] + + + The `\times' command with its inverted fraction order `N/T' is + still available. + etc. see NEWS.txt + +------------------------------------------------------------------- +Mon Dec 31 14:25:31 UTC 2012 - [email protected] + +- updated to 2.17.9: + * The `\clef' command supports optional octavation: + + \clef "treble_(8)" + c2 c + \clef "bass^[15]" + c2 c + * The LilyPond syntax of dot-separated words `Voice.Accidental' has + been made interchangeable with `#'(Voice Accidental)', a Scheme + list of symbols. As one result, code like + \override Voice.TextSpanner #'(bound-details left text) = "rit." + is now equivalent to + \override Voice.TextSpanner bound-details.left.text = "rit." + or even + \override #'(Voice TextSpanner) bound-details.left.text = "rit." + * Grob and grob property path no longer need to be specified as two + separate arguments to commands like `\override' and `\revert', + allowing for the syntax + \override Voice.TextSpanner.bound-details.left.text = "rit." + Since complementary music functions like `\overrideProperty' + cannot support forms with and without separating space at the same + time, using a single dotted path is now the preferred form. + Specifying grob path and grob property path separately, currently + still supported with `\override' and `\revert' for compatibility + reasons, is deprecated. + * Due to words now being accepted as symbol function arguments, the + interfaces of `\accidentalStyle', `\alterBroken', `\footnote' and + `\tweak' had to be redesigned where optional symbol arguments were + involved. Please check the respective music function + documentation for details. + * Several commands now accept symbol lists (conveniently entered as + dot-separated words) for various kinds of arguments. These + include `\accidentalStyle', `\alterBroken', `\footnote', `\hide', + `\omit', `\overrideProperty', `\shape', and `\tweak'. + * The bar line user interface has changed. Bar glyphs now resemble + the appearance of the bar line, so a left repeat sign has to be + coded as `.|:'. The command `\defineBarLine' provides an easy way + to define additional bar line styles. + * Accidentals in the key signature may be printed in octaves other + than their traditional positions, or in multiple octaves. + +------------------------------------------------------------------- Old: ---- lilypond-2.16.1.tar.gz lilypond-gcc44-relocate.patch lilypond-python26.patch New: ---- lilypond-2.17.24.tar.gz lilypond-make-doc-crash.patch ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ lilypond-doc.spec ++++++ --- /var/tmp/diff_new_pack.Z5IX6o/_old 2013-08-23 11:07:45.000000000 +0200 +++ /var/tmp/diff_new_pack.Z5IX6o/_new 2013-08-23 11:07:45.000000000 +0200 @@ -1,7 +1,7 @@ # # spec file for package lilypond-doc # -# Copyright (c) 2012 SUSE LINUX Products GmbH, Nuernberg, Germany. +# Copyright (c) 2013 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,9 @@ #%%define info yes Name: lilypond-doc -Version: 2.16.1 +%define ver 2.17 +%define plevel 24 +Version: %{ver}.%{plevel} Release: 0 BuildRequires: autoconf BuildRequires: autotrace @@ -43,11 +45,13 @@ BuildRequires: libgnutls-devel BuildRequires: libguile1-devel >= 1.8.2 BuildRequires: libtool +BuildRequires: lndir BuildRequires: mftrace BuildRequires: pango-devel >= 1.12 BuildRequires: perl BuildRequires: python-devel >= 2.4 BuildRequires: t1utils +BuildRequires: texlive-lh BuildRequires: texlive-metapost BuildRequires: zip @@ -70,9 +74,7 @@ Group: Documentation/HTML BuildArch: noarch Url: http://lilypond.org/ -Source0: http://download.linuxaudio.org/lilypond/sources/v2.16/lilypond-%{version}.tar.gz -Patch0: lilypond-python26.patch -Patch1: lilypond-gcc44-relocate.patch +Source0: http://download.linuxaudio.org/lilypond/sources/v%{ver}/lilypond-%{version}.tar.gz BuildRoot: %{_tmppath}/%{name}-%{version}-build PreReq: %install_info_prereq /usr/bin/touch /usr/bin/sed @@ -100,7 +102,6 @@ LilyPond is part of the GNU Project. %global rlversion %{version} -#%%(bash %%{S:6} %%{S:0}) %define usrsrcp %{buildroot} %define _configure ./smart-configure.sh @@ -111,8 +112,6 @@ %prep %setup -q -n lilypond-%{version} -%patch0 -%patch1 # Convert translations to UTF-8 for file in $(grep -L charset=UTF-8 po/*.po) ; do msgconv -t UTF-8 $file >$file.new @@ -125,11 +124,8 @@ %build -#smart-autogen.sh -#--noconfigure # export GS_LIB="/home/$USER/.fonts" is a work around for bnc#568280 -%if 1 == 1 -export GS_LIB="/home/$USER/.fonts:%{_buildir}/mf/out" +#export GS_LIB="/home/$USER/.fonts:%{_buildir}/mf/out" export CFLAGS="-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -ggdb" %if 0%{?suse_version} == 1210 export CFLAGS="$CFLAGS -fno-optimize-sibling-calls" @@ -137,13 +133,10 @@ export GUILE_AUTO_COMPILE=0 export CFLAGS="$RPM_OPT_FLAGS -ggdb -fpermissive -fabi-version=4" export CXXFLAGS="$CFLAGS" -%endif export LILYPOND_EXTERNAL_BINARY="%{_bindir}/lilypond" export LILYPOND_BINARY=$LILYPOND_EXTERNAL_BINARY %configure --with-ncsb-dir=%{_datadir}/ghostscript/fonts/ ./smart-autogen.sh --noconfigure - -gs -h # build documentation echo "*********************************" echo "* Start the documentation build *" @@ -155,15 +148,12 @@ make -C scripts && make -C python pushd Documentation LILYPOND_EXTERNAL_BINARY="%{_bindir}/lilypond" LILYPOND_BINARY=$LILYPOND_EXTERNAL_BINARY make -e %{?jobs:-j%jobs CPU_COUNT=%jobs} doc \ -|| (lndir -ignorelinks out-www/notation . \ +|| (lndir -ignorelinks out-www/notation . && \ LILYPOND_EXTERNAL_BINARY="%{_bindir}/lilypond" LILYPOND_BINARY=$LILYPOND_EXTERNAL_BINARY make %{?jobs:-j%jobs CPU_COUNT=%jobs} doc) -#make po-replace popd make out=www WWW-post %install -echo %rlversion -echo %{rlversion} mkdir -p "%{buildroot}%{_datadir}/lilypond/%{rlversion}" # install documentation @@ -171,10 +161,8 @@ cp -a COPYING LICENSE LICENSE.DOCUMENTATION \ DEDICATION HACKING ROADMAP AUTHORS.txt NEWS.txt \ - THANKS VERSION elisp/server.el.patch \ + VERSION \ %{buildroot}%{_docdir}/lilypond -#ChangeLog -#install -m0644 "%%{SOURCE3}" "%%{buildroot}%%{_docdir}/%%{name}" find %{buildroot}%{_docdir}/lilypond -name *.signature -exec rm {} \; @@ -218,7 +206,6 @@ %exclude %{_docdir}/lilypond/DEDICATION %exclude %{_docdir}/lilypond/HACKING %exclude %{_docdir}/lilypond/ROADMAP -%exclude %{_docdir}/lilypond/THANKS %exclude %{_docdir}/lilypond/VERSION %exclude %{_docdir}/lilypond/AUTHORS.txt %exclude %{_docdir}/lilypond/NEWS.txt ++++++ lilypond.spec ++++++ --- /var/tmp/diff_new_pack.Z5IX6o/_old 2013-08-23 11:07:45.000000000 +0200 +++ /var/tmp/diff_new_pack.Z5IX6o/_new 2013-08-23 11:07:45.000000000 +0200 @@ -1,7 +1,7 @@ # # spec file for package lilypond # -# Copyright (c) 2012 SUSE LINUX Products GmbH, Nuernberg, Germany. +# Copyright (c) 2013 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,18 +20,18 @@ %define ttfdir %{fontdir}/truetype Name: lilypond -Version: 2.16.1 +%define ver 2.17 +%define plevel 24 +Version: %{ver}.%{plevel} Release: 0 Summary: A typesetting system for music notation License: GPL-3.0+ Group: Productivity/Publishing/Other Url: http://www.lilypond.org -Source0: http://download.linuxaudio.org/lilypond/sources/v2.15/%{name}-%{version}.tar.gz -# PATCH-MISSING-TAG -- See http://wiki.opensuse.org/openSUSE:Packaging_Patches_guidelines -Patch0: lilypond-python26.patch -# PATCH-MISSING-TAG -- See http://wiki.opensuse.org/openSUSE:Packaging_Patches_guidelines -Patch1: lilypond-gcc44-relocate.patch +Source0: http://download.linuxaudio.org/lilypond/sources/v%{ver}/lilypond-%{version}.tar.gz +# upstream patch, will be in 2.17.25 +Patch0: lilypond-make-doc-crash.patch BuildRoot: %{_tmppath}/%{name}-%{version}-build Requires: ghostscript >= 8.15 @@ -59,6 +59,7 @@ BuildRequires: makeinfo BuildRequires: texlive-extratools BuildRequires: texlive-latex +BuildRequires: texlive-lh BuildRequires: texlive-metafont BuildRequires: texlive-metapost %else @@ -117,9 +118,7 @@ %prep %setup -q - -%patch0 -p0 -%patch1 -p0 +%patch0 -p1 %build %configure --without-kpathsea --disable-checking \ @@ -154,13 +153,10 @@ rmdir %{buildroot}%{_datadir}/lilypond/%{version}/fonts/otf ln -s %{ttfdir} %{buildroot}%{_datadir}/lilypond/%{version}/fonts/otf -%clean -rm -rf %{buildroot} - %files -f %{name}.lang %defattr(-,root,root,-) -%doc AUTHORS.txt COPYING DEDICATION HACKING INSTALL.txt -%doc NEWS.txt README.txt ROADMAP THANKS VERSION +%doc AUTHORS.txt COPYING DEDICATION HACKING LICENSE* +%doc NEWS.txt README.txt ROADMAP VERSION %{_bindir}/* %{_libdir}/lilypond %{_datadir}/lilypond ++++++ lilypond-2.16.1.tar.gz -> lilypond-2.17.24.tar.gz ++++++ /work/SRC/openSUSE:Factory/lilypond/lilypond-2.16.1.tar.gz /work/SRC/openSUSE:Factory/.lilypond.new/lilypond-2.17.24.tar.gz differ: char 5, line 1 ++++++ lilypond-make-doc-crash.patch ++++++ >From d87f3084a9e83a72d509dbc5196800062eee3f28 Mon Sep 17 00:00:00 2001 From: David Kastrup <[email protected]> Date: Sun, 11 Aug 2013 16:19:05 +0200 Subject: [PATCH 1/1] Avoid Scheme-computed Skyline_pair values to get collected before use Retaining them as SCM values until they are no longer needed avoids premature garbage collection. This addresses circumstances in connection with issue 3490. --- lily/side-position-interface.cc | 34 ++++++++++++++++------------------ 1 files changed, 16 insertions(+), 18 deletions(-) diff --git a/lily/side-position-interface.cc b/lily/side-position-interface.cc index dad906f..8e23c2a 100644 --- a/lily/side-position-interface.cc +++ b/lily/side-position-interface.cc @@ -214,14 +214,13 @@ Side_position_interface::aligned_side (Grob *me, Axis a, bool pure, int start, i common[Y_AXIS] = staff_symbol->common_refpoint (common[Y_AXIS], Y_AXIS); Skyline my_dim; - Skyline_pair *skyp = Skyline_pair::unsmob ( - me->get_maybe_pure_property (a == X_AXIS - ? "horizontal-skylines" - : "vertical-skylines", - pure, - start, - end)); - if (skyp) + SCM skyp = me->get_maybe_pure_property (a == X_AXIS + ? "horizontal-skylines" + : "vertical-skylines", + pure, + start, + end); + if (Skyline_pair::unsmob (skyp)) { // for spanner pure heights, we don't know horizontal spacing, // so a spanner can never have a meaningful x coordiante @@ -237,7 +236,7 @@ Side_position_interface::aligned_side (Grob *me, Axis a, bool pure, int start, i Real yc = a == X_AXIS ? me->pure_relative_y_coordinate (common[Y_AXIS], start, end) : me->get_parent (Y_AXIS)->maybe_pure_coordinate (common[Y_AXIS], Y_AXIS, pure, start, end); - Skyline_pair copy = Skyline_pair (*skyp); + Skyline_pair copy = *Skyline_pair::unsmob (skyp); copy.shift (a == X_AXIS ? yc : xc); copy.raise (a == X_AXIS ? xc : yc); my_dim = copy[-dir]; @@ -280,16 +279,15 @@ Side_position_interface::aligned_side (Grob *me, Axis a, bool pure, int start, i { - Skyline_pair *sp = Skyline_pair::unsmob - (e->get_maybe_pure_property (a == X_AXIS - ? "horizontal-skylines" - : "vertical-skylines", - pure || cross_staff, - start, - end)); + SCM sp = e->get_maybe_pure_property (a == X_AXIS + ? "horizontal-skylines" + : "vertical-skylines", + pure || cross_staff, + start, + end); aligns_to_cross_staff |= cross_staff; - if (sp) + if (Skyline_pair::unsmob (sp)) { Real xc = pure && dynamic_cast<Spanner *> (e) ? e->get_parent (X_AXIS)->relative_coordinate (common[X_AXIS], X_AXIS) @@ -299,7 +297,7 @@ Side_position_interface::aligned_side (Grob *me, Axis a, bool pure, int start, i Real yc = a == X_AXIS ? e->pure_relative_y_coordinate (common[Y_AXIS], start, end) : e->maybe_pure_coordinate (common[Y_AXIS], Y_AXIS, pure, start, end); - Skyline_pair copy = Skyline_pair (*sp); + Skyline_pair copy = *Skyline_pair::unsmob (sp); if (a == Y_AXIS && Stem::has_interface (e) && to_boolean (me->get_maybe_pure_property ("add-stem-support", pure, start, end))) -- 1.7.2.5 -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
