https://bugzilla.novell.com/show_bug.cgi?id=851999 https://bugzilla.novell.com/show_bug.cgi?id=851999#c2 --- Comment #2 from Petr Gajdos <pgajdos@suse.com> 2013-11-26 09:02:20 UTC --- (In reply to comment #0)
The LilyPond version shipping in openSUSE 13.1 is 2.17.26, part of the 2.17.x series of development releases. (As Linux used to do, odd-numbered major releases are for development of the next even-numbered stable release; thus 2.13.x, 2.15.x, 2.17.x, and so on are unstable).
I would find many examples that this isn't true ;-). Ok, next time, I will do an update in factory only to next 'stable' version for lilypond, but..
While it makes sense to be shipping the 2.17.x series in Factory, we should have been downgraded to 2.16.2---the most recent stable release---when 13.1 branched from Factory. As it is, the should-be-stable package shipped with 13.1 is not only a development version, but an early and out-of-date development version.
Thus, I request a downgrade to LilyPond 2.16.2. If that's impractical, please start shipping updated development versions until the 2.18.x series is released, which should be soon (the current 2.17.95 is beta for 2.18.0).
. I do not see a point to have 2.17.x for a long time in factory and then downgrade to 2.16.x. We can think about version upgrade to 2.18.0 for 13.1 as soon as it is out. I will upgrade lilypond in factory soon.
(As an aside, I note from bug 733730 and https://build.opensuse.org/package/users/openSUSE:13.1/lilypond that there may be no dedicated maintainer for the "lilypond" package. If that's the case, I may wish to join in).
I am the maintainer together with Dave; but if you wish, tell me a buildservice id, I will add you as maintainer -- more hands are of course welcome. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.