Got it upgraded on the cvsup.postgresql.org server ... still have to do
the other servers ...
On Wed, 12 Sep 2001, Thomas Lockhart wrote:
> New problems with CVSup. We should all upgrade asap, though I'm not sure
> of the current status of builds for non-FreeBSD machines. Marc, could we
> possibly install this on the postgresql.org machine(s)?
>
> - Thomas
>
> -----Original Message-----
> From: jdp@polstra.com [mailto:jdp@polstra.com]
> Sent: Sunday, September 09, 2001 19:40 PM
> To: nanbor@cs.wustl.edu
> Subject: HEADS UP: CVSup timestamp bug
>
>
> This morning a bug was discovered in most versions of CVSup up to
> and including SNAP_16_1c. The bug causes all newly-updated files to
> receive incorrect timestamps. Usually the files receive timestamps
> from early in 1970. This bug has been present for a very long time,
> but it only began to have an effect when the Unix representation of
> the date and time passed 1,000,000,000. That occurred on 9 September
> 2001 at 01:46:40 UTC. Yes, other people had Y2K bugs, but I managed
> to produce an S1G bug.
>
> I have fixed the bug and have released a new snapshot of CVSup,
> SNAP_16_1d. I have also created binary packages for FreeBSD-4.x which
> can be installed using "pkg_add". For information about updating your
> CVSup installation, look here:
>
> http://people.freebsd.org/~jdp/s1g/
>
> To fix the bug, both the client and the server need to be upgraded to
> SNAP_16_1d. The FreeBSD mirror site maintainers have been working
> feverishly to upgrade their installations. Many of them are already
> upgraded, and the rest will be upgraded soon. Meanwhile, all CVSup
> users should upgrade their CVSup installations.
>
> I apologize for the inconvenience caused by this bug, and thank you
> in advance for your patience.
>
> John Polstra
>
