Re: SourceForge CVS repository corruption

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Tue, 8 Jun 2004 01:28:50 +0200 (CEST)

On Tue, 8 Jun 2004, Evgeny Kotsuba wrote:

> On Tue, 8 Jun 2004 00:32:23 +0200 (CEST)
> Henrik Nordstrom <hno@squid-cache.org> wrote:
> >The SourceForge CVS repository has been corrupted in at least the
> >following files:
>
> It seems that all cvs.sourceforge.net:/cvsroot/squid co -rs2_5 -d
> squid-s2_5 squid is also corrupted/

Only a few files is corrupted, but cvs will choke badly on the corrupted
files on any checkout/update attempts.

It is the CVS files as such that have been corrupted. Not the individual
source revisions.

> By the way, the problems with DNS for cvs.devel.squid-cache.org is also
> stiil i in place (Problem 's localisation is somewere at SourceForge's
> DNS servers - some servers know about cvs.devel.squid-cache.org while
> other don't know)

cvs.devel.squid-cache.org is an CNAME for cvs.sourceforge.net. The
SourceForge servers should not know about cvs.devel.squid-cache.org as
this is a squid-cache.org name.

Most likely your DNS resolver (the name server referenced by resolv.conf)
is broken and does not handle expired DNS records correctly in all
situations. Have seen this a couple of times before on RedHat 7 and 8... I
would recommend you to first try upgrading your DNS server before assuming
the problem is with the SourceForge servers.

Regards
Henrik
Received on Mon Jun 07 2004 - 17:28:55 MDT

This archive was generated by hypermail pre-2.1.9 : Wed Jun 30 2004 - 12:00:03 MDT