svn server problem?

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

svn server problem?

Richard L. Hamilton-3

svn co https://svn.macports.org/repository/macports/contrib/MacPorts_Framework@86927
svn: E170013: Unable to connect to a repository at URL 'https://svn.macports.org/repository/macports/contrib/MacPorts_Framework'
svn: E120108: Error running context: The server unexpectedly closed the connection.

(the URL came from the log for MacPorts_Framework, which had that problem too; just figured I'd try the command by hand, for the heck of it)


signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: svn server problem?

Ryan Schmidt-24
On Jul 14, 2017, at 19:24, Richard L. Hamilton wrote:
>
> svn co https://svn.macports.org/repository/macports/contrib/MacPorts_Framework@86927
> svn: E170013: Unable to connect to a repository at URL 'https://svn.macports.org/repository/macports/contrib/MacPorts_Framework'
> svn: E120108: Error running context: The server unexpectedly closed the connection.
>
> (the URL came from the log for MacPorts_Framework, which had that problem too; just figured I'd try the command by hand, for the heck of it)


The old svn repo should still work (I'm able to access that URL in a web browser) but the port should be updated to fetch from GitHub.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: svn server problem?

Clemens Lang-2
In reply to this post by Richard L. Hamilton-3
On Fri, Jul 14, 2017 at 08:24:05PM -0400, Richard L. Hamilton wrote:
> svn co https://svn.macports.org/repository/macports/contrib/MacPorts_Framework@86927
> svn: E170013: Unable to connect to a repository at URL 'https://svn.macports.org/repository/macports/contrib/MacPorts_Framework'
> svn: E120108: Error running context: The server unexpectedly closed the connection.
>
> (the URL came from the log for MacPorts_Framework, which had that problem too; just figured I'd try the command by hand, for the heck of it)

Works fine for me. Does the problem still persist? If so, which version
of Subversion do you use?

--
Clemens
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: svn server problem?

Richard L. Hamilton-3

On Jul 15, 2017, at 14:43, Clemens Lang <[hidden email]> wrote:

On Fri, Jul 14, 2017 at 08:24:05PM -0400, Richard L. Hamilton wrote:
svn co https://svn.macports.org/repository/macports/contrib/MacPorts_Framework@86927
svn: E170013: Unable to connect to a repository at URL 'https://svn.macports.org/repository/macports/contrib/MacPorts_Framework'
svn: E120108: Error running context: The server unexpectedly closed the connection.

(the URL came from the log for MacPorts_Framework, which had that problem too; just figured I'd try the command by hand, for the heck of it)

Works fine for me. Does the problem still persist? If so, which version
of Subversion do you use?

--
Clemens



sh-3.2$ type svn
svn is hashed (/usr/bin/svn)
sh-3.2$ svn --version|head -1
svn, version 1.9.4 (r1740329)
svn: E170013: Unable to connect to a repository at URL 'https://svn.macports.org/repository/macports/contrib/MacPorts_Framework'
svn: E120108: Error running context: The server unexpectedly closed the connection.
sh-3.2$ # also without the @##### suffix:
svn: E170013: Unable to connect to a repository at URL 'https://svn.macports.org/repository/macports/contrib/MacPorts_Framework'
svn: E120108: Error running context: The server unexpectedly closed the connection.

sh-3.2$ # same with the newer version in MacPorts:
sh-3.2$ /opt/local/bin/svn --version|head -1
svn, version 1.9.6 (r1800392)
svn: E170013: Unable to connect to a repository at URL 'https://svn.macports.org/repository/macports/contrib/MacPorts_Framework'
svn: E120108: Error running context: The server unexpectedly closed the connection.
sh-3.2$ # and again without the suffix:
svn: E170013: Unable to connect to a repository at URL 'https://svn.macports.org/repository/macports/contrib/MacPorts_Framework'
svn: E120108: Error running context: The server unexpectedly closed the connection.


With a browser, the URL with the @###### suffix seems to redirect to https://trac.macports.org/changeset/86927/contrib/MacPorts_Framework
while without the suffix, it at least comes up on a much plainer page.

Also odd is that the version apparently identified by the suffix is rather old, compared to the latest; I've got to wonder if the Macports_Framework port has been updated in quite a while...


signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: svn server problem?

Clemens Lang-2
Hi,

On Sat, Jul 15, 2017 at 09:06:08PM -0400, Richard L. Hamilton wrote:
> With a browser, the URL with the @###### suffix seems to redirect to
> https://trac.macports.org/changeset/86927/contrib/MacPorts_Framework
> while without the suffix, it at least comes up on a much plainer page.

Yes. We added the redirect deliberately so that the git-svn-id headers
created by our SVN->Git migration tooling would be clickable:

  https://github.com/macports/macports-base/commit/c610ee4ceaa500be41aa0d47c2c0f1f2c2d5e604

However, the SVN client does not send the @###### part to the server
when you run svn co on it.

In fact, looking at the logs, I don't see any of the typical patterns an
SVN client would send when attempting a checkout. Considering the
checkout works for me with and without the @ suffix, do you happen to
have any proxies or internet security utilities configured on your
machine that might intercept your traffic?

If you can rule that out, can you grab a packet capture for me, e.g.
with Wireshark?

> Also odd is that the version apparently identified by the suffix is
> rather old, compared to the latest; I've got to wonder if the
> Macports_Framework port has been updated in quite a while...

That's not surprising, since the MacPorts_Framework code itself hasn't
been touched in a while:

  https://github.com/macports/pallet/tree/master/MacPorts_Framework

The Portfile should still be updated to fetch from GitHub instead of
Subversion, though.

--
Clemens
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: svn server problem?

Richard L. Hamilton-3
Rebooted my router; worked afterward.

I have no proxies, and no particularly strange rules, certainly not for most sorts of client functionality.  But, like most home routers, it NATs a single external address, and  I have enough UPnP stuff (server processes, occasional BT client, etc), that I suppose an accumulation of rules that didn't time out could get ugly; Parallels Desktop is an example of something that doesn't clean up its rules (just keeps adding more periodically), so I already know I have to reboot the router once in a while to get rid of those.

> On Jul 16, 2017, at 05:56, Clemens Lang <[hidden email]> wrote:
>
> Hi,
>
> On Sat, Jul 15, 2017 at 09:06:08PM -0400, Richard L. Hamilton wrote:
>> With a browser, the URL with the @###### suffix seems to redirect to
>> https://trac.macports.org/changeset/86927/contrib/MacPorts_Framework
>> while without the suffix, it at least comes up on a much plainer page.
>
> Yes. We added the redirect deliberately so that the git-svn-id headers
> created by our SVN->Git migration tooling would be clickable:
>
>  https://github.com/macports/macports-base/commit/c610ee4ceaa500be41aa0d47c2c0f1f2c2d5e604
>
> However, the SVN client does not send the @###### part to the server
> when you run svn co on it.
>
> In fact, looking at the logs, I don't see any of the typical patterns an
> SVN client would send when attempting a checkout. Considering the
> checkout works for me with and without the @ suffix, do you happen to
> have any proxies or internet security utilities configured on your
> machine that might intercept your traffic?
>
> If you can rule that out, can you grab a packet capture for me, e.g.
> with Wireshark?
>
>> Also odd is that the version apparently identified by the suffix is
>> rather old, compared to the latest; I've got to wonder if the
>> Macports_Framework port has been updated in quite a while...
>
> That's not surprising, since the MacPorts_Framework code itself hasn't
> been touched in a while:
>
>  https://github.com/macports/pallet/tree/master/MacPorts_Framework
>
> The Portfile should still be updated to fetch from GitHub instead of
> Subversion, though.
>
> --
> Clemens
>


signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: svn server problem?

Richard L. Hamilton-3

> On Jul 16, 2017, at 06:55, Richard L. Hamilton <[hidden email]> wrote:
>
> Rebooted my router; worked afterward.
>
> I have no proxies, and no particularly strange rules, certainly not for most sorts of client functionality.  But, like most home routers, it NATs a single external address, and  I have enough UPnP stuff (server processes, occasional BT client, etc), that I suppose an accumulation of rules that didn't time out could get ugly; Parallels Desktop is an example of something that doesn't clean up its rules (just keeps adding more periodically), so I already know I have to reboot the router once in a while to get rid of those.


That would be Parallels Access (remote desktop access to Mac that may be running Parallels VM's, and to the VM's on it) rather than Parallels Desktop.


signature.asc (859 bytes) Download Attachment
Loading...