Re: 2.16.1

[Phil Holmes]

----- Original Message ----- 
From: "Graham Percival" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: <address@hidden>; "David Kastrup" <address@hidden>
Sent: Friday, November 09, 2012 6:32 PM
Subject: Re: 2.16.1


> 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


> From my experience, that's not exactly what happens.  As you say, the build 
creates a comparison of regtests built against the current binary with any 
tarball in the regtests/ directory.  For me, this was only 2.16.0 - I was 
careful to ensure this.  We would then expect this output to be put in a 
2.16.1 directory and labelled 2.16.1.  What happened in practice was that 
the output was put in a 2.17.6 directory.  This then killed the upload later 
on in the evening, since it could not find the 2.16.1 directory.  I renamed 
it and restarted the upload, which appeared to finish correctly.  I'm now 
going to update VERSION and hope the website updates during the day.

--
Phil Holmes