On Tue, Jan 02, 2007 at 07:21:02AM +0000, Nigel Frankcom wrote:
> It went in clean on all servers when I ran it this morning. I guess
> you fixed whatever the issue was?

I believe the order of what happened was:

- I pushed the update on the evening of 12/31
- In the morning of 1/1, the automatic 3.2 update process pushed out an update
  with the same revision number, overwriting the 3.1 file
- JM pushed out a new 3.1 update package

So it's working now, but there was a time where the 3.1 channel pointed
at a 3.2 file.  Needless to say, the automatic update script needs at
least a "if [ -f ... ]" snippet to avoid overwriting existing files.

-- 
Randomly Selected Tagline:
"A CAT scan should take less time than a PET scan.  For a CAT scan,
 they're only looking for one thing, whereas a PET scan could result in
 a lot of things."               - Carl Princi, 2002/07/19

Attachment: pgpJOrb0YrRZJ.pgp
Description: PGP signature

Reply via email to