On Mon 18 Nov 2024 at 21:21:31 (-0800), Stu McKenzie wrote: > On 2024-11-18 11:52, Stu McKenzie wrote: > > On 2024-11-18 11:50, Stu McKenzie wrote: > > > On 2024-11-18 11:00, Knute Snortum wrote: > > > > On Mon, Nov 18, 2024 at 10:41 AM Stu McKenzie wrote: > > > > > > > > I'm using LilyPond version 2.25.21. > > > > > > > > This message occurred: > > > > > > > > " > > > > Note: compilation failed and \version outdated, did you > > > > update input syntax with convert-ly? > > > > > > > > > > > > https://lilypond.org/doc/v2.25/Documentation/usage/updating-files-with-convert_002dly > > > > " > > > > > > > > The message appeared during processing of a score, and provides no > > > > indication of where the culprit is. > > > > > > > > I verified that all of my source files have the correct version > > > > number > > > > (\version "2.25.18"). > > > > > > > > > > > > Is it possible that you have to convert from 2.25.18 to 2.25.21? > > > > > > > convert-ly.py released in 2.25.21 leaves the version as "2.25.18". > > > I've managed to prepare a simple example of the error message by > experimenting with scores. > > Unfortunately, there is 1 error before the compilation failed message, > but it shows that no specific file is mentioned in the message.
It's typical that an error occurs before the "outdated" message is issued. But your OP reads as if the message appeared out of the blue, without any previous error having occurred. Is that correct, and if not, what was the error that you didn't report? Cheers, David.
