Bug 221070 - Handbook points users to use https with subversion, but https does not work
Summary: Handbook points users to use https with subversion, but https does not work
Status: Closed DUPLICATE of bug 219367
Alias: None
Product: Documentation
Classification: Unclassified
Component: Books & Articles (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-doc (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-28 14:44 UTC by Russell Haley
Modified: 2017-07-28 20:14 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Russell Haley 2017-07-28 14:44:43 UTC
The handbook points users to use the HTTPS protocol for retrieving the FreeBSD source code with subversion. The two instances I found were:

https://www.freebsd.org/doc/handbook/svn.html

https://www.freebsd.org/doc/handbook/makeworld.html

Currently using http:// fails with various messages depending on the day it seems. Sometimes it complains about depth, sometimes that the hostname is not available. 

Using svn:// instead of https:// corrects the issue somewhat, but the svn protocol is not a robust in my experience.

I have assumed this to be a documentation issue as I have heard nothing about an official change away from https and my query on the ARM mailing list did not elicit any responses indicating such a change. However, someone did respond and tell me they also had to switch away from https a few weeks ago.
Comment 1 Kurt Jaeger freebsd_committer freebsd_triage 2017-07-28 16:56:24 UTC
Which endpoint do you retrieve from ?

I'm testing from 2001:41c8:112:8300::e6a:0 right now and it looks fine.
Comment 2 Kurt Jaeger freebsd_committer freebsd_triage 2017-07-28 16:56:47 UTC
That's svnmir.bme.freebsd.org, btw.
Comment 3 Kurt Jaeger freebsd_committer freebsd_triage 2017-07-28 16:57:16 UTC
See also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219367
Comment 4 Russell Haley 2017-07-28 20:06:23 UTC

*** This bug has been marked as a duplicate of bug 219367 ***
Comment 5 Russell Haley 2017-07-28 20:14:01 UTC
(In reply to Kurt Jaeger from comment #1)
Sorry, I was rushing this morning. I followed the handbook instructions. I will need to check my output later to verify resolved endpoint.