Jon:
thank you very much for trying it out and posting the Sourceforge-URL. Like
you, I am a little bit
helpless at the moment as doing a svn switch to the new URL, like:
svn switch https://svn.code.sf.net/p/oorexx/code-0 oorexx
does not succeed with the same svn errors as before (unable to connect).
(Also, in the case of bsf4oorexx the ssh protocol (svn+ssh:) has been used,
which should be secure
by itself.)
---rony
On 19.02.2017 17:10, Jon Wolfers wrote:
> This is what I get using Tortoise
>
> Updating: C:\oorexx\svn\code-0
> Error: Unable to connect to a repository at URL
> Error: 'svn+ssh://sahana...@svn.code.sourceforge.net/p/oorexx/code-0
> <http://sahana...@svn.code.sourceforge.net/p/oorexx/code-0>'
> Error: To better debug SSH connection problems, remove the -q option from
> 'ssh' in the
> Error: [tunnels] section of your Subversion configuration file.
> Error: Network connection closed unexpectedly
>
> There is a message about a change on the Sourceforge Status page here
> <https://sourceforge.net/blog/category/sitestatus/> which occured 2 days ago.
> Sounds like one now
> needs to use https to access the svn.
>
> I'm a bit of a naive SVN user. Rick helped me set up tortoise and it has
> more or less worked ever
> since.
>
> Guidance would be appreciated.
>
> Jon
>
>
>
> On 19 February 2017 at 15:33, Rony G. Flatscher <rony.flatsc...@wu.ac.at
> <mailto:rony.flatsc...@wu.ac.at>> wrote:
>
> Hi there,
>
> have tried to update the oorexx source code using "svn update", but
> unfortunately, this does
> not work all of a sudden for me.
>
> Here is the Windows copy & paste of the "svn update" with the error
> messages.
>
> F:\work\svn\oorexx>svn update Updating '.': svn: E170013: Unable to
> connect to a
> repository at URL 'http://svn.code.sf.net/p/oorexx/code-0
> <http://svn.code.sf.net/p/oorexx/code-0>' svn: E730061: Error running
> context: Es konnte
> keine Verbindung hergestellt werden, da der Zielcomputer die
> Verbindung verweigerte.
>
> The last message translates into English as: "Connection could not be
> established, because the
> server refused it."
>
> Trying an "svn update" on my Mac yields E170012 as above, the second
> message reads:
>
> svn: E120108: Error running context: The sever unexpectedly closed
> the connection.
>
> ---
>
> However, using plink.exe from PuTTY allows me to get a shell on
> sourceforge using the ssha-2
> keys that I have been using successfully in the past and which are stored
> on Sourceforge, so I
> would expect "svn update" to work as well.
>
> Here is the plink.exe output on Windows (replaced my login id with "abc"):
>
> E:\cygwin\home\Administrator\.ssh>plink -v -t
> a...@shell.sourceforge.net
> <mailto:a...@shell.sourceforge.net> create Looking up host
> "shell.sourceforge.net
> <http://shell.sourceforge.net>" Connecting to 216.34.181.119 port 22
> We claim version:
> SSH-2.0-PuTTY_Release_0.67 *Server version: SSH-2.0-OpenSSH_6.6.1*
> *We believe remote
> version has SSH-2 channel request bug* Using SSH protocol version 2
> Doing Diffie-Hellman
> group exchange Doing Diffie-Hellman key exchange with hash SHA-256
> Host key fingerprint
> is: ssh-rsa 2048 80:1c:ee:50:14:cd:ef:28:3e:82:c6:ef:44:55:d7:74
> Initialised AES-256 SDCTR
> client->server encryption Initialised HMAC-SHA-256 client->server MAC
> algorithm
> Initialised AES-256 SDCTR server->client encryption Initialised
> HMAC-SHA-256
> server->client MAC algorithm Pageant is running. Requesting keys.
> Pageant has 2 SSH-2 keys
> Using username "abc". Trying Pageant key #0 Authenticating with
> public key
> "imported-openssh-key" from agent Sending Pageant's response Access
> granted Opening
> session as main channel Opened main channel Allocated pty (ospeed
> 38400bps, ispeed
> 38400bps) Started a shell/command Requesting a new shell for "abc"
> and waiting for it to
> start. queued... creating... starting... This is an interactive shell
> created for user
> abc,users Use the "timeleft" command to see how much time remains
> before shutdown. Use the
> "shutdown" command to destroy the shell before the time limit. For
> path information and
> login help, type "sf-help". abc@shell-23008:~[abc@shell-23008 ~]$
> timeleft Time remaining
> before shutdown: 240 minutes. abc@shell-23008:~[abc@shell-23008 ~]$
> shutdown Requesting
> that your shell be shut down. This request will be processed soon.
> abc@shell-23008:~[abc@shell-23008 ~]$ Broadcast message from
> root@shell-23008
> (unknown) at 15:10 ... The system is going down for halt NOW! Server
> sent command exit
> status 255 Connection to shell-23008 closed by remote host.
> Connection to shell-23008
> closed. Disconnected: All channels closed
>
> It seems that Sourceforge would use an old SSH-2 server, namely version
> SSH-2.0-OpenSSH_6.6.1,
> where the latest version is 7.4 (from December 19, 2016). There is some
> older information
> about that bug (if it is the same) from 2014-07-07:
>
> <http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/ssh-close-vs-request.html>
>
> <http://www.chiark.greenend.org.uk/%7Esgtatham/putty/wishlist/ssh-close-vs-request.html>.
>
> As I would like to create a debug version of oorexx on my Windows
> machine, I would need the
> latest (at least a newer) version of the sources.
>
> So, is Sourceforge (doing a "svn update" for oorexx) working for you?
>
> Sorry for the noise.
>
> ---rony
>
> P.S.: Also, today, my ability to commit to bsf4oorexx on Sourceforge
> stopped. (Did update
> cygwin, Tortoise svn, etc., to no avail.)
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
