From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Nam Nguyen <namn@berkeley.edu>
Cc: 32855@debbugs.gnu.org
Subject: bug#32855: sshuttle /usr/bin/env
Date: Thu, 27 Sep 2018 21:11:45 +0200 [thread overview]
Message-ID: <87va6qhi1a.fsf@tobias.gr> (raw)
In-Reply-To: <20180927182323.GA30836@antelope>
Hullo,
Thanks for the report!
Nam Nguyen wrote:
> sshuttle is a python program that uses /usr/bin/env at line 196
> of:
> /gnu/store/...-sshuttle-0.78.4/lib/python3.6/site-packages/sshuttle/client.py
> ['sudo', '-p', '[local sudo] Password: ', '/usr/bin/env',
>
> Trying to run sshuttle on GuixSD results in:
> $ sshuttle -r user@server.com 0/0 -x server.com
> sudo: /usr/bin/env: command not found
This means that sshuttle on vanilla GuixSD has been broken ever
since I added it in 2016, which saddens me. I guess nobody else
uses it or, like me, they happen to also have a /usr/bin/env
symlink.
> Here is a potential fix that I recycled from sshoot's recipe. I
> tested it,
> and it works.
>
> $ diff
> ~/.config/guix/current/share/guile/site/2.2/gnu/packages/vpn.scm
> ~/vpn.scm
> 349a350,357
>> (arguments
>> '(#:phases
>> (modify-phases %standard-phases
>> (add-after 'unpack 'patch-paths
>> (lambda _
>> (substitute* "sshuttle/client.py"
>> (("/usr/bin/env") (which "env")))
>> #t)))))
I'll push this soon. Is it all right if I mention your name &
e-mail in the commit message?
Kind regards,
T G-R
next prev parent reply other threads:[~2018-09-27 19:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 18:23 bug#32855: sshuttle /usr/bin/env Nam Nguyen
2018-09-27 19:11 ` Tobias Geerinckx-Rice [this message]
2018-09-27 19:22 ` Nam Nguyen
2018-09-27 22:04 ` Tobias Geerinckx-Rice
2018-09-29 22:40 ` Nam Nguyen
2018-09-30 11:52 ` Tobias Geerinckx-Rice
2018-09-30 14:45 ` Nam Nguyen
2018-10-06 14:19 ` Marius Bakke
2018-10-06 14:49 ` Tobias Geerinckx-Rice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87va6qhi1a.fsf@tobias.gr \
--to=me@tobias.gr \
--cc=32855@debbugs.gnu.org \
--cc=namn@berkeley.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).