Ubuntu
sshuttle package

  1. Bug #1873368
  2. Comment #43

Comment 43 for bug 1873368

Revision history for this message
Dan Streetman (ddstreet) wrote :

Note that the t/x failures are *not* regressions related to this bug; they already failed with the existing versions in -release or -updates.

FROM trusty:
FAILS to python3 in t/x/b/f/g

FROM xenial:
FAILS to python3 in t

As t is ESM only now, I'm going to just ignore its failure connecting to any remote system with python3.

Since x works for py2 and py3 for all remote releases except t, and it does work with py2 in t, and the default python in t is py2, and the failure is not new (not caused by any change for this bug), I'm ignoring this failure as well.

Leaving the only remaining failures being from g to any remote release with py2:

FROM groovy:
FAILS TO python2 in t/x/b/f/g