bug#34279: guix-install.sh: uses /bin/bash shebang

2019-02-01 Thread
This means ./guix-install.sh doesn't work on e.g. NixOS. :-) Please use /usr/bin/env bash. The manual workaround is obvious, but this is a thousand-papercuts bug.

bug#21142: Sshfs-fuse requires fuse

2015-11-29 Thread
On Nov 29, 2015 6:01 PM, "Ludovic Courtès" wrote: > >> >> On GuixSD, this is addressed by having ‘fusermount’ setuid-root in > >> >> /run/setuid-programs, so things just work. > > > > You mean under GuixSD this works automagically? > > Yes. ‘fusermount’ is part of ‘%setuid-programs’: Still, fus

bug#21142: Sshfs-fuse requires fuse

2015-11-29 Thread
On Nov 29, 2015 3:58 PM, "Ludovic Courtès" wrote: > >> However, we explicitly patch it because in practice the ‘fusermount’ > >> binary must be at least set-user-gid to fuse, per mount.fuse(8): > > [ . . . ] > >> On GuixSD, this is addressed by having ‘fusermount’ setuid-root in > >> /run/setuid-

bug#21142: Sshfs-fuse requires fuse

2015-11-29 Thread
On 29-Nov-2015 12:19 pm, "Ludovic Courtès" wrote: > However, we explicitly patch it because in practice the ‘fusermount’ > binary must be at least set-user-gid to fuse, per mount.fuse(8): [ . . . ] > On GuixSD, this is addressed by having ‘fusermount’ setuid-root in > /run/setuid-programs, so thi

bug#21209: /gnu/store should be able to be a symlink, but it can't

2015-08-07 Thread
Not commenting on the underlying problem, but on your workaround. On 07-Aug-2015 11:22 pm, "Kragen Javier Sitaker" wrote: > > Apparently I can’t make /gnu/store a symlink: [ . . . ] > I’m working around that by directly mounting the /gnustore partition > under /gnu/store now. [ . . . ] >

bug#21142: Sshfs-fuse requires fuse

2015-07-28 Thread
On Jul 28, 2015 4:21 PM, "Mark H Weaver" wrote: > Claes Wallin (韋嘉誠) writes: > > On 27-Jul-2015 5:06 pm, "Andreas Enge" wrote: > >> > >> Hello, > >> > >> when trying to execute sshfs from the sshfs-fuse package, I obtai

bug#21142: Sshfs-fuse requires fuse

2015-07-27 Thread
On 27-Jul-2015 5:06 pm, "Andreas Enge" wrote: > > Hello, > > when trying to execute sshfs from the sshfs-fuse package, I obtain >fuse: failed to exec fusermount: No such file or directory > > I think that fuse should be a propagated input of sshfs-fuse. Maybe it's less intrusive toward the us

bug#20402: HTTP and FTP proxies for guix package / guix-daemon

2015-07-01 Thread
Nope. guix download works. It successfully looks up and connects to the proxy. When I next have the chance I will report: 1) Results with guix-compiled guix-daemon 2) Results with dev-compiled guix-daemon 3) /gnu/store hash of 1) On Jul 1, 2015 4:45 PM, "Ludovic Courtès" wrote: > &qu

bug#20402: HTTP and FTP proxies for guix package / guix-daemon

2015-07-01 Thread
On Wed, Jul 1, 2015 at 10:19 AM, Ludovic Courtès wrote: > To test, I first run the daemon like this: > > sudo sh -c 'export http_proxy=foobar ; ./pre-inst-env guix-daemon > --build-users-group=guixbuild' Could there be a difference because you are testing with the checked-out, semi-manually b

bug#20402: HTTP and FTP proxies for guix package / guix-daemon

2015-06-17 Thread
On Wed, Jun 17, 2015 at 6:46 PM, Claes Wallin (韋嘉誠) wrote: > Why so many different guile drivers? Is that expected? ... derivations. Sorry.

bug#20402: HTTP and FTP proxies for guix package / guix-daemon

2015-06-17 Thread
Finally got around to this. On Sat, Jun 13, 2015 at 7:44 PM, Ludovic Courtès wrote: > "Claes Wallin (韋嘉誠)" skribis: > >> I suppose if I have a freshly built guix with "guix package -i guix" >> or "guix package -u guix" it should be using guile

bug#20803: guix-daemon: support ftp_proxy environment variable

2015-06-13 Thread
It would be very useful to be able to tell guix-daemon to download sources and substitutes through a proxy, even when using ftp. Even more so than http, as ftp is easily messed up by NAT and "helpful" Application-Level Gateways. The format of the ftp_proxy environment variable is the same as for h

bug#20402: guix cannot download via an http proxy

2015-06-09 Thread
Would support for $ftp_proxy as well require the implementation of new functionality, or would it be a case of just letting the environment variable through?