In Mageia 2, as far as I can tell, the only available LilyPond release is 2.15.31, which is a development release. This release should never have been available except in cauldron; mga2 should have stayed with the stable 2.14.2 until the next stable release, 2.16.0. 2.15.31 is also quite old. The release announcement, dated 29 February 2012, says "It is strongly recommended that normal users do not use this release, and instead use the stable 2.14 version. Please note that due to a few Critical bugs, this is not the next release candidate." --http://www.lilypond.org/old-news.html Now that 2.16.0 has been released, somebody moved it into cauldron, which I guess is good, but now we have a bizarre situation where Mageia-development has a stable LilyPond and Mageia-stable has a development LilyPond. So I'd like to request an update to LilyPond 2.16.0 for Mageia 2, and 2.17.1 (the next development version) for cauldron. I am willing to help package LilyPond and a few other related applications, like Frescobaldi, if required.
Assignee: bugsquad => thomas
I will update it in mageia 2 to 2.16. I personally have been using the current version for a long time.(BTW what problem did you have?) I will not update it in cauldron anymore before mageia 3 comes out, otherwise we will have a development version in mageia 3 as we have in mageia 2.
Status: NEW => ASSIGNED
Thanks for responding. I've also been using 2.16.0 for a long time, but only because I encountered 2.15.31 in the repository. I was trying to figure out whether to specify an rgb colour as three values between 0 and 255, or between 0 and 1 (as in the 2.16 series... no idea why). I could have just tried it, but because I'm writing a program that uses LilyPond, I didn't want to settle on a poor solution--and moreover, it's very important in that case to know that what I see is what my users would see. Plus, when I saw this, I overreacted a little because a poor update policy for LilyPond is one of the things that provoked me to stop using Fedora for my everyday work.
iot's in updates testing. Would you mind to test it. I'll then get it submitted for moving to updates
Looks good so far. I'll keep going at it for a couple of days, then let you know. Does Mageia have a formalized updates-approval process?
(In reply to comment #4) > Does Mageia have a formalized updates-approval process? yep https://wiki.mageia.org/en/QA_process_for_validating_updates https://wiki.mageia.org/en/Updates_policy
I have used it for a while in cauldron. This replaces the development versions. Please push it to updates after testing. Testing cases are available at http://lilypond.org/development.html
CC: (none) => thomasAssignee: thomas => qa-bugs
Thankyou for the testcases Thomas. Could you give the SRPM and list of RPMs please. Thanks.
Assuming it's just lilypond srpm which has been updated here is a list of rpms. $ ./srpm lilypond Testing Media: Testing SRPM: lilypond-2.16.0-1.mga2.src.rpm ------------------------------------ lilypond-debug lilypond-doc lilypond Also depcheck give the list below which will need linking.. guile-2.0.5-4.mga2 (Core 32bit Release) guile-2.0.5-4.mga2 (Core Release) guile-runtime-2.0.5-4.mga2 (Core 32bit Release) guile-runtime-2.0.5-4.mga2 (Core Release) lib64guile2.0_22-2.0.5-4.mga2 (Core Release) lib64unistring0-0.9.3-5.mga2 (Core Release)
Depends on: (none) => 2317
Errors during install ... install-info: warning: no info dir entry in `/usr/share/info/lilypond-learning.info.xz' install-info: warning: no info dir entry in `/usr/share/info/music-glossary.info.xz Also man lilypond states info LilyPond should give you access to the complete manual, but the info command doesn't find the page. Also, as noted by kis on irc, http://lilypond.org/doc/v2.16/input/regression/e1/lily-69780993.ly from http://lilypond.org/doc/v2.16/input/regression/collated-files.html fails to compile. Neither of these are regressions though.
CC: (none) => davidwhodgins
I tested on MGA2-32. I checked about 15-20 files from http://lilypond.org/doc/v2.16/input/regression/collated-files.html. They were all ok except for mozart-hrn-3.ly, which did not compile. As Dave already said, this is not a regression: the file does not compile with lilypond 2.15 either. I also tested the musicxml2ly script (followed by lilypond) on about 5 files from http://lilypond.org/doc/v2.16/input/regression/musicxml/collated-files.html. They all worked fine. Since it seems that none of the problems were regressions, I'll put in the MGA2-32-OK marker.
CC: (none) => kristina.striegnitzWhiteboard: (none) => MGA2-32-OK
Testing complete on Mageia 2 x86-64. Could someone from the sysadmin team push the srpm lilypond-2.16.0-1.mga2.src.rpm from Mageia 2 Core updates Testing to Core Updates and link thee rpm packages guile-2.0.5-4.mga2 (Core 32bit Release) guile-2.0.5-4.mga2 (Core Release) guile-runtime-2.0.5-4.mga2 (Core 32bit Release) guile-runtime-2.0.5-4.mga2 (Core Release) lib64guile2.0_22-2.0.5-4.mga2 (Core Release) lib64unistring0-0.9.3-5.mga2 (Core Release) from Mageia 2 Core Release to Core Updates. Advisory: This update brings lilypond to version 2.16, replacing the unstable version included in Mageia 2. https://bugs.mageia.org/show_bug.cgi?id=7274
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugsWhiteboard: MGA2-32-OK => MGA2-32-OK MGA2-64-OK
Packages linked and update pushed: https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0203
Status: ASSIGNED => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED