group.of.nepali.translators team mailing list archive

[Dan Streetman <1897987@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

[impact]

connecting to a remote host with py3.4 fails

[test case]

root@lp1896299-x:~# sshuttle --python python3 -r lp1896299-t.lxd 1.2.3.4/24
client: Connected.
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "assembler.py", line 39, in <module>
  File "sshuttle.server", line 273, in main
TypeError: unsupported operand type(s) for %: 'bytes' and 'tuple'
client: fatal: server died with error code 1

[regression potential]

any regression would likely prevent the initial connection from being
setup correctly.

[scope]

this is needed only for x

this was fixed in 4241381d827ca42fd40b6a4bc5a4e2fdde92577b which is
included upstream in v0.78.0 so bionic and later are already fixed.

[other info]

since xenial defaults to py35, this is mainly needed to connect from
xenial to trusty using py3 instead of py2. this is particularly
important with the change made in bug 1592853, which effectively causes
sshuttle to default to py3 if it is found on the system (previously, it
defaulted to py2 unless py3 version 3.5 exactly was available). so this
bug is needed to allow sshuttle from x to t to continue working without
needing to specify --python python2

also the commit that fixes this was partially included in the backport
for bug 1896299, this bug only adds a missing part of that backport into
the patch file to fix this bug.

** Affects: sshuttle (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: sshuttle (Ubuntu Xenial)
     Importance: Medium
     Assignee: Dan Streetman (ddstreet)
         Status: In Progress

** Also affects: sshuttle (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: sshuttle (Ubuntu)
       Status: New => Fix Released

** Changed in: sshuttle (Ubuntu Xenial)
       Status: New => In Progress

** Changed in: sshuttle (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: sshuttle (Ubuntu Xenial)
     Assignee: (unassigned) => Dan Streetman (ddstreet)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1897987

Title:
  connection to py34 fails

Status in sshuttle package in Ubuntu:
  Fix Released
Status in sshuttle source package in Xenial:
  In Progress

Bug description:
  [impact]

  connecting to a remote host with py3.4 fails

  [test case]

  root@lp1896299-x:~# sshuttle --python python3 -r lp1896299-t.lxd 1.2.3.4/24
  client: Connected.
  Traceback (most recent call last):
    File "<string>", line 1, in <module>
    File "assembler.py", line 39, in <module>
    File "sshuttle.server", line 273, in main
  TypeError: unsupported operand type(s) for %: 'bytes' and 'tuple'
  client: fatal: server died with error code 1

  [regression potential]

  any regression would likely prevent the initial connection from being
  setup correctly.

  [scope]

  this is needed only for x

  this was fixed in 4241381d827ca42fd40b6a4bc5a4e2fdde92577b which is
  included upstream in v0.78.0 so bionic and later are already fixed.

  [other info]

  since xenial defaults to py35, this is mainly needed to connect from
  xenial to trusty using py3 instead of py2. this is particularly
  important with the change made in bug 1592853, which effectively
  causes sshuttle to default to py3 if it is found on the system
  (previously, it defaulted to py2 unless py3 version 3.5 exactly was
  available). so this bug is needed to allow sshuttle from x to t to
  continue working without needing to specify --python python2

  also the commit that fixes this was partially included in the backport
  for bug 1896299, this bug only adds a missing part of that backport
  into the patch file to fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1897987/+subscriptions