> No, no - I'm sure it's an effect of Guido's time machine - some
> LilyPond Python script used "from __future__ import __version__"!
> ;-D
>
I had a feeling something like that might have been at work but I've
always been so bad at temporal mechanics that I was loath to even
suggest it. ;)
Am 2005-08-22 um 09:17 schrieb Mats Bengtsson:
Looks like a silly packaging error. Just edit the converted .ly file
and replace "2.7.7" with "2.7.6" in the \version statement.
No, no - I'm sure it's an effect of Guido's time machine - some
LilyPond Python script used "from __future__ import
I noticed the same thing. Just change the \version statement and you are good
to go.
Henrik Frisk
>
> Looks like a silly packaging error. Just edit the converted .ly file
> and replace "2.7.7" with "2.7.6" in the \version statement.
>
> /Mats
>
> David Fedoruk wrote:
> > Hello all:
> >
>
Looks like a silly packaging error. Just edit the converted .ly file
and replace "2.7.7" with "2.7.6" in the \version statement.
/Mats
David Fedoruk wrote:
Hello all:
I downloaded the latest development version of lilypond for Mac OS X
(2.7.6-1 (vBuild from 19-08-2005 22:05). When I run Upd
Hello all:
I downloaded the latest development version of lilypond for Mac OS X
(2.7.6-1 (vBuild from 19-08-2005 22:05). When I run Update Syntax from
the GUI in O S X, it converts to the wrong version.
To test this I took the Welcome document which opens the application
and contains a short test
