Thread: cvs/website/make problems

cvs/website/make problems

From
"Greg Sabino Mullane"
Date:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Seems there is a problem with anoncvs:
> cvs update: authorization failed: server 
> anoncvs.postgresql.org rejected access to 
> /projects/cvsroot for user anoncvs

Problems like this (and similar problems with the website) 
seem to be occuring rather regularly. Perhaps someone could 
write a small expect script that would check things out 
hourly and email the correct person? (and run manually 
after any changes). Seems this might catch the problem before 
people start complaining via email lists.

Perhaps even have something that once a day goes through the 
entire motion (surf, download, extract, compile, test) 
and makes sure everything works from A to Z.


Just a thought,
Greg Sabino Mullane
greg@turnstep.com
PGP Key: 0x14964AC8 200111261433

-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html

iQA/AwUBPAKZk7ybkGcUlkrIEQI2EwCgh1xPqjxI9j8K21LZgt4AmU/uS7EAoPma
gWLyH6zp2CkdgVhlBQjGqrtV
=FDl2
-----END PGP SIGNATURE-----




Re: cvs/website/make problems

From
"Marc G. Fournier"
Date:
Let me know once you have this written, and we can look at implementing it
...

More seriously, this is the result of some *very* drastic *physical* moves
over the past month that are just starting to settle down ... once we have
it all settled out, then we pretty much go back to 'business as usual',
but its one of the reasons why the Beta, and Release, are being delayed as
they are, cause we don't want the release to go out without everything
else stabilized ...

On Mon, 26 Nov 2001, Greg Sabino Mullane wrote:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > Seems there is a problem with anoncvs:
> > cvs update: authorization failed: server
> > anoncvs.postgresql.org rejected access to
> > /projects/cvsroot for user anoncvs
>
> Problems like this (and similar problems with the website)
> seem to be occuring rather regularly. Perhaps someone could
> write a small expect script that would check things out
> hourly and email the correct person? (and run manually
> after any changes). Seems this might catch the problem before
> people start complaining via email lists.
>
> Perhaps even have something that once a day goes through the
> entire motion (surf, download, extract, compile, test)
> and makes sure everything works from A to Z.
>
>
> Just a thought,
> Greg Sabino Mullane
> greg@turnstep.com
> PGP Key: 0x14964AC8 200111261433
>
> -----BEGIN PGP SIGNATURE-----
> Comment: http://www.turnstep.com/pgp.html
>
> iQA/AwUBPAKZk7ybkGcUlkrIEQI2EwCgh1xPqjxI9j8K21LZgt4AmU/uS7EAoPma
> gWLyH6zp2CkdgVhlBQjGqrtV
> =FDl2
> -----END PGP SIGNATURE-----
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>