[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bug in file `VERSION'
From: |
Graham Percival |
Subject: |
Re: bug in file `VERSION' |
Date: |
Wed, 6 Apr 2011 19:37:14 +0100 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Wed, Apr 06, 2011 at 03:13:00PM +0200, Werner LEMBERG wrote:
>
> -PATCH_LEVEL=57
> +PATCH_LEVEL=58
> MY_PATCH_LEVEL=
> VERSION_STABLE=2.12.3
> -VERSION_DEVEL=2.13.56
> +VERSION_DEVEL=2.13.57
>
>
> IMHO, VERSION_DEVEL should be be 2.13.58 also.
No.
http://lilypond.org/doc/v2.13/Documentation/contributor/minor-release-checklist
(see "post release")
> I had to manually adjust
> usr/local/bin/convert-ly:
>
> for d in ['/usr/local/share/lilypond/2.13.58',
> '/usr/local/lib/lilypond/2.13.58']:
> sys.path.insert (0, os.path.join (d, 'python'))
>
> (it was 2.13.57 after `make install', and this version is not
> installed on my GNU/Linux box).
That sounds... really weird. AFAIK we haven't changed any of the
VERSION_FOO build system in months, and I've been following the
written build policy for over a year. VERSION_DEVEL should not be
used for a string on convert-ly.
A quick grep doesn't suggest anything that might lead to
convert-ly getting that .58 in there. Hmm.
Cheers,
- Graham