lilypond-doc-2.20.0-bp153.5.73

- Remove dependency on texinfo4-links package and generate the
  links in the spec file instead.

- 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

- Replace a BuildRequires: fontforge-devel with
  BuildRequires: fontforge, since the build system only requires
  the fontforge binary.

- Add _constraints for PowerPC to avoid build error of lilypond-doc

- Fix Factory build by requiring missing fonts and texlive packages
  directly.

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

- Some minor cleanup

- Created package texinfo4 from 13.2's texinfo package to fix the
  documentation build in Factory and future openSUSE versions
  until upstream have fixed the problem. See bnc#936870
- Added patch lilypond-doc-texinfo4.patch to enable lilypond to use
  the texinfo4 binaries to build the documentation.

- Uncomment texi2html BuildRequires: to fix build break
  Note, the build can go for tens of minutes without producing any output.
  It will eventually make progress.

- Add texi2html BuildRequires: this was split off from texinfo (as
  it's in fact an independent upstream tarball).

- split lilypond-doc [bnc#908078]

- Don't build documentations in parallel. It breaks occasionally.

- 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

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

- remove unnecessary (and conflicting) buildrequires on libicu

- 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

- Remove dependency on ghostscript-fonts-rus (not available on >= 12.2).

- Readd lilypond-doc for 2.16.0