Package: transmission-remote-cli Version: 1.7.0-1 Severity: normal Dear Maintainer,
I use conda to use different environments. When such an environment is activated, `python` points to a binary in that environment and when I then try to start transmission-remote-cli it fails (in this case because it seems to be a python2 only script and I had activated a python3 environment). Please consider patching the /usr/bin/transmission-remote-cli to simply use `/usr/bin/python2` instead of `/usr/bin/env python`. See also https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-interpreter_loc which explicitly mentions not using `/usr/bin/env python`. Thanks a lot, Jan *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.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 transmission-remote-cli depends on: ii python 2.7.13-2 Versions of packages transmission-remote-cli recommends: ii python-adns 1.2.1-5+b1 ii python-geoip 1.3.2-1+b2 ii python-ipy 1:0.83-1 ii transmission-cli 2.92-2 transmission-remote-cli suggests no packages. -- no debconf information
