<handheldCar>"The root-owned /etc/nix-setuid.conf file is read by nix-setuid-helper; it should contain exactly two words: the user name under which the authorized guix-daemon runs, and the name of the build users group." <mark_weaver>I've never used that mode of operation, but presumably if you want to do it that way, you need to create that file. <mark_weaver>and presumably you'd also need to make the 'nix-setuid-helper' setuid root. <handheldCar>should this have an ampersand @ the end (run in background): # guix-daemon --build-users-group=guix-builder <mark_weaver>it depends on your preference. it does produce output occasionally, so I usually run it in the foreground on a dedicated terminal, but it's up to you :) <civodul>viric: filegive doesn't work behind the corporate firewall <viric>civodul: if you have a remote ssh server under your control, you can use it as a 'bridge' <viric>whether you can traverse the firewall or not, it is up to your firewall maintainers :) <viric>filegive doesn't use any 'trick'. Fair network! <viric>for the ssh, you need a special sshd_config option which is silly disabled by default. <viric>does it? sure? great, if so :) <viric># Using a third computer through ssh as a forwarder <viric># It requires the special "GatewayPorts clientspecified", in sshd_config <viric>civodul: if you can't ask any port redirection or upnp to your firewall admins, and you don't have any sshd under your control in a public address, you are a bit doomed. you are in a situation where you have to use '3rd party services' <civodul>well i could also install filegive on a machine i have access to, even if i'm not root there, right? <youlysses>So I did a clean install of Guix and I'm no-longer having an issue installing cmake -- that being said, something seems to of gone astray loading gl.scm, when I was trying to fix it for the (hopefully) final patch, it now throws an "unknown package" at me again, for all expressions in the module. Here it is, if you want to look for something, I might have over-looked. :^P http://paste.lisp.org/+2ZFU <viric>civodul: maybe I should add suport for some kind of 'socat' too, to avoid the ssh root thing. Damn default option. <civodul>youlysses: you do remember how to fix the "unknown package" issue, right? :-) <youlysses>civodul: I mean, I ran it through ./pre-inst-env and it seems to load fine, if that's what you mean? <civodul>./pre-inst-env guile -c '(use-modules (gnu packages gl))' <civodul>youlysses: ./pre-inst-env guix build freeglut -n works for me <civodul>could it be that you have stale {opengl,freeglut,whatnot}.scm files around? <civodul>youlysses: also, the file is called gl.scm, right? <youlysses>civodul: I wouldn't think-so -- this is a new clone, and not the stable tarball I was working on prior, during the hackathon. And yeah, it's gl.scm -- as suggested. <civodul>so dunno, maybe you could strace ./pre-inst-env guix build freeglut, to check which gl.scm gets picked or somethign *youlysses has been considering just retorgrading back to NixOS from Fedora19, until the upstream GNU distro is a viable option -- I'd imagine that there would be less-of a chance, for a margin of error doing-so. :^P <viric>going to nixos, 'retrograde'? <youlysses>viric: Well as-in retracing steps prior, not from a techincal level, no. :^P <viric>you had nixos, and then updatedto fedora19? <viric>I simply find that step strange <youlysses>viric: At the time, I was still pretty heavily dependent on a DE and GNOME was by-far the most-usable -- I had came into contact with, so seeing that Fedora is more-or-less the primetime of GNOME in many regards, it made sense -- in such-a framing. Since then, as I've gotten down an dirty and have pretty much fully abandoned any want nor need for a such an environment, so the main selling point is now pretty-much irrelevant. :^P <youlysses>The thought-process then was more-so direct practicallity vs a technologically superior alternative, which usually I'm impulsive enough to throw everything out the window and go the road less traveled, to get there -- but I think the paranoia of having something due in a class, and something goes wrong and I wouldn't know how to fix it -- always kept me fairly far-off, but now, while certainly no expert, I think I have a solid <youlysses>foundational basis, in-general -- that would allow me to get over that hump (too and a live-image ready, just in case). :^) <youlysses>I really should at least try to get 3-4 hours of sleep tonight; I'll sleep on it, but there's a good 50/50 chance that I'll end-up on that side-of the fence by the end of today. <youlysses>Ok; I'll be back later -- peace people. o/ AFK. <civodul>youlysses: note that you can keep using Guix on whatever distro you choose underneath <civodul>note that NixOS includes non-free packages <viric>civodul: the best is the violin one, on that <Arne```>civodul: Git is too frustrating to use. <jxself>civodul: You have acess to SSH on a public address - Fencepost, if nothing else right? <jxself>It even accepts connections in port 443 in case your firewall blocks the usual port, but you have to use the fp-ssh.gnu.org name instead for that. <jxself>I've done that a few times to get around stupid network stuff at work. <civodul>jxself: yeah, i have access to a couple of machines such as fp, but i'm not root there <ArneBab_>civodul: I lost 15 minutes because I ran into a git-trapwire which I did not know yet… <ArneBab_>committing a file with an error, trying to amend and accidently committing some files and then not finding out within 15 minutes how to undo that. <viric>I fail to find anything about strtod_l <ArneBab_>civodul: does the updated patch work for you? <civodul>ArneBab_: i'll test tonight and report back <civodul>ArneBab_: you were able to build it locally, right? <ArneBab_>civodul: I still did not manage to recreate a working test environment ☹ <ArneBab_>civodul: and I do not understand why - even reinstalling and replacing version-control.scm did noot work <civodul>could you mail the details in the thread, maybe? ***civodul changes topic to 'GNU Guix --- http://gnu.org/s/guix/ --- 0.4 is out!'
<viric>civodul: I added the socat thing to filegive. Pick the trunk and test :) <foeniks>I was just trying to install guix-git with the arch linux' yaourt package manager <foeniks>so far building seemed to work, however a test fails <foeniks>this probably should fail, but my ISP kind of eager to guide me to its homepage <viric>yesterday there was such issue <Steap>foeniks: your ISP is a huge bastard <viric>your DNS server is misleading your system. It says that does.not exists. <foeniks>now this kind of is a problem, since the test fails and Yaourt won't install guix this way <Steap>foeniks: can you disable the test ? <foeniks>and this is Germany's main ISP, so there will be more people with that problem <Steap>foeniks: yes, French ISP also suck hard :) <foeniks>Steap, now that you name it, I probably can ;) <foeniks>just wanted mention the issue to the dev team ***zooko` is now known as zooko
<civodul>viric: you should make a Guix package for filegive (and a GCC-go package as well) :-) <viric>I'm still disabled in scheme! <viric>civodul: gccgo 4.7 has some problems; I wonder if 4.8 has enough fixes <viric>I guess iant has a limited dedication to it <viric>civodul: is there a guix package in nixpkgs? or maybe guix includes a nix expression to build it? <civodul>viric: yes Guix is in Nixpkgs, but i forgot to update it i think <viric>then you can run: nix-env -i guix -f . <viric>well, you, and I will also be able to run that. hehe *youlysses just decided on setting up a minimal vm via parabola. :^) <civodul>youlysses: it's safe to test Guix directly on your machine, rather than in a VM, FWIW <civodul>it won't interfere with your main distro <youlysses>civodul: Oh I know, I just still don't have a clue of what happened on my orginal install -- nor the time to really look into it, till next week. :^P <viric>civodul: I'll release 0.7.1 once you have checked socat for your setup <youlysses>So, this is more-or-less a practical solution -- that will let me finish testing the second version of the patch, before submission. <viric>civodul: do you use guix in the guruplug? how are its ram requirements? <youlysses>Yah, it really does build correctly! :^) Okay, I'm about to upload the second version of the patch in a-few then. <civodul>viric: the distro is Intel-only at the moment <viric>civodul: I read about building the bootstrap binaries <viric>it sounds great, of course. It should work though. hehe <viric>then, that's close to running guix in the guruplug, no? <civodul>i mean it works *on the supported platforms* :-) <civodul>cross-building the bootstrap tarballs works also <civodul>so the when porting the issues are mainly about platform-specific things, as noted in the "Porting" section <civodul>we're just doing our first port that way, to MIPS <alip2890>in gnu/packages/algebra.scm:106 the prefix of readline is retrieved, from inputs, which is a function argument. how can I get the input list in #:configure-flags? <alip2890>I guess I always have to alist-replace the configure phase? <youlysses>So -- is the first patch I submited really creating the package in guix's top-level directory... because from what I can see on it, it looks as-if it actually is compiling the expression to gnu/packages/...? <civodul>alip2890: there's the %build-inputs variable, which is a list of name/directory pairs <civodul>alip2890: why do you say you always have to replace the configure phase? <alip2890>I mean whenever I need prefixes in configure flags, but if there's %build-inputs there is no need <alip2890>I just saw the configure phase replaced several times in order to get prefixes, so I thought that's the way to go <civodul>the "normal" way is to do #:configure-flags (list (string-append "--with-foo=" (assoc-ref %build-inputs "foo")))