Thread: [Fwd: [Fwd: [tao-users] FW: HEADS UP: CVSup timestamp bug]]
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
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 >
> Got it upgraded on the cvsup.postgresql.org server ... still have to do
> the other servers ...
I'm hopelessly confused on what servers we have, and whether that one is
new, old, online, offline, being built, or being decommissioned. Can I
use this machine (or virtual machine) for cvsup now?
- Thomas
On Mon, 17 Sep 2001, Thomas Lockhart wrote: > > Got it upgraded on the cvsup.postgresql.org server ... still have to do > > the other servers ... > > I'm hopelessly confused on what servers we have, and whether that one is > new, old, online, offline, being built, or being decommissioned. Can I > use this machine (or virtual machine) for cvsup now? yes, but due to the CVSROOT move yesterday, its only as current as before the move ... I just have to change around its pointers this morning ... Right now, we have: anoncvs.postgresql.org== cvsup.postgresql.org - same machine, brand new cvs.postgresql.org== www.postgresql.org== mail.postgresql.org== ssh/login server - same machine rsync.postgresql.org== ftp.postgresql.org== primary www server - old server, slowly being migrated between the above two machines (rsync -> anoncvs, ftp/primary -> cvs)
Re: [Fwd: [Fwd: [tao-users] FW: HEADS UP: CVSup timestamp bug]]
From
"Christopher Kings-Lynne"
Date:
I am still unable to update my cvs tree! What server, username, password, cvsroot and module do I need to use? Thanks, Chris > -----Original Message----- > From: pgsql-hackers-owner@postgresql.org > [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Marc G. Fournier > Sent: Monday, 17 September 2001 8:03 PM > To: Thomas Lockhart > Cc: Hackers List > Subject: Re: [HACKERS] [Fwd: [Fwd: [tao-users] FW: HEADS UP: CVSup > timestamp bug]] > > > On Mon, 17 Sep 2001, Thomas Lockhart wrote: > > > > Got it upgraded on the cvsup.postgresql.org server ... still > have to do > > > the other servers ... > > > > I'm hopelessly confused on what servers we have, and whether that one is > > new, old, online, offline, being built, or being decommissioned. Can I > > use this machine (or virtual machine) for cvsup now? > > yes, but due to the CVSROOT move yesterday, its only as current as before > the move ... I just have to change around its pointers this morning ... > > Right now, we have: > > anoncvs.postgresql.org > == cvsup.postgresql.org > - same machine, brand new > cvs.postgresql.org > == www.postgresql.org > == mail.postgresql.org > == ssh/login server > - same machine > > rsync.postgresql.org > == ftp.postgresql.org > == primary www server > - old server, slowly being migrated between the above two > machines (rsync -> anoncvs, ftp/primary -> cvs) > > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster >
> Right now, we have:
OK, these are three *physically distinct* machines with some aliases
attached to them? Or are virtual hosts involved too?? I need a site map
from someone since nothing but my home directory is in the place they
used to be (actually, even that moved but I *do* know how to find my
home directory ;). I've found some stuff, but no doc areas and no ftp
areas.
Help!! (At your convenience, of course; I *know* you are doing a lot of
work on this ;)
- Thomas
golem> host cvsup.postgresql.org
cvsup.postgresql.org is a nickname for rs.PostgreSQL.org
rs.PostgreSQL.org has address 64.39.15.238
rs.PostgreSQL.org has address 64.39.15.238
golem> host anoncvs.postgresql.org
anoncvs.postgresql.org is a nickname for rs.PostgreSQL.org
rs.PostgreSQL.org has address 64.39.15.238
rs.PostgreSQL.org has address 64.39.15.238
golem> host cvs.postgresql.org
cvs.postgresql.org is a nickname for mail.postgresql.org
mail.postgresql.org has address 216.126.85.28
mail.postgresql.org has address 216.126.85.28
golem> host mail.postgresql.org
mail.postgresql.org has address 216.126.85.28
golem> host www.postgresql.org
www.postgresql.org is a nickname for rs.postgresql.org
rs.postgresql.org has address 64.39.15.238
rs.postgresql.org has address 64.39.15.238
golem> host ftp.postgresql.org
ftp.postgresql.org is a nickname for postgresql.org
postgresql.org has address 216.126.84.28
postgresql.org has address 216.126.84.28
golem> host rsync.postgresql.org
rsync.postgresql.org is a nickname for rs.postgresql.org
rs.postgresql.org has address 64.39.15.238
rs.postgresql.org has address 64.39.15.238
> anoncvs.postgresql.org
> == cvsup.postgresql.org
> - same machine, brand new
> cvs.postgresql.org
> == www.postgresql.org
> == mail.postgresql.org
> == ssh/login server
> - same machine
>
> rsync.postgresql.org
> == ftp.postgresql.org
> == primary www server
> - old server, slowly being migrated between the above two
> machines (rsync -> anoncvs, ftp/primary -> cvs)