[Xastir] CVS back online
Tom Russo
russo at bogodyn.org
Thu Dec 6 17:39:28 EST 2012
On Thu, Dec 06, 2012 at 03:30:33PM -0700, we recorded a bogon-computron collision of the <russo at bogodyn.org> flavor, containing:
> On Thu, Dec 06, 2012 at 04:10:57PM -0600, we recorded a bogon-computron collision of the <kd5mkv at hotmail.com> flavor, containing:
> > cvs update: CC_OpenStreetMap_logo.png is no longer in the repository
>
> > cvs update: Updating CVSROOT
>
> [etc.]
> > cvs update: cannot open directory /cvsroot/xastir/xastir/src: No such file
> > or directory
> > cvs update: skipping directory src
> > cvs update: Updating symbols
> > cvs update: cannot open directory /cvsroot/xastir/xastir/symbols: No such
> > file or directory
> > cvs update: skipping directory symbols
> > cvs update: Updating xastir
>
> [etc., etc.]
>
> Clearly, anonymous CVS is still broken. The errors you're getting are on
> the sourceforge side, and are not problems with "./configure" or "bootstrap.sh"
> --- unless you count the fact that CVS is so confused that it's REMOVED
> pretty much all the files that it thinks it can't find in the repository.
>
> This problem has to be fixed by sourceforge. Your best bet is to submit
> a support request to SF directly. They seem to think that anonymous CVS is
> back on line, as they've announced it on their news page, but your output
> clearly shows that there's something wrong on their end.
Just did a fresh anonymous CVS checkout and it worked, but in a bizarre
way. It checked out not only Xastir, but the CVSROOT directory associated
with the project. This is not the right behavior, but it does mean there's a
path forward in the short term: blow away your CVS checkout, and use this
command to check out a new one:
cvs -d:pserver:anonymous at xastir.cvs.sourceforge.net:/cvsroot/xastir/xastir co xastir
The difference here is the repository path, "/cvsroot/xastir/xastir" instead
of "/cvsroot/xastir" --- the latter will create xastir/CVSROOT and
xastir/xastir, the former will get you just xastir.
This is only a workaround for a broken set-up at SourceForge. If they FIX the
issue, you'll have to blow away your checkout and check it out again using
the old instructions.
This should still be reported to sourceforge as a problem.
--
Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/
Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM
echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]
More information about the Xastir
mailing list