On Fri, Nov 09, 2012 at 06:02:04PM -0000, Phil Holmes wrote:
----- Original Message ----- From: "David Kastrup" <address@hidden>
To: <address@hidden>
Sent: Friday, November 09, 2012 5:36 PM
Subject: Re: 2.16.1
>>I've just built 2.16.1 and will be uploading it later this evening.
>>All seems OK except I tried to create a regtest comparison versus
>>2.16.0 and instead got a comparison of 2.17.6 versus 2.16.0.
>
>But you are certain that the binary itself is 2.16.1? How would it
>produce a comparison of 2.17.6?
The binary is certainly named as 2.16.1 so I've no doubt that it is
2.16.1 - it was also built from stable/2.16 and there's not 2.17.6
code there. I'm assuming that VERSION has 2.17.6 unstable, and it
does a regtest comparison with the highest numbered release - or at
least says it does. I don't think this is likely to be more than an
oddity.
Regtests are built from the just-compiled binaries to any regtest
tarballs you have in regtests/ . You evidently had a
regtest/lilypond-2.16.0-test.tar.gz and -2.17.6-test- tarballs in
that directory. Each tarball contains various .eps and/or
"signature" files which are used to produce the comparisons. See
the code for more details because about what's in the regtest
tarballs and how they're used, because I'm not clear on it.
- Graham