[Nix-dev] python3.4-bedup-20140206 doesn't build
Hi guys, I tried to get bedup running, refuses to build. Any idea what's wrong with this package? exporting g...@github.com:g2p/bedup.git (rev 80cb217d4819a03e159e42850a9a3f14e2b278a3) into /nix/store/j3bz1nhqxgpq5f11v7qbpzr02pnp0liy-git-export Initialized empty Git repository in /nix/store/j3bz1nhqxgpq5f11v7qbpzr02pnp0liy-git-export/.git/ error: cannot run ssh: No such file or directory fatal: unable to fork error: cannot run ssh: No such file or directory fatal: unable to fork Unable to checkout 80cb217d4819a03e159e42850a9a3f14e2b278a3 from g...@github.com:g2p/bedup.git. builder for `/nix/store/4sihkx15ygp5n42ykms46l7b15qd0k9s-git-export.drv' failed with exit code 1 cannot build derivation `/nix/store/2d4pk9rfji9iml59s0xkhhga43cqzy3x-python3.4-bedup-20140206.drv': 1 dependencies couldn't be built cannot build derivation `/nix/store/9dhy1wq67g32cv99ap120ncicddsb5xa-system-path.drv': 1 dependencies couldn't be built cannot build derivation `/nix/store/m5vbabdv4lawsb1jl7mjqclm6wznyli2-nixos-14.04pre42122.e572b5c.drv': 1 dependencies couldn't be built error: build of `/nix/store/m5vbabdv4lawsb1jl7mjqclm6wznyli2-nixos-14.04pre42122.e572b5c.drv' failed Aloha, RK. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] python3.4-bedup-20140206 doesn't build
use public git urls On Thu, Apr 17, 2014 at 7:54 AM, Raahul Kumar raahul.ku...@gmail.com wrote: Hi guys, I tried to get bedup running, refuses to build. Any idea what's wrong with this package? exporting g...@github.com:g2p/bedup.git (rev 80cb217d4819a03e159e42850a9a3f14e2b278a3) into /nix/store/j3bz1nhqxgpq5f11v7qbpzr02pnp0liy-git-export Initialized empty Git repository in /nix/store/j3bz1nhqxgpq5f11v7qbpzr02pnp0liy-git-export/.git/ error: cannot run ssh: No such file or directory fatal: unable to fork error: cannot run ssh: No such file or directory fatal: unable to fork Unable to checkout 80cb217d4819a03e159e42850a9a3f14e2b278a3 from g...@github.com:g2p/bedup.git. builder for `/nix/store/4sihkx15ygp5n42ykms46l7b15qd0k9s-git-export.drv' failed with exit code 1 cannot build derivation `/nix/store/2d4pk9rfji9iml59s0xkhhga43cqzy3x-python3.4-bedup-20140206.drv': 1 dependencies couldn't be built cannot build derivation `/nix/store/9dhy1wq67g32cv99ap120ncicddsb5xa-system-path.drv': 1 dependencies couldn't be built cannot build derivation `/nix/store/m5vbabdv4lawsb1jl7mjqclm6wznyli2-nixos-14.04pre42122.e572b5c.drv': 1 dependencies couldn't be built error: build of `/nix/store/m5vbabdv4lawsb1jl7mjqclm6wznyli2-nixos-14.04pre42122.e572b5c.drv' failed Aloha, RK. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] reply-to setting in mailman
Hi, could list administrators change mailman settings so that reply-to field is set to maillist address, not the author's one? Thank you ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] python3.4-bedup-20140206 doesn't build
Raahul Kumar raahul.ku...@gmail.com writes: Hi guys, I tried to get bedup running, refuses to build. Any idea what's wrong with this package? Yes, I copied the private github url and used nix-prefetch-git locally. Should be fixed now. exporting g...@github.com:g2p/bedup.git (rev 80cb217d4819a03e159e42850a9a3f14e2b278a3) into /nix/store/j3bz1nhqxgpq5f11v7qbpzr02pnp0liy-git-export Initialized empty Git repository in /nix/store/j3bz1nhqxgpq5f11v7qbpzr02pnp0liy-git-export/.git/ error: cannot run ssh: No such file or directory fatal: unable to fork error: cannot run ssh: No such file or directory fatal: unable to fork Unable to checkout 80cb217d4819a03e159e42850a9a3f14e2b278a3 from g...@github.com:g2p/bedup.git. builder for `/nix/store/4sihkx15ygp5n42ykms46l7b15qd0k9s-git-export.drv' failed with exit code 1 cannot build derivation `/nix/store/2d4pk9rfji9iml59s0xkhhga43cqzy3x-python3.4-bedup-20140206.drv': 1 dependencies couldn't be built cannot build derivation `/nix/store/9dhy1wq67g32cv99ap120ncicddsb5xa-system-path.drv': 1 dependencies couldn't be built cannot build derivation `/nix/store/m5vbabdv4lawsb1jl7mjqclm6wznyli2-nixos-14.04pre42122.e572b5c.drv': 1 dependencies couldn't be built error: build of `/nix/store/m5vbabdv4lawsb1jl7mjqclm6wznyli2-nixos-14.04pre42122.e572b5c.drv' failed Aloha, RK. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] npm2nix maintainership
Excerpts from Shea Levy's message of Thu Apr 17 02:16:24 + 2014: I wrote npm2nix, but I'm no longer doing any work with node stuff and would prefer to hand it off to someone who is using it and motivated to keep it up-to-date and working. Is there anyone who might want to take ownership of the project? If you don't find anybody document current state on the wiki. Then it'll be found easily again by people who want to use it. Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] python3.4-bedup-20140206 doesn't build
Still getting the same error messages. Has it been pushed to nixos unstable channel yet? Initialized empty Git repository in /nix/store/j3bz1nhqxgpq5f11v7qbpzr02pnp0liy-git-export/.git/ error: cannot run ssh: No such file or directory fatal: unable to fork error: cannot run ssh: No such file or directory fatal: unable to fork Unable to checkout 80cb217d4819a03e159e42850a9a3f14e2b278a3 from g...@github.com:g2p/bedup.git. builder for `/nix/store/4sihkx15ygp5n42ykms46l7b15qd0k9s-git-export.drv' failed with exit code 1 Aloha, RK. On Thu, Apr 17, 2014 at 5:21 PM, Mathijs Kwik math...@bluescreen303.nlwrote: Raahul Kumar raahul.ku...@gmail.com writes: Hi guys, I tried to get bedup running, refuses to build. Any idea what's wrong with this package? Yes, I copied the private github url and used nix-prefetch-git locally. Should be fixed now. exporting g...@github.com:g2p/bedup.git (rev 80cb217d4819a03e159e42850a9a3f14e2b278a3) into /nix/store/j3bz1nhqxgpq5f11v7qbpzr02pnp0liy-git-export Initialized empty Git repository in /nix/store/j3bz1nhqxgpq5f11v7qbpzr02pnp0liy-git-export/.git/ error: cannot run ssh: No such file or directory fatal: unable to fork error: cannot run ssh: No such file or directory fatal: unable to fork Unable to checkout 80cb217d4819a03e159e42850a9a3f14e2b278a3 from g...@github.com:g2p/bedup.git. builder for `/nix/store/4sihkx15ygp5n42ykms46l7b15qd0k9s-git-export.drv' failed with exit code 1 cannot build derivation `/nix/store/2d4pk9rfji9iml59s0xkhhga43cqzy3x-python3.4-bedup-20140206.drv': 1 dependencies couldn't be built cannot build derivation `/nix/store/9dhy1wq67g32cv99ap120ncicddsb5xa-system-path.drv': 1 dependencies couldn't be built cannot build derivation `/nix/store/m5vbabdv4lawsb1jl7mjqclm6wznyli2-nixos-14.04pre42122.e572b5c.drv': 1 dependencies couldn't be built error: build of `/nix/store/m5vbabdv4lawsb1jl7mjqclm6wznyli2-nixos-14.04pre42122.e572b5c.drv' failed Aloha, RK. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] npm2nix maintainership
Hi, I'm still using Node.js at the moment, mostly for internal projects of the company I'm currently working for. If nobody else is planning to take maintainership, then I'm probably the best person to do it, since I'm still regularly using npm2nix and it's actually quite useful for us. And of course NiJS depends on Node.js, hahaha!! (sorry, I promise not to make jokes about it again!) Best, Sander From: nix-dev-boun...@lists.science.uu.nl [nix-dev-boun...@lists.science.uu.nl] on behalf of Marc Weber [marco-owe...@gmx.de] Sent: Thursday, April 17, 2014 11:15 AM To: nix-dev Subject: Re: [Nix-dev] npm2nix maintainership Excerpts from Shea Levy's message of Thu Apr 17 02:16:24 + 2014: I wrote npm2nix, but I'm no longer doing any work with node stuff and would prefer to hand it off to someone who is using it and motivated to keep it up-to-date and working. Is there anyone who might want to take ownership of the project? If you don't find anybody document current state on the wiki. Then it'll be found easily again by people who want to use it. Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] npm2nix maintainership
Quoting Sander van der Burg - EWI (2014-04-17 12:39:38) Hi, I'm still using Node.js at the moment, mostly for internal projects of the company I'm currently working for. If nobody else is planning to take maintainership, then I'm probably the best person to do it, since I'm still regularly using npm2nix and it's actually quite useful for us. And of course NiJS depends on Node.js, hahaha!! (sorry, I promise not to make jokes about it again!) Best, i'm also using it quite a lot in current projects, but mostly for getting the tools for frontend development. i'm not doing (at the moment) a lot of node work. if nothing else i can help sander mantain it. -- Rok Garbas - http://www.garbas.si ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] npm2nix maintainership
Ah, if you're willing to that'd be great! Let me know if you're sure you want to and we can figure out the logistics of it all. On Thu, Apr 17, 2014 at 11:39:38AM +, Sander van der Burg - EWI wrote: Hi, I'm still using Node.js at the moment, mostly for internal projects of the company I'm currently working for. If nobody else is planning to take maintainership, then I'm probably the best person to do it, since I'm still regularly using npm2nix and it's actually quite useful for us. And of course NiJS depends on Node.js, hahaha!! (sorry, I promise not to make jokes about it again!) Best, Sander From: nix-dev-boun...@lists.science.uu.nl [nix-dev-boun...@lists.science.uu.nl] on behalf of Marc Weber [marco-owe...@gmx.de] Sent: Thursday, April 17, 2014 11:15 AM To: nix-dev Subject: Re: [Nix-dev] npm2nix maintainership Excerpts from Shea Levy's message of Thu Apr 17 02:16:24 + 2014: I wrote npm2nix, but I'm no longer doing any work with node stuff and would prefer to hand it off to someone who is using it and motivated to keep it up-to-date and working. Is there anyone who might want to take ownership of the project? If you don't find anybody document current state on the wiki. Then it'll be found easily again by people who want to use it. Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] npm2nix maintainership
Perhaps we should move the repo to the NixOS organisation at github? Cheers, Rob On Thu, Apr 17, 2014 at 2:56 PM, Shea Levy s...@shealevy.com wrote: Ah, if you're willing to that'd be great! Let me know if you're sure you want to and we can figure out the logistics of it all. On Thu, Apr 17, 2014 at 11:39:38AM +, Sander van der Burg - EWI wrote: Hi, I'm still using Node.js at the moment, mostly for internal projects of the company I'm currently working for. If nobody else is planning to take maintainership, then I'm probably the best person to do it, since I'm still regularly using npm2nix and it's actually quite useful for us. And of course NiJS depends on Node.js, hahaha!! (sorry, I promise not to make jokes about it again!) Best, Sander From: nix-dev-boun...@lists.science.uu.nl [ nix-dev-boun...@lists.science.uu.nl] on behalf of Marc Weber [ marco-owe...@gmx.de] Sent: Thursday, April 17, 2014 11:15 AM To: nix-dev Subject: Re: [Nix-dev] npm2nix maintainership Excerpts from Shea Levy's message of Thu Apr 17 02:16:24 + 2014: I wrote npm2nix, but I'm no longer doing any work with node stuff and would prefer to hand it off to someone who is using it and motivated to keep it up-to-date and working. Is there anyone who might want to take ownership of the project? If you don't find anybody document current state on the wiki. Then it'll be found easily again by people who want to use it. Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Rob Vermaas [email] rob.verm...@gmail.com ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] npm2nix maintainership
Ah that's a good idea. We'll still need someone to run the npm publish for new versions as well. On Thu, Apr 17, 2014 at 03:59:44PM +0200, Rob Vermaas wrote: Perhaps we should move the repo to the NixOS organisation at github? Cheers, Rob On Thu, Apr 17, 2014 at 2:56 PM, Shea Levy s...@shealevy.com wrote: Ah, if you're willing to that'd be great! Let me know if you're sure you want to and we can figure out the logistics of it all. On Thu, Apr 17, 2014 at 11:39:38AM +, Sander van der Burg - EWI wrote: Hi, I'm still using Node.js at the moment, mostly for internal projects of the company I'm currently working for. If nobody else is planning to take maintainership, then I'm probably the best person to do it, since I'm still regularly using npm2nix and it's actually quite useful for us. And of course NiJS depends on Node.js, hahaha!! (sorry, I promise not to make jokes about it again!) Best, Sander From: nix-dev-boun...@lists.science.uu.nl [ nix-dev-boun...@lists.science.uu.nl] on behalf of Marc Weber [ marco-owe...@gmx.de] Sent: Thursday, April 17, 2014 11:15 AM To: nix-dev Subject: Re: [Nix-dev] npm2nix maintainership Excerpts from Shea Levy's message of Thu Apr 17 02:16:24 + 2014: I wrote npm2nix, but I'm no longer doing any work with node stuff and would prefer to hand it off to someone who is using it and motivated to keep it up-to-date and working. Is there anyone who might want to take ownership of the project? If you don't find anybody document current state on the wiki. Then it'll be found easily again by people who want to use it. Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Rob Vermaas [email] rob.verm...@gmail.com ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] npm2nix maintainership
Oh wait, it's a mercurial repo, that won't work :) Cheers, Rob On Thu, Apr 17, 2014 at 4:09 PM, Shea Levy s...@shealevy.com wrote: Ah that's a good idea. We'll still need someone to run the npm publish for new versions as well. On Thu, Apr 17, 2014 at 03:59:44PM +0200, Rob Vermaas wrote: Perhaps we should move the repo to the NixOS organisation at github? Cheers, Rob On Thu, Apr 17, 2014 at 2:56 PM, Shea Levy s...@shealevy.com wrote: Ah, if you're willing to that'd be great! Let me know if you're sure you want to and we can figure out the logistics of it all. On Thu, Apr 17, 2014 at 11:39:38AM +, Sander van der Burg - EWI wrote: Hi, I'm still using Node.js at the moment, mostly for internal projects of the company I'm currently working for. If nobody else is planning to take maintainership, then I'm probably the best person to do it, since I'm still regularly using npm2nix and it's actually quite useful for us. And of course NiJS depends on Node.js, hahaha!! (sorry, I promise not to make jokes about it again!) Best, Sander From: nix-dev-boun...@lists.science.uu.nl [ nix-dev-boun...@lists.science.uu.nl] on behalf of Marc Weber [ marco-owe...@gmx.de] Sent: Thursday, April 17, 2014 11:15 AM To: nix-dev Subject: Re: [Nix-dev] npm2nix maintainership Excerpts from Shea Levy's message of Thu Apr 17 02:16:24 + 2014: I wrote npm2nix, but I'm no longer doing any work with node stuff and would prefer to hand it off to someone who is using it and motivated to keep it up-to-date and working. Is there anyone who might want to take ownership of the project? If you don't find anybody document current state on the wiki. Then it'll be found easily again by people who want to use it. Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Rob Vermaas [email] rob.verm...@gmail.com -- Rob Vermaas [email] rob.verm...@gmail.com ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] impureEnvVars, the second
Hi All sorry to bother you again regarding impureEnvVars. I still can't get my fetchdarcs over ssh to work, even though I am now using constant-output derivations and have impureEnvVars = [ SSH_AGENT_PID SSH_AUTH_SOCK ]; in my fetchdarcs/default.nix. The environment variables are now defined in the builder. However, they are empty :( Could this be because I am using the Nix multi-user setup where building is delegated to a number of nixbld users? Is impureEnvVars supposed to work in this setting? If not, what can I do to make it work? If yes, then I probably made a mistake when setting up the nix build users. (I am using Nix-1.7.) Cheers Ben -- Make it so they have to reboot after every typo. -- Scott Adams ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] npm2nix maintainership
Excerpts from Rob Vermaas's message of Thu Apr 17 14:14:22 + 2014: Oh wait, it's a mercurial repo, that won't work :) Why not turn it into git? Marc Weber ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] impureEnvVars, the second
Hi, On 17/04/14 17:04, Ben Franksen wrote: sorry to bother you again regarding impureEnvVars. I still can't get my fetchdarcs over ssh to work, even though I am now using constant-output derivations and have impureEnvVars = [ SSH_AGENT_PID SSH_AUTH_SOCK ]; in my fetchdarcs/default.nix. The environment variables are now defined in the builder. However, they are empty :( Could this be because I am using the Nix multi-user setup where building is delegated to a number of nixbld users? Right, environment variables from the client are not passed to the builder. Even if they were, the builder probably would not have file system access to the socket identifier by $SSH_AUTH_SOCK. -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] impureEnvVars, the second
Eelco Dolstra wrote: On 17/04/14 17:04, Ben Franksen wrote: sorry to bother you again regarding impureEnvVars. I still can't get my fetchdarcs over ssh to work, even though I am now using constant-output derivations and have impureEnvVars = [ SSH_AGENT_PID SSH_AUTH_SOCK ]; in my fetchdarcs/default.nix. The environment variables are now defined in the builder. However, they are empty :( Could this be because I am using the Nix multi-user setup where building is delegated to a number of nixbld users? Right, environment variables from the client are not passed to the builder. Even if they were, the builder probably would not have file system access to the socket identifier by $SSH_AUTH_SOCK. The latter could, I guess, be worked-around (using build-chroot-dirs) but the former seems... hopeless :( I wonder what other options I have to achieve my goal. ATM I can see two: (1) Make the repositories available via http. That means I'll have to convince the sysadmin to set up a web server on the repo server and let it offer the directory that contains our repos. Or I can setup the web werver on another machine that can NFS mount the repo directory; yes, that sounds more practical ;-) (2) Use my self-written nix-prefetch-darcs. That works because it does not delegate the downloading to a nixbld user. The problem is that this breaks automatic dependency resolution during nix-build, if the source derivation is not yet in the Nix store. Developers will have to use nix-prefetch-darcs at least once for every new dependency an application acquires. I could modify the source derivations to display a message to users like Builder cannot proceed: please call nix-prefetch-darcs user@host:path tag from the command line and try again. where the placeholders user, host, path and tag are automatically filled in by the builder, so the user can cut and paste this line into their shell. The main question with regard to (2) is: how do I prevent the source derivations from being garbage collected (for instance in case the final build did not succeed and no result link gets created) so that users at least have to do this only once for each dependency? Cheers Ben -- Make it so they have to reboot after every typo. -- Scott Adams ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] impureEnvVars, the second
On Thu, Apr 17, 2014 at 06:13:35PM +0200, Ben Franksen wrote: Eelco Dolstra wrote: On 17/04/14 17:04, Ben Franksen wrote: sorry to bother you again regarding impureEnvVars. I still can't get my fetchdarcs over ssh to work, even though I am now using constant-output derivations and have impureEnvVars = [ SSH_AGENT_PID SSH_AUTH_SOCK ]; in my fetchdarcs/default.nix. The environment variables are now defined in the builder. However, they are empty :( Could this be because I am using the Nix multi-user setup where building is delegated to a number of nixbld users? Right, environment variables from the client are not passed to the builder. Even if they were, the builder probably would not have file system access to the socket identifier by $SSH_AUTH_SOCK. The latter could, I guess, be worked-around (using build-chroot-dirs) Actually, fixed-output derivations are done outside of the chroot, so you just need to ensure the socket is accessible to the build users group. In fact, *not* having it in the chroot is better so that non-fixed-output builds don't have access. but the former seems... hopeless :( Why? Just start the daemon with the right environment settings. I wonder what other options I have to achieve my goal. ATM I can see two: (1) Make the repositories available via http. That means I'll have to convince the sysadmin to set up a web server on the repo server and let it offer the directory that contains our repos. Or I can setup the web werver on another machine that can NFS mount the repo directory; yes, that sounds more practical ;-) (2) Use my self-written nix-prefetch-darcs. That works because it does not delegate the downloading to a nixbld user. The problem is that this breaks automatic dependency resolution during nix-build, if the source derivation is not yet in the Nix store. Developers will have to use nix-prefetch-darcs at least once for every new dependency an application acquires. I could modify the source derivations to display a message to users like Builder cannot proceed: please call nix-prefetch-darcs user@host:path tag from the command line and try again. where the placeholders user, host, path and tag are automatically filled in by the builder, so the user can cut and paste this line into their shell. The main question with regard to (2) is: how do I prevent the source derivations from being garbage collected (for instance in case the final build did not succeed and no result link gets created) so that users at least have to do this only once for each dependency? Cheers Ben -- Make it so they have to reboot after every typo. -- Scott Adams ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] impureEnvVars, the second
Shea Levy wrote: On Thu, Apr 17, 2014 at 06:13:35PM +0200, Ben Franksen wrote: Eelco Dolstra wrote: On 17/04/14 17:04, Ben Franksen wrote: sorry to bother you again regarding impureEnvVars. I still can't get my fetchdarcs over ssh to work, even though I am now using constant-output derivations and have impureEnvVars = [ SSH_AGENT_PID SSH_AUTH_SOCK ]; in my fetchdarcs/default.nix. The environment variables are now defined in the builder. However, they are empty :( Could this be because I am using the Nix multi-user setup where building is delegated to a number of nixbld users? Right, environment variables from the client are not passed to the builder. Even if they were, the builder probably would not have file system access to the socket identifier by $SSH_AUTH_SOCK. The latter could, I guess, be worked-around (using build-chroot-dirs) Actually, fixed-output derivations are done outside of the chroot, so you just need to ensure the socket is accessible to the build users group. In fact, *not* having it in the chroot is better so that non-fixed-output builds don't have access. but the former seems... hopeless :( Why? Just start the daemon with the right environment settings. Well, those would have to be static, as the daemon is not started separately by each user. But the environment variables are created dynamically when the ssh agent is started. But: what you said here gave me an idea for a much simpler solution: I don't have to rely on the developer's credentials at all. Instead I'll give the Nix build users their own ssh identity (key pair) w/o passphrase. Then add their public key to the repouser@reposerver's .ssh/authorized_keys. No impureEnvVars needed, since the build users don't need to connect to an ssh agent. I hope that Nix build users not having a home directory is only a recommendation, not a requirement for the multi-user setup to work. Cheers Ben -- Make it so they have to reboot after every typo. -- Scott Adams ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] impureEnvVars, the second
Ben Franksen wrote: Shea Levy wrote: On Thu, Apr 17, 2014 at 06:13:35PM +0200, Ben Franksen wrote: Eelco Dolstra wrote: On 17/04/14 17:04, Ben Franksen wrote: sorry to bother you again regarding impureEnvVars. I still can't get my fetchdarcs over ssh to work, even though I am now using constant-output derivations and have impureEnvVars = [ SSH_AGENT_PID SSH_AUTH_SOCK ]; in my fetchdarcs/default.nix. The environment variables are now defined in the builder. However, they are empty :( Could this be because I am using the Nix multi-user setup where building is delegated to a number of nixbld users? Right, environment variables from the client are not passed to the builder. Even if they were, the builder probably would not have file system access to the socket identifier by $SSH_AUTH_SOCK. The latter could, I guess, be worked-around (using build-chroot-dirs) Actually, fixed-output derivations are done outside of the chroot, so you just need to ensure the socket is accessible to the build users group. In fact, *not* having it in the chroot is better so that non-fixed-output builds don't have access. but the former seems... hopeless :( Why? Just start the daemon with the right environment settings. Well, those would have to be static, as the daemon is not started separately by each user. But the environment variables are created dynamically when the ssh agent is started. But: what you said here gave me an idea for a much simpler solution: I don't have to rely on the developer's credentials at all. Instead I'll give the Nix build users their own ssh identity (key pair) w/o passphrase. Then add their public key to the repouser@reposerver's .ssh/authorized_keys. No impureEnvVars needed, since the build users don't need to connect to an ssh agent. I hope that Nix build users not having a home directory is only a recommendation, not a requirement for the multi-user setup to work. Just wanted to report that this approach finally worked! Yay! (BTW, this is possible only because fixed-output derivations are built outside the chroot, else ssh could not access the identity file in the build user's home.) Cheers thanks again Ben -- Make it so they have to reboot after every typo. -- Scott Adams ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Problems installing NixOS with btrfs from a USB stick
Well I think to workaround it, a call to ln -s needs to be added here: https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/installer/cd-dvd/iso-image.nix#L213 I just can't remember right now what the symlink has to be... When I get some time (and someone else doesn't beat me to it) I'll try to reproduce. Of course the real issue is that mkfs.btrfs gets confused while trying to find the root fs and should be fixed. Adding a symlink is an easier fix though ;-) Cheers, Wout. On Wed, Apr 16, 2014 at 9:31 AM, Lluís Batlle i Rossell vi...@viric.namewrote: On Wed, Apr 16, 2014 at 07:09:32AM +0200, Wout Mertens wrote: Actually, I wasn't being clear, I only fixed it for me :-) I remember going through this too, two years ago. At some point I reported that upstream, and as I didn't install anything else, I hoped someone fixed it. On Apr 16, 2014 3:11 AM, Thomas Strobel ts...@cam.ac.uk wrote: Thank you very much for looking into it and fixing it so quickly! On Tue, 2014-04-15 at 08:52 +0200, Wout Mertens wrote: I fixed it by stracing mkfs. btrfs and creating a symlink to /. Basically it gets confused by the bind mounts and looks for root at the original location. So just strace -eopen mkfs... and look for enoent. On phone, sorry for lack of details. On Apr 13, 2014 12:41 PM, Alexei Robyn sha...@shados.net wrote: Hello, If you're talking about the can't determine mount status of /dev/... issue, this is a bug with mkfs.btrfs. See http://lists.science.uu.nl/pipermail/nix-dev/2012-December/010237.html - Alexei On Sun, Apr 13, 2014, at 07:49 PM, Cillian de Róiste wrote: Hi! On Sun, Apr 13, 2014 at 11:05 AM, Thomas Strobel ts...@cam.ac.uk wrote: Hi there, I was running into problems when trying to install NixOS with btrfs from a USB stick. I downloaded the current .iso and used unetbootin to create a bootable USB drive from it. Unfortunately, the resulting installation environment did not allow to use mkfs.btrfs as it could not decide on the mounting status of my partition. It seemed as if unetbootin prepared the system in a way that prevented mkfs.btrfs from working. Did anyone else experience that problem? If so, then my question is if the .iso files could be changed in a way that allows to prepare the USB stick with a simple dd-command, e.g. like Debian or GRML ISOs do, and that keeps mkft.btrfs working? You could try installing syslinux and using isohybrid to create a hybrid bootable image which you can dd onto a USB stick: isohybrid filename.iso http://www.syslinux.org/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE I'm not sure if that will help with the btrfs issue, but it would be good to know if it worked. Good luck! Cillian ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
