Bug 232945 - devel/subversion: ... does not support the HTTP/DAV protocol
Summary: devel/subversion: ... does not support the HTTP/DAV protocol
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Walter Schwarzenfeld
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-03 20:46 UTC by cyclaero
Modified: 2019-03-03 22:45 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (lev)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description cyclaero 2018-11-03 20:46:06 UTC 
I updated devel/subversion via build from the ports. The previous version was 1.10.3. Now it is 1.11.0. I need it with SASL2 support, and I turned on the respective switch, however, I left all other options at their default states.

Now, when I try to svn update from within any working copy to remote HTTPS repositories, I see the following error:

svn: E170013: Unable to connect to a repository at URL 'https://github.com/cyclaero/ContentCGI.git/trunk'
svn: E175003: The server at 'https://github.com/cyclaero/ContentCGI.git/trunk' does not support the HTTP/DAV protocol

As a matter of fact, the server is falsely incriminated by svn 1.11, since the GitHub server does support the HTTP/DAV protocol very well. I cross-checked this with subversion 1.10 on another machine. And when I do a quick downgrade-install by the way of the binary packages of subversion v1.10.3 (1.11 didn’t made it into the binary repository yet), using the command below, then HTTP/DAV works as well on the given machine.

pkg delete -f subversion; pkg install subversion
Comment 1 Lev A. Serebryakov freebsd_committer freebsd_triage 2018-11-05 21:36:13 UTC 
(In reply to cyclaero from comment #0)
I've checked Windows and Linux versions and error is the same.

Yes, 1.10.x doesn't have this problem on FreeBSD, Linux and Windows.

Looks like it is upstream problem

Please, report it upstream (to subversion's developers).
Comment 2 cyclaero 2018-11-06 00:21:54 UTC 
see the following thread:

https://mail-archives.apache.org/mod_mbox/subversion-users/201811.mbox/%3c16862E55-81D9-4FA7-B6D0-ABCCDD4D3E1D@obsigna.com%3e

The Subversion developers and the GitHub engineers need sort this out. For the time being, our options are:

1. stay with subversion 1.10
2. don’t use GitHub with subversion
3. apply the patch mentioned in my second post to the subversion-users mailing list as a temporary hot-fix to subversion 1.11

I tried the whole afternoon to do (1), but there was running in circles resolving conflicts because I got also devel/git with subversion support installed, and this insisted to stay with subversion 1.11.

At the end of the day we need to wait what comes out of the necessary discussion between Subversion and GitHub.
Comment 3 danielsh 2018-12-29 12:40:32 UTC 
tl;dr This was a GitHub bug which they fixed on their end.  You can now use 1.11.0 with GitHub.  I recommend to close this bug now, no further action needed.
Comment 4 Michael Osipov 2019-03-03 22:25:21 UTC 
Please close, this was a bug in GitHub.
Comment 5 Walter Schwarzenfeld 2019-03-03 22:45:55 UTC 
See comment4. Overcome by events.