[spambayes-dev] RE: [Python-Dev] SSH problems getting into SourceForge's CVS?

[Tim Peters]

If you're getting messages like this today when trying to cvs up:

   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
   @       WARNING: POSSIBLE DNS SPOOFING DETECTED!          @
   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
   The RSA1 host key for cvs.spambayes.sourceforge.net has changed,
   and the key for the according IP address 66.35.250.209
   is unknown. This could either mean that
   DNS SPOOFING is happening or the IP address for the host
   and its host key have changed at the same time.
   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
   @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
   IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!

   [yadda yadda yadda]

it's apparently because SourceForge changed the way they like their CVS
servers to get addressed.  Here's a link to a python-dev article with a
Python script to crawl over your checkout tree and change the hidden CVS
cruft so that SF stops whining at you:

    http://mail.python.org/pipermail/python-dev/2004-April/044593.html

For example, in the root of my spambayes checkout, I ran

    cvs_chroot.py :ext:tim_one at cvs.sourceforge.net:/cvsroot/spambayes

and then SF stopped complaining.  The hostname part of my URLs used to be
"cvs.spambayes.sourceforge.net", and SF doesn't want the "spambayes." part
there anymore.  Since this string gets buried in CVS admin files in each of
your subtrees too, you really don't want to hunt them down and fiddle them
all by hand.