Tom, I just ran 'update-xastir' going from V2.0.3 compiled on 01Nov2012 to V2.0.5 compiled "just now" with no problems or errors.
73 Dave KB3EFS On 12/10/2012 02:34 PM, Tom Russo wrote: > On Mon, Dec 10, 2012 at 12:31:04PM -0700, we recorded a bogon-computron > collision of the <[email protected]> flavor, containing: >> 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. > FWIW, I just did a fresh anonymous CVS checkout using the recommended > path, and it works as it did before this problem surfaced. So my expectation > is that those with old anonymous CVS checkouts can now update, and those who > did fresh checkouts with the modified path will have to redo that with the > old path. > > Please let me know if you try anonymous CVS and what the results are, so I > can let Chris Tsai at SourceForge know if the thing is fixed to our > satisfaction. > -- David A Aitcheson [email protected] Go Green! Print this email only when necessary. _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
