[Xastir] [ctsai at users.sf.net: [forge:site-support] #1887 Anonymous CVS behavior has changed since the service was re-established]

[Tom Russo]

Got this from SourceForge today.

Looks like the next time a developer makes a commit, the anon cvs thing will
return to old behavior, which means that anyone who used a workaround to 
checkout in the meantime will have to go back to the old deal.

I just this minute made an inconsequential commit (added a comment line to
configure.ac) to force anon CVS to by updated.

If those who have existing anonymous CVS checkouts with the 
README.CVS-recommended repository could check that CVS update works, that'd
be helpful.  Those who did new checkouts using the path with the extra
"/xastir" in it will have to do fresh checkouts without the extra path
element.

If this works, please let me know and I'll get back to Chris.

----- Forwarded message from Chris Tsai <ctsai at users.sf.net> -----

Date: Mon, 10 Dec 2012 19:25:10 +0000
From: Chris Tsai <ctsai at users.sf.net>
To: "[forge:site-support] " <1887 at site-support.forge.p.re.sf.net>
Subject: [forge:site-support] #1887 Anonymous CVS behavior has changed since
	the service was re-established

   So, the sync script between the developer and anonymous access has been
   fixed, however, you won't see this as fixed until a new developer change
   is made. Once that's done, it should correct the anonymous access with the
   next sync.

   Let me know if this helps!

   Regards,
   Chris Tsai, SourceForge.net Support

   --------------------------------------------------------------------------

   [1][site-support:#1887] Anonymous CVS behavior has changed since the
   service was re-established

   Status: pending
   Labels: siteops p3
   Created: Thu Dec 06, 2012 10:54 PM UTC by Tom Russo
   Last Updated: Fri Dec 07, 2012 04:05 PM UTC
   Owner: Chris Tsai

   The anonymous cvs service behavior after it has been restored has changed
   in a manner that has caused users of the Xastir project to be unable to
   issue "cvs update" on existing checkouts.

   The long-standing instructions from project developers to anon CVS users
   has been that they should do their initial checkouts with:

   cvs -d:pserver:anonymous at xastir.cvs.sourceforge.net:/cvsroot/xastir co
   xastir

   Users who have done so have begun to report that "cvs update" is spewing
   errors now. An example (heavily trimmed) from a user report follows:

     cvs update
     cvs update: Updating .
     cvs update: .cvsignore is no longer in the repository
     cvs update: ABOUT-NLS is no longer in the repository
     cvs update: AUTHORS is no longer in the repository
     cvs update: CC_OpenStreetMap_logo.png is no longer in the repository
     cvs update: CC_OpenStreetMap_txt.png is no longer in the repository
     cvs update: COPYING is no longer in the repository
     [2][... one such message for every single file normally present in the
     top level...]
     cvs update: Updating CVSROOT
     U CVSROOT/checkoutlist
     U CVSROOT/commitinfo
     U CVSROOT/config
     U CVSROOT/cvswrappers
     U CVSROOT/editinfo
     U CVSROOT/loginfo
     U CVSROOT/modules
     U CVSROOT/notify
     U CVSROOT/rcsinfo
     U CVSROOT/taginfo
     U CVSROOT/verifymsg
     [3][This is new --- no normal checkout should have included CVSROOT]
     cvs update: Updating CVSROOT/Emptydir
     cvs update: Updating Davis
     cvs update: cannot open directory /cvsroot/xastir/xastir/Davis: No such
     file or directory
     [4][one such error message for every subdirectory in the project]

   When I checked into this, I discovered that a fresh checkout using our
   standard instructions now gets not only the normal files in the project,
   but the CVSROOT directory, too. Also, all files are an additional level
   down in path name.

   I found that issuing a modified cvs checkout:

   cvs -d:pserver:anonymous at xastir.cvs.sourceforge.net:/cvsroot/xastir/xastir
   co xastir

   produced a checkout that matched prior behavior.

   It appears that an extra level of "xastir" has been added to the
   repository path somehow, and this has broken the ability to update
   existing checkouts.

   Could you please look into this and let us know if anonymous CVS can be
   returned to its old behavior? We have given our users the workaround (to
   blow away their existing checkouts and use the modified repository to get
   a new one), but that will, of course, break their checkouts again if the
   service is returned to old behavior.

   --------------------------------------------------------------------------

   Sent from sourceforge.net because you indicated interest in
   [5]https://sourceforge.net/p/forge/site-support/1887/

   To unsubscribe from further messages, please visit
   [6]https://sourceforge.net/auth/prefs/

References

   Visible links
   1. http://sourceforge.net/p/forge/site-support/1887/
   2. http://sourceforge.net/...%20one%20such%20message%20for%20every%20single%20file%20normally%20present%20in%20the%20top%20level...
   3. http://sourceforge.net/This%20is%20new%20---%20no%20normal%20checkout%20should%20have%20included%20CVSROOT
   4. http://sourceforge.net/one%20such%20error%20message%20for%20every%20subdirectory%20in%20the%20project
   5. https://sourceforge.net/p/forge/site-support/1887/
   6. https://sourceforge.net/auth/prefs/


----- End forwarded message -----

-- 
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]