lilypond-2.24.1-bp156.2.61

- Update to Factory version lilypond-2.24.1 to fix boo#1210502 -
  CVE-2020-17354: lilypond: Lilypond allows attackers to bypass
  the -dsafe protection mechanism.
- Added lilypond-missing-lgc.patch and removed obsolete
  Issue-5243-1-editor-scm-Add-shell-quote-argument-function.diff

- Remove linked lilypond-doc package and use one spec file

- Exclude all 32 bit builds.

- Update to 2.23.3
- Update dependencies:
  * Add texlive-bibtex-bin build requirement.
  * Use sil-gentium-fonts instead of gentium.
- Remove deprecated scripts in spec file.
- Refreshed patches:
  * reproducible.patch
  * add_dircategories_to_documentation.patch
  * use_cstring_and_ctype_includes.patch
- Update _constraints to let lilypond-doc build.

- Fix factory build by requiring t1utils for the build.

- Update to version 2.22.0 and remove incorporated patches:
  0101-read_relocation_dir-in-lilypond_datadir-too.patch and
  0001-scm-disable-embedded-ps-and-embedded-svg-in-dsafe-mo.patch
- Upstream changes:
  * Displaying pitch improvements
  * Rhythm improvements
  * Expressive mark improvements
  * Editorial annotation improvements
  * Vocal music improvements
  * Unfretted and fretted string instrument improvements
  * Chord notation improvements
  * Contemporary music improvements
  * Input file improvements
  * Output improvements

- Add patch from git to fix boo#1174949 - CVE-2020-17353:
  0001-scm-disable-embedded-ps-and-embedded-svg-in-dsafe-mo.patch

- Update to version 2.20.0.
- Removed incorporated and obsolete patches:
  Avoid-segfault-in-grob.cc-with-gcc-6.patch,
  Issue-5243-2-Let-get-editor-use-shell-quote-argument.diff,
  Issue-5243-3-More-conservative-parsing-of-textedit-URIs.diff,
  add_set-global-fonts_function.patch, hurd_file_name_support.patch,
  lilypond-doc-texinfo4.patch and  use_system_correctly.patch.
- lilypond-century-schoolbook-l-fonts replaced by
  lilypond-texgy-fonts.
- Lots of upstream new features and fixes, see:
  /usr/share/doc/packages/lilypond/NEWS.txt

- Use %license

- Work around boo#1163190 by requiring pkgconfig(cairo) for 15.2

- Fix build against glib2 >= 2.60.2 by manually adding:
  - lglib-2.0 -lgobject-2.0 to the linker flags.

- Removed requirement for autotrace which was needed by mftrace
  and replaced with potrace. See boo#1040278

- Fix boo#1093056 CVE-2018-10992 with Debian patch
  use_system_correctly.patch.
- Added 0101-read_relocation_dir-in-lilypond_datadir-too.patch
  hurd_file_name_support.patch
  Issue-5243-3-More-conservative-parsing-of-textedit-URIs.diff
  add_dircategories_to_documentation.patch
  Issue-5243-1-editor-scm-Add-shell-quote-argument-function.diff
  add_set-global-fonts_function.patch
  Issue-5243-2-Let-get-editor-use-shell-quote-argument.diff and
  use_cstring_and_ctype_includes.patch from Debian.

- Add Avoid-segfault-in-grob.cc-with-gcc-6.patch to fix crash on
  newer systems with gcc 6 or newer. This also fixes the doc build.
  The patch is from:
  https://sourceforge.net/p/testlilyissues/issues/4814/
  (upstream bug tracker).

- Add reproducible.patch to sort input files (boo#1041090),
  to override current timestamp and to not have random uniqueIds
  to make build more reproducible

- Use correct vim directory
- Cleanup of the spec file
  * Install info files correctly (fixes RPMLint warnings)

- Add netpbm BuildRequires in all paths, to fix build break

- Add netpbm BuildRequires: needed for pngtopnm.

- updated to 2.18.2: This version provides a number of updates to
  2.18.0, including updated manuals.  We recommend all users to
  upgrade to this version.

- updated to 2.18.0:
  * final release, see changelogs for beta versions
- dropped use-recommended-freetype-include.patch (upstreamed)

- updated to 2.17.97:
  * beta phase to 2.18
  * bugfixes

- Added 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 version

- updated to 2.17.96:
  * beta phase to 2.18
  * bugfixes

- updated to 2.17.26:
  * Decimal numbers can now be written directly in music, without a
    hash sign.  Together with the previous change in the way object
    properties are specified, the code to change the length of stems
    has changed from this:
    \override Stem #'length = #5.6
    e' f' g' a'
    to this:
    \override Stem.length = 5.6
    e' f' g' a'
    One has to write a digit on both sides of the dot - values like
    `4.' or `-.3' are not allowed.
    Decimal fractions are also not accepted in `\chordmode'.
  * A number of shorthands like `(', `)', `|', `[', `]', `~', `\(',
    `\)' and others can now freely be redefined like normal commands.
    An example would be
    "\\{" = (
    "\\}" = )
    "(" = \melisma
    ")" = \melismaEnd
    \new Staff <<
    \relative c' {
    c8 \{ d e f \} % slurred
    g ( a b c ) % no slur, but with melisma
    c,1 \bar "|."
    }
    \addlyrics { Li -- ly -- pond. }
    >>
    [image of music]
  * The articulation shorthand for `\staccatissimo' has been renamed
    from `-|' to `-!'.
  * Tempo change ranges are now written as `\tempo 4 = 60 - 68' rather
    than `\tempo 4 = 60 ~ 68'.
- make-doc-crash.patch upstreamed

- updated to 2.17.24:
  * bugfixes
- make doc do not crash anymore
  + lilypond-make-doc-crash.patch

- updated to 2.17.23:
  * bugfixes
- removed python26.patch and gcc44-relocate.patch

- 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.

- 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

- 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.

- update to version 2.16.1
- This is a bugfix update see :
  http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1

- Re-add lilypond-doc.spec again to build the offline documentation
  again. It has been adjusted for 2.16.0 from the latest revision
  where it was still part of and a bit cleaned up. Info pages are
  excluded because they are part of the main package now.

- Update to release 2.16.0
- See :
  http://lilypond.org/doc/v2.16/Documentation/changes/index.html
  For upstream changes.