<snape>Oh I talked to mange but it was you thorwil who had the issue, sorry
<thorwil>i certainly don't mind, if people discuss my issue! ;)
<thorwil>if init fails after doing much of the work, should the command be reused, or should one switch to reconfigure?
<snape>thorwil: I think you needs to use init, because reconfigure doesn't know about your system being in /mnt. Unless you do it in a chroot? I have no idea, really, I've done this once, long time ago :-)
<snape>if it's just the bootloader install phase that failed, it's probably safe to consider that the installation is an overall success
<snape>Assuming you have a bootloader installed somewhere else, that is able to read grub.cfg of course
<snape>(you should check that /boot/grub/grub.cfg has been generated)
<thorwil>yes, i already was at the point of having a grub in the store, but no grub.cfg, since i did use --no-bootloader. to only then notice that it's useless that way :}
<pmikkelsen>hi guix, I have a question that may be a bit strange. Would it make sense to have a package definition which builds a static website using one of the many static site generators, and then use the output directy in a nginx service configuration? This way, I think it would be possible to update the package definition, run 'guix system reconfigure ...' and then the new website will be used. Just an idea I had, but I would like your view on
<rekado>pmikkelsen: yes, this would work. It may be a little heavy-handed to update the package definition each time, but it coudl be okay for sites that don’t change too often.
<pmikkelsen>rekado: okay, I guess I will have to package the software I use first then
<mange>At the moment it won't work, though, because I don't think reloading nginx config works using reconfigure. I was just reading some issues earlier, where nginx hardcodes its config and reconfigure doesn't touch running services, so it would take reboot to update.
<mange>You could do it by writing a system service that puts your package/website contents into a predefined folder that nginx reads from, but at that point you might as well just put it there yourself.
<pmikkelsen>What I have now is that I put it there myself via rsync from my laptop which works OK
<thomassgn>hmm, geiser complains about "possibly unbound variables cppunit-1.14" and xmlsec-nss. And then when I try to build the definition it gives me "ERROR: xmlsec-nss: unbound variable" despite xml module being included/used... How to get around it?
<thomassgn>explicitly running (use-modules (gnu packages xml)) in geiser does not help
<snape>resh: cd is built into the shell, you can't use sudo with it
<bavier`>resh: `su -` will switch to the root user
<snape>"as root" is unclear, it actually means that you need to switch to the root user because "sudo" doesn't work
<thomassgn>snape: allright, didn't work though. I get the same errors from both restarting geiser and evaluating and evaluating the variables and use-module exp. xmlsec-nss is in xml.scm - don't see how or what is causing this one to fail as there's plenty of other variables/packages from modules with different names.
<snape>thomassgn: did you try C-M-x within xmlsec-nss>?
<resh>ohh so I should not use su- and sudo before.
<roptat>but you can get the value by using (package-<field-name> libreoffice)
<resh>roptat and rekado not inside any directory ... installed without cd to any directory
<rekado>resh: so it might still be in your home directory then.
<thomassgn>So if I just want to add something I have to copy the contents of the inherited field into the new def.? uh, sorry, what did you mean with (package-<field-name> libreoffice)? I ould just go read the docs ofc.
<vagrantc>efraim: also have some wandboard/cubox-i/hummingboard variants i might be able to test
<g_bor>rekado: I've checked your message related to jeromq.
<g_bor>There are two possibilities, as the whole testsuite is being refactored. Either we go with this big patch, and we can drop that on release, or we can downgrade from 0.4.3 to 0.4.2, where we don't need the patch , and wit for the release WDYT?
<civodul>rekado: 2018-03-07T22:35:13 spec 'python-updates': fetched commit "accec9d67f78b5dab88eb815d17e92365b9d9ce4" (stamp was "")
<civodul>it seems that it's still evaluating the branch
<civodul>rekado: i just pushed the package/inherit thing for glibc-final
<axg>So, I'm trying to install java, and while there is many packages that come up, nothing looks like openjdk or openjre in any way. Who is using java successfully and what package did you grab to get the javac and java?
<civodul>mbakke: do you think we're ready to merge 'staging'?
<mbakke>civodul: not sure, we're still lacking many substitutes (evolution-data-server). There's also been a lot of activity on master, so IMO we should merge and do another eval first.
<mbakke>Me neither and "afk" atm. I don't expect any problems, so it should be safe to merge. But would like to test GNOME first.
<mbakke>I can merge and start a Hydra evaluation in a few hours if Hydra isn't too busy.
<mbakke>But feel free to merge if the weather is good ;)
<civodul>ok, i guess i should take a closer look first :-)
<rekado>civodul: thanks for taking care of the glibc graft!
<rekado>civodul: re cuirass on berlin: yeah, it’s finally doing something. I restarted it after about an hour.
<civodul>that shouldn't have been necessary, but maybe it went amiss
<jackhill>I'm looking at the postgresql package and would like a postgres build with SSL and gssapi support. How are optional features usually handled? Would it be okay to submit a patch that added those to the existing package, or something else so not to increase the current closure size?
<civodul>that doesn't seem related to proot though, does it?
<bavier`>maybe not, I was missing the '-0' flag...
<bavier`>ok, now I get "guix package: error: build failed: cloning builder process: Operation not permitted"
<bavier`>that's definitely a problem, probably my kernel is too old
<bavier`>what's the version that's needed for NEWNS?
<rekado>jackhill: it depends on how common this feature is and how much larger it makes the package closure. In some cases it may be good to add a “-minimal” variant for use with other packages and a regular variant for installation.
<bavier`>oh, 2.6-ish, my kernel has all those then, maybe processes cannot clone inside proot?
<civodul>bavier`: i think we had EPERM in containers too, but i can't remember why