[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GUB test file naming

From: Han-Wen Nienhuys
Subject: Re: GUB test file naming
Date: Sat, 11 Jul 2009 16:14:22 -0300

When we transitioned from gub2 to gub3, the build numbers on the
installers, and all manner of documentation tarballs got broken: the
.py scripts inserted the build number implying that I have to connect
to from brazil for every build I did.  I kludged up a fix
to have the gub scripts output a HEAD buildnumber, so I could release
2.13.1 (or was it .2?).  I have never gotten round to making a real

On Sat, Jul 11, 2009 at 5:12 AM, Jan
Nieuwenhuizen<address@hidden> wrote:
>> The file: uploads/lilypond-2.13.4-HEAD.test-output.tar.bz2
>> clearly doesn't match the "m = (..." line.  What I can't
>> understand is *why* the script is searching for such a string...
>> or alternately, *why* does GUB give the test output a filename
>> that doesn't match what the later script is expecting?
> Me neither.  I never used the test feature in GUB.  I think
> something must have changed, somewhere.
>> PS if you're wondering how I managed to make any releases, the
>> answer is that after some combination of makes, renaming files,
>> deleting files, etc; the problem goes away.  However, since I
>> can't figure out which step(s) fixed it, this is hardly a
>> permenant solution.
> Interesting.  Possibly this answers how Han-Wen made releases.
> I'd just change the regexp and add "HEAD\." [or even "(HEAD\.)?"]
> and see when that breaks ... that could give more understanding
> if it isn't a full fix :-0

Han-Wen Nienhuys - address@hidden -

reply via email to

[Prev in Thread] Current Thread [Next in Thread]