Date: Thu, 20 Jun 2013 05:07:49 GMT From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/179742: devel/subversion (1.8.0): svn: E170000: Unrecognized URL scheme for 'https://xxx.xxx.xxx/aaa/aaa' Message-ID: <201306200507.r5K57nNE085856@oldred.freebsd.org> Resent-Message-ID: <201306200510.r5K5A0vs088058@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 179742 >Category: ports >Synopsis: devel/subversion (1.8.0): svn: E170000: Unrecognized URL scheme for 'https://xxx.xxx.xxx/aaa/aaa' >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 20 05:10:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: O. Hartmann >Release: FreeBSD 10.0-CURRENT/amd64 >Organization: FU Berlin >Environment: FreeBSD 10.0-CURRENT #0 r251994: Wed Jun 19 17:58:51 CEST 2013 amd64 >Description: Since the successfully update to devel/subversion 1.8.0 inclusive the missing mod_dav_svn (see PR ports/179728), the Apache 2.4.X based backend serving subversion repositories via HTTPS connection is established again. But now, even with having "svn upgrade" done in the local copy of the repositories, I always receive svn update svn: E170000: Unrecognized URL scheme for 'https:/foo.bar.de/svn/repo/software' This error is supposed to occur when SERF or NEON hasn't been compiled with subversion, as Google-master says, but I explicitely selected SERF when I compiled subversion 1.8.0 . This seems not the issue. On recent FreeBSD 10.0 (r251994) we have now also a subversion 1.8.0 client called "svnlite". Using this in the very same folder of the repo copy which has been rejected by the ports devel/subversion installed client, I can successfully check out or update the port from the remote machine. The URL is the very same as in both cases. I also have on FreeBSD 10.0 on ALL systems the weird behaviour of the ports system/portmaster, that when I have configured the port once, I have to configure the port at least again when it gets finally installed. That menas, by doing "make rmconfig" in devel/subversion removes the config. Then the selection box pops up. Selecting the options should be saving the options, but then, in the middle of compiling, the option box again pops up. And at the end, when the installation process is about to install the port finally. This weird behaviour is seen in other ports as well (pulseaudio, xrdp, et ceterum). >How-To-Repeat: Update/install port devel/subversion. Have a local copy of a repository at hand which is backed up by a subversion server run via Apache 2.4 (this is the setup we use). After "svn upgrade" of a former subversion 1.7.10 local copy try to do "svn update" or "svn co". In all of our cases, we receive a "svn: E170000: Unrecognized URL scheme for". Have now a most recent copy of FreeBSD 10.0 running, on which svnlite has been recently introduced and is present in the system's world/path. Try the same procedure with the prior failing copy of your repo. This should now work and svnlite should update/checkout the repo that has been reported failing before. In my opnion, this indicates that the backend is working correctly (apache24/subversion with mod_dav_svn/mod_authz). >Fix: Not known. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201306200507.r5K57nNE085856>