Hi Bill, I can't recall exactly what the reason was, but, in the past there were various checkout issues from SF when using the svn:// prefix, which is why I opted for using the http:// prefix.
For what it's worth, since SF came back up after their last major down period, I've not had any trouble with checkouts or updates, including the boost addition. However, I've been using Linux almost exclusively the last couple months. If users want to test svn:// v.s. http://, they can edit the top of: C:\JTSDK\scripts\qtenv-build-wsjtx.cmd For HTTP (default) SET devurl=http://svn.code.sf.net/p/wsjt/wsjt/branches SET garurl=http://svn.code.sf.net/p/wsjt/wsjt/tags SET baseurl=http://svn.code.sf.net/p/wsjt/wsjt For SVN (optional) SET devurl=svn://svn.code.sf.net/p/wsjt/wsjt/branches SET garurl=svn://svn.code.sf.net/p/wsjt/wsjt/tags SET baseurl=svn://svn.code.sf.net/p/wsjt/wsjt Obviously, if they change the url, then a relocate or new checkout would be needed. 73's Greg, KI7MT On 3/2/2017 7:00 AM, Bill Somerville wrote: > On 02/03/2017 13:11, Wolfgang wrote: >> (JTSDK-QT 5.5 ) C:\JTSDK\src\wsjtx)svn info >> Path: . >> Working Copy Root Path: C:\JTSDK\src\wsjtx >> URL:http://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx >> Relative URL: ^/branches/wsjtx >> Repository Root:http://svn.code.sf.net/p/wsjt/wsjt >> Repository UUID: ab8295b8-cf94-4d9e-aec4-7959e3be5d79 >> Revision: 7593 >> Node Kind: directory >> Schedule: normal >> Last Changed Author: bsomervi >> Last Changed Rev: 7593 >> Last Changed Date: 2017-03-02 03:45:29 +0100 (Do, 02 Mrz 2017) > > Hi Wolfgang, > > that's interesting. I wonder if the use of the HTTP scheme is the root > of the problem. SourceForge offer the SVN and HTTPS schemes for > read-only Subversion repository access. Clearly HTTP does work as well > and I have just tested doing fresh checkouts using it without issue. I > think we should change to using the SVN scheme in case HTTP does stop > working and SVN is probably a little more efficient. > > Can someone who uses the JTSDK for write access to the WSJT repository > explain how they set up their Subversion workspace for read+write access > please? > > Greg can easily change the initial checkout URL in the JTSDK to use the > SVN scheme but that will not change anything for those that, sensibly, > only ever do updates on an existing workspace. > > If anyone is suffering this time out problem right now, you can > experiment with switching the scheme of your Subversion client area by > typing the following: > > cd C:\JTSDK\src\wsjtx > svn relocate svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx > > then try the update again, probably preceded by: > > svn cleanup > > if the last update attempt failed. > > The above `svn relocate ...` command will be overridden if you ask the > JTSDK to do a clean checkout as it will revert to HTTP scheme. > > 73 > Bill > G4WJS. > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
