On Sat, Jun 09, 2012 at 07:55:30PM -0300, Han-Wen Nienhuys wrote:
> On Sat, Jun 9, 2012 at 4:58 PM, Graham Percival
> wrote:
>
> > I've been fairly clear: every release says either
> > "It is strongly recommended that normal users do not use this
> > release, and instead use the stable 2.14 ver
On Sat, Jun 9, 2012 at 4:58 PM, Graham Percival
wrote:
> I've been fairly clear: every release says either
> "It is strongly recommended that normal users do not use this
> release, and instead use the stable 2.14 version."
> or
> "All users are invited to experiment with this version."
>
> Ma
On Sat, Jun 09, 2012 at 09:19:31PM +0200, Frédéric Bron wrote:
> After update, it comes with g++ 4.7.0-5 and lilypon 2.15.39.
> Please find attached the output which looks good to me.
> Any idea why it does not come with a stable release (i.e. 2.14)?
Because the fedora mainter(s) for lilypond thin
On Sat, 9 Jun 2012 21:19:31 +0200
Frédéric Bron wrote:
> I just installed fedora 17 x86_64.
> After update, it comes with g++ 4.7.0-5 and lilypon 2.15.39.
> Please find attached the output which looks good to me.
Yes, it looks good.
> Any idea why it does not come with a stable release (i.e. 2.
>>> I mentioned in passing that Fedora 17 (currently in beta) ships
>>> Lilypond 2.15.29 that reports bogus bar checks.
>>>
>>> It turns out that both the current Lilypond from git and Lilypond
>>> 2.14.2 are miscompiled on the up-to-date Fedora 17 so they exhibit the
>>> same problem.
>>
>> What c
