[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LSR updates

From: Phil Holmes
Subject: Re: LSR updates
Date: Sun, 13 Apr 2014 17:22:25 +0100

----- Original Message ----- From: "Phil Holmes" <address@hidden>
To: "Graham Percival" <address@hidden>
Cc: "David Kastrup" <address@hidden>; "Pierre Perol-Schneider" <address@hidden>; "Devel" <address@hidden>
Sent: Sunday, April 13, 2014 12:44 PM
Subject: Re: LSR updates

----- Original Message ----- From: "Graham Percival" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: "David Kastrup" <address@hidden>; "Devel" <address@hidden>; "Pierre Perol-Schneider" <address@hidden>
Sent: Sunday, April 13, 2014 11:40 AM
Subject: Re: LSR updates

On Sun, Apr 13, 2014 at 11:18:43AM +0100, Phil Holmes wrote:
-\version "2.17.30"
+\version "2.14.2"

So it appears to be ignoring updated syntax and setting the version
back to 2.14.  Or simply not updating the syntax at all.  Anyone any
thoughts why this might be?

It's running convert-ly from your Ubuntu lilypond installation,
/usr/bin/convert-ly.  As to why it's not finding the correct
convert-ly, I don't know. is supposed to warn you if
you haven't built lilypond (or maybe even it's supposed to run
make for you).

- Graham

Great theory, but unfortunately not correct.

On the terminal, I get this: reading /home/phil/LSRArchive/lsr-snippets-docs-2014-04-13/really-simple/ writing Documentation/snippets/
convert-ly (GNU LilyPond) 2.19.5

convert-ly: Processing `Documentation/snippets/'...
Applying conversion: 2.15.7, 2.15.9, 2.15.10, 2.15.16, 2.15.17, 2.15.18, 2.15.19, 2.15.20, 2.15.25, 2.15.32, 2.15.39, 2.15.40, 2.15.42, 2.15.43, 2.16.0, 2.17.0, 2.17.4, 2.17.5, 2.17.6, 2.17.11, 2.17.14, 2.17.15, 2.17.18, 2.17.19, 2.17.20, 2.17.25, 2.17.27, 2.17.29, 2.17.97, 2.18.0, 2.19.2

GNU LilyPond 2.19.5
Changing working directory to: `/tmp/lsrtest'
Processing `Documentation/snippets/'
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Success: compilation successfully completed

It looks like convert-ly is simply not writing the updated snippet to Documentation/snippets

Phil Holmes

I believe I have found the problem. The LSR is currently producing its tarballs with LilyPond files headed '\version "2.14.2"', but with syntax from later versions. As an example, uses:

\override StaffGroup.SystemStartBracket.collapse-height = #4

which is 2.18 syntax. convert-ly recognises that no updates are needed, and so doesn't update the \version string. I think the solution is that the LSR needs to output the version number of the currently installed LilyPond, before it will be possible to import the tarball. Pierre: could you discuss this with Seba, please?

Phil Holmes

reply via email to

[Prev in Thread] Current Thread [Next in Thread]