> Hi, Fedora lilypond maintainer. We've actually got our 2.19.45 patched, but
> the update was superceded by 2.19.46. If you do sudo dnf update lilypond*
> --enablerepo=updates-testing you should get it.
Many thanks; this fixed it!
___
bug-lilypond
On Fri, Jul 29, 2016 at 12:32 PM, Kevin Barry wrote:
> Thank you for taking the time to test it. I'm using the package in
> Fedora's repo, so I suppose I should take it up with them? I'm not
> sure how to troubleshoot further. Reinstalling didn't help.
>
> Kevin
>
>
At 18:32 on 29 Jul 2016, Kevin Barry wrote:
>Thank you for taking the time to test it. I'm using the package in
>Fedora's repo, so I suppose I should take it up with them? I'm not
>sure how to troubleshoot further. Reinstalling didn't help.
Thank you for taking the time to test it. I'm using the package in
Fedora's repo, so I suppose I should take it up with them? I'm not
sure how to troubleshoot further. Reinstalling didn't help.
Kevin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Hello,
On 29/07/16 15:41, Kevin Barry wrote:
Apologies if this is fixed in 2.19.46
It worked in previous versions of 2.19 (I'm not sure when it broke
cause it's not from something i worked on too recently). I am on Linux
64-bit (Fedora). A MWE follows (compiling with no options should
Hello,
On 29/07/16 17:59, James wrote:
Hello,
On 29/07/16 15:41, Kevin Barry wrote:
Apologies if this is fixed in 2.19.46
It worked in previous versions of 2.19 (I'm not sure when it broke
cause it's not from something i worked on too recently). I am on Linux
64-bit (Fedora). A MWE follows
Apologies if this is fixed in 2.19.46
It worked in previous versions of 2.19 (I'm not sure when it broke
cause it's not from something i worked on too recently). I am on Linux
64-bit (Fedora). A MWE follows (compiling with no options should
segfault). There must be some kind of problem caused by