| Summary: | media-sound/lilypond-2.19.80 should not have gone stable | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Lars Henrik Ørn <larshenrikoern> |
| Component: | Current packages | Assignee: | Scheme Project <scheme> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | CC: | hangglider, karl.j.linden, leio, mgorny, proxy-maint |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=701380 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Lars Henrik Ørn
2018-12-17 07:54:57 UTC
It had to go stable because older lilypond doesn't work with guile-2, and as such was blocking guile-2 stabling for everyone otherwise, which in turn blocked other stable software (requiring guile-2) newer versions from going to gentoo stable. See bug 647476 We can drop lilypond to ~arch entirely, I guess. Hi again Dropping all versios to testing is not necessary. The 2.18 version is working just fine. I have masked the 2.19.* version, because I as professional are depending on the program, and need a stable predictable behavior. In a few weeks the next 2.20 version will be released, and everything should be fine by then. Have a nice day As already said in the scribus bug: Some upstream release cycles align very badly with rolling release needs as in Gentoo. lilypond upstream's current stable release is from March 23, 2014, that says it all. I don't think there is anything to add to comment #1. If there are actual issues with 2.19.80, we can hope that each subsequent release is fixing more than it breaks, I checked and opened bug 673660 for 2.19.82. Please test with 2.19.83 then. |
