Your message dated Fri, 4 Jul 2008 02:49:48 -0500
with message-id <[EMAIL PROTECTED]>
and subject line control socket problems don't seem to be related to subversion
has caused the Debian Bug report #350893,
regarding control socket not working with svn+ssh
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
350893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=350893
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: ssh
Version: 1:4.2p1-5
Severity: normal

This may well be a bug in subversion, but I am filing it against SSH
because the control socket functionality is very new and the
subversion folks may not know about it yet.

The following should explain it all: the socket is not removed after
the svn connection was tunneled via SSH:

cirrus:~/coding/libhid> svn up                                               
[30]
At revision 295.
cirrus:~/coding/libhid> svn up                                               
[31]
Control socket 
connect(/home/madduck/.ssh/var/ssh_control_gaia.ailab.ch_22_krafft): Connection 
refused
ControlSocket /home/madduck/.ssh/var/ssh_control_gaia.ailab.ch_22_krafft 
already exists
svn: Connection closed unexpectedly

-- System Information:
Debian Release: testing/unstable
  APT prefers stable
  APT policy: (700, 'stable'), (600, 'testing'), (98, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages ssh depends on:
ii  openssh-client                1:4.2p1-5  Secure shell client, an rlogin/rsh
ii  openssh-server                1:4.2p1-5  Secure shell server, an rshd repla

ssh recommends no packages.

-- debconf-show failed

-- 
 .''`.     martin f. krafft <[EMAIL PROTECTED]>
: :'  :    proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver!
 
"'this must be a thursday,' said arthur to himself, sinking low over
 his beer.  'i never could get the hang of thursdays.'"
                                 -- hitchhiker's guide to the galaxy

Attachment: signature.asc
Description: Digital signature (GPG/PGP)


--- End Message ---
--- Begin Message ---
I appreciate that a stale ssh control socket can cause mischief, but
subversion doesn't seem to be involved anymore, given that now we

  (a) kill ssh with TERM, not KILL (has been true for a long time), and

  (b) run ssh by default with "-o ControlMaster=no" (new in 1.5.0), so
ssh launched from subversion will not attempt to create a control
socket.  It will still use one if it exists, which seems correct.
-- 
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/


--- End Message ---

Reply via email to