Your message dated Sat, 6 Aug 2016 20:36:26 +1000
with message-id <[email protected]>
and subject line Re: Bug#810930: Fixed in 0.76-1
has caused the Debian Bug report #810930,
regarding sshuttle: Crashes if using the --seed-hosts option
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.)


-- 
810930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810930
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sshuttle
Version: 0.75-1
Severity: normal
Tags: patch upstream

Dear Maintainer,

When using the --seed-hosts command line option, sshuttle crashes on
connect. This is due to difference in handling of bytes in between python 2 & 3.
I submitted pull request #63 to upstream.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sshuttle depends on:
ii  iptables                     1.4.21-2+b1
ii  openssh-client [ssh-client]  1:7.1p1-6
ii  python3-pkg-resources        18.8-1
pn  python3:any                  <none>

Versions of packages sshuttle recommends:
ii  sudo  1.8.15-1.1

Versions of packages sshuttle suggests:
pn  autossh  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 0.76-1

On Mon, Jan 18, 2016 at 05:09:04PM +0000, Shai Ayal wrote:
> Thank you

This bug was never correctly closed. Closing it now.

Thanks
-- 
Brian May <[email protected]>

--- End Message ---

Reply via email to