Обсуждение: Re: CVS vs anoncvs (was Re: Case sensitive file names)
should be four hours, but I haven't had a chance, with the newest worm/virus going around right now having killed our core router yesterday, to redirect the sync'ag with the new server ... will do that first thing tomorrow ... On Wed, 19 Sep 2001, Tom Lane wrote: > Peter Bierman <bierman@apple.com> writes: > > If it's already been fixed (yay!), the fix isn't at anoncvs yet. > > I think there is some lag between the master CVS and anoncvs now. > Marc, is that correct? How much lag? > > regards, tom lane >
"Marc G. Fournier" wrote: > should be four hours, but I haven't had a chance, with the newest > worm/virus going around right now having killed our core router yesterday, > to redirect the sync'ag with the new server ... will do that first thing > tomorrow ... > > On Wed, 19 Sep 2001, Tom Lane wrote: > > > Peter Bierman <bierman@apple.com> writes: > > > If it's already been fixed (yay!), the fix isn't at anoncvs yet. > > > > I think there is some lag between the master CVS and anoncvs now. > > Marc, is that correct? How much lag? > > > > regards, tom lane > > It's definitely more than 16 hours. I still can't see M. Meskes' commits (16:09 MEST, 10:09 EDT) While you're at it, could you please fix this error: ~/pgsql-cvs/pgsql > cvs -z3 update -dP cannot create_adm_p /tmp/cvs-serv2966/ChangeLogs Permission denied for i in `find -type d ! -name CVS ` ; do (cd $i ; cvs -z3 update -l -d ) done cvs server: Updating . cvs server: Updating . [.....] This works somehow but is really ugly and bandwidth-wasting. This even occurs with a fresh checkout: ~/pgsql-cvs/tmp > cvs -d :pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot co pgsql/ChangeLogs cvs server: Updating pgsql/ChangeLogs U pgsql/ChangeLogs/ChangeLog-7.1-7.1.1 U pgsql/ChangeLogs/ChangeLog-7.1RC1-to-7.1RC2 U pgsql/ChangeLogs/ChangeLog-7.1RC2-to-7.1RC3 U pgsql/ChangeLogs/ChangeLog-7.1RC3-to-7.1rc4 U pgsql/ChangeLogs/ChangeLog-7.1beta1-to-7.1beta3 U pgsql/ChangeLogs/ChangeLog-7.1beta3-to-7.1beta4 U pgsql/ChangeLogs/ChangeLog-7.1beta4-to-7.1beta5 U pgsql/ChangeLogs/ChangeLog-7.1beta5-to-7.1beta6 U pgsql/ChangeLogs/ChangeLog-7.1beta6-7.1RC1 U pgsql/ChangeLogs/ChangeLog-7.1rc4-7.1 ~/pgsql-cvs/tmp > cd pgsql/ ~/pgsql-cvs/tmp/pgsql > cvs update cannot create_adm_p /tmp/cvs-serv4350/ChangeLogs Permission denied Yours Christof
> While you're at it, could you please fix this error: > > ~/pgsql-cvs/pgsql > cvs -z3 update -dP > cannot create_adm_p /tmp/cvs-serv2966/ChangeLogs > Permission denied Instead of checking out over your existing checkout, checkout to a new dir and there's no problem. Chris
Christopher Kings-Lynne wrote: > > While you're at it, could you please fix this error: > > > > ~/pgsql-cvs/pgsql > cvs -z3 update -dP > > cannot create_adm_p /tmp/cvs-serv2966/ChangeLogs > > Permission denied > > Instead of checking out over your existing checkout, checkout to a new dir > and there's no problem. Sorry, I want to update (only the differences cross the wire) or diff, not check out all again twice a day (which works). Christof
Okay, its updated effective a few minutes ago ... and the upate should work as well ... On Thu, 20 Sep 2001, Christof Petig wrote: > "Marc G. Fournier" wrote: > > > should be four hours, but I haven't had a chance, with the newest > > worm/virus going around right now having killed our core router yesterday, > > to redirect the sync'ag with the new server ... will do that first thing > > tomorrow ... > > > > On Wed, 19 Sep 2001, Tom Lane wrote: > > > > > Peter Bierman <bierman@apple.com> writes: > > > > If it's already been fixed (yay!), the fix isn't at anoncvs yet. > > > > > > I think there is some lag between the master CVS and anoncvs now. > > > Marc, is that correct? How much lag? > > > > > > regards, tom lane > > > > > It's definitely more than 16 hours. I still can't see M. Meskes' commits > (16:09 MEST, 10:09 EDT) > > While you're at it, could you please fix this error: > > ~/pgsql-cvs/pgsql > cvs -z3 update -dP > cannot create_adm_p /tmp/cvs-serv2966/ChangeLogs > Permission denied > > for i in `find -type d ! -name CVS ` ; do (cd $i ; cvs -z3 update -l -d ) > done > cvs server: Updating . > cvs server: Updating . > [.....] > > This works somehow but is really ugly and bandwidth-wasting. This even occurs > with a fresh checkout: > > ~/pgsql-cvs/tmp > cvs -d > :pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot co pgsql/ChangeLogs > > cvs server: Updating pgsql/ChangeLogs > U pgsql/ChangeLogs/ChangeLog-7.1-7.1.1 > U pgsql/ChangeLogs/ChangeLog-7.1RC1-to-7.1RC2 > U pgsql/ChangeLogs/ChangeLog-7.1RC2-to-7.1RC3 > U pgsql/ChangeLogs/ChangeLog-7.1RC3-to-7.1rc4 > U pgsql/ChangeLogs/ChangeLog-7.1beta1-to-7.1beta3 > U pgsql/ChangeLogs/ChangeLog-7.1beta3-to-7.1beta4 > U pgsql/ChangeLogs/ChangeLog-7.1beta4-to-7.1beta5 > U pgsql/ChangeLogs/ChangeLog-7.1beta5-to-7.1beta6 > U pgsql/ChangeLogs/ChangeLog-7.1beta6-7.1RC1 > U pgsql/ChangeLogs/ChangeLog-7.1rc4-7.1 > ~/pgsql-cvs/tmp > cd pgsql/ > ~/pgsql-cvs/tmp/pgsql > cvs update > cannot create_adm_p /tmp/cvs-serv4350/ChangeLogs > Permission denied > > Yours > Christof > > >
"Marc G. Fournier" wrote: > Okay, its updated effective a few minutes ago ... and the upate should > work as well ... Should ... ~/pgsql-cvs/pgsql/src/interfaces/ecpg/preproc > cvs status preproc.y cvs server: failed to create lock directory for `/projects/cvsroot/pgsql/src/interfaces/ecpg/preproc' (/projects/cvsroot/pgsql/src/interfaces/ecpg/preproc/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/projects/cvsroot/pgsql/src/interfaces/ecpg/preproc' cvs [server aborted]: read lock failed - giving up ~/pgsql-cvs/pgsql > cvs update cannot create_adm_p /tmp/cvs-serv48812/ChangeLogs Permission denied ~/pgsql-cvs/pgsql > cvs update -l cvs server: Updating . cvs server: failed to create lock directory for `/projects/cvsroot/pgsql' (/projects/cvsroot/pgsql/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/projects/cvsroot/pgsql' cvs [server aborted]: read lock failed - giving up ... but it does not, yet. Christof