<refpga>Hi, is the certbot service supposed to show up using "# herd status"? I configured it as per the guix services docs, and reconfigured system to /etc/config.scm without any errors, still herd doesn't show any service named certbot.
<wazamflaw>hello, can anyone recommend the the way to install on Guix System packages that are not yet in the guix archives? as in installing them from a tarball
<wazamflaw>for example, the rust language server package: rls
<wazamflaw>preferably in such a way that the packages could be easily uninstalled should they be added to the archives
<wazamflaw>i believe that `guix environment` could be of use in this situation?
<vagrantc>phase `check' succeeded after 2063.4 seconds ... if you skip the tests the whole package build takes 30-45 seconds
<samplet`>refpga: IIRC, the certbot service is mostly just a cron job with an NGINX configuration extension, so it makes sense that it would’t show up with “herd status”.
<leungbk>I submitted some commits directly and would like to shut down the associated patch threads that I created a couple weeks ago via email. How can I do this?
<BenKey76>The following is from near the end of the Binary Installation document.Source etc/profile to augment PATH and other relevant environment variables:# GUIX_PROFILE="`echo ~root`/.config/guix/current" ; \ source $GUIX_PROFILE/etc/profileThis is unclear. It sets environment variables for that single session and for that single user. The document says
<BenKey76>nothing about setting the necessary environment variables for future sessions.
<BenKey76>The next few sections of the manual speak of building and installing from source. Then at the beginnig of the Application Setup section, the following can be found.Packages installed via Guix will not use the locale data of the host system. Instead, you must first install one of the locale packages available with Guix and then define the
<BenKey76>GUIX_LOCPATH environment variable:$ guix install glibc-locales$ export GUIX_LOCPATH=$HOME/.guix-profile/lib/locale1. How is $HOME/.guix-profile created for user B?2. And again this sets a variable for a single session.
<demotri>civodul: Thanks, that was what I thought could work.
<demotri>civodul: Last question: Is llvm-6 an input, or native-input? Thought it is just the compiler (i.e. native), but "guix gc --references /gnu/store/...freecad..." has the llvm-toolchain-6 as reference. Or is that just because of the clang-6 package?
*demotri got right now a broken plastics part on the desktop, so it's really time to push that patch :-)
<apteryx>is there a reason we should keep python-minimal to 3.5, or can it be version bumped to something recent (on core-updates-next)
<refpga>roptat:Sorry for the late reply. I've already configured the service as per the guix docs on certbot. But it mentions that certbot will run at random minute in an hour per day. I don't know when I would get the certificates, I wish there was a way to force it to generate them the first time immediately. Anyway, I have generated certs using the commandline (sudo certbot certonly), but need to renew them using the service still.
<civodul>demotri: i'm not sure, i guess you can make it "inputs"
<gnu_srs1>Hello again: unpacking bootstrap Guile to '/gnu/store/vi66s7rcx853cwwddbhnccsppppi8x01-guile-bootstrap-2.0'... ./bin/guile: Empty file!!
<gnu_srs1>cat /gnu/store/...-build-bootstrap-guile.sh: echo "unpacking bootstrap Guile to '$out'..."; ... /gnu/store/yaxqsba39qdlyv3wrz04i3705l0l0kyp-xz -dc < $GUILE_TARBALL | /gnu/store/z8zria3rlr8p24kx4gk6wwlmfpyp4lhv-tar xv; extracts stuff but fails here: $out/bin/guile --version since that file is empty??
<apteryx>civodul: OK, I just read that core-updates-next was meant to be core-updates-tmp ;-)
<civodul>yeah, so we should remove it but there's a couple of commits there :-/
<apteryx>anyway, my suggestion to branch off core-updates to stabilize it still makes sense I think; it removes the chance that someone pushes a big changes there by mistake while it's being prepped for a merge to master
<apteryx>and it leaves core-updates open to buziness
<roptat>you should install them with guix, then point the variables to their location in your profile
<roptat>when they are installed, they will be in a known location in your profile, namely etc/ssl
<roptat>so for the root user, /root/.guix-profile/etc/ssl
<demotri>Parra: You can also download the QEMU image from the homepage, if that helps.
<roptat>I think they are already installed in the binary tarball, so you only have to make the variables point to the profile (/root/.guix-profile might not exist, so /var/guix/profiles/per-user/root/guix-profile/etc/ssl)
<bgardner>Good morning guix! I installed Guix System on a rack server with a default ssh configuration and it failed to start on the last reboot. No error, nothing in the logs, just a herd status of "enabled, not running, will respawn". Any suggestions on where I should start looking to find more information? herd start ssh-daemon brought it right up, so I'm puzzled.
<jlicht>bgardner: perhaps something to do with your networking? I know I've had some issues with that a long time ago, where I basically had to start ssh-daemon myself afterwards. I only had this problem once though
<bgardner>nckx: I'm making no progress on disabling IPv6, are you aware of any documentation that I'm missing?
<nckx>bgardner: All I know of is that bug report. I haven't fixed my own system yet.
<bgardner>nckx: Gotcha. Looks like the static-networking-service code doesn't allow for 'disable', so I might be stuck. I'll bookmark the bug report and try to supply any clues I stumble upon. Thanks again.
<civodul>but yeah, i think it's the right place for GWL questions
***OriansJ` is now known as OriansJ
<jlicht>well, yes that too, but I actually mean something that gives me "Hello, World!" output
<jlicht>The current website explains (in a super nice way, by the way) how to make files that describe processes and workflows etc, but not how to actually run them. The naive approach of `guix workflow -r <myfile>' does not seem to do the trick
<jlicht>I simply did `guix install gwl', as I had hoped that would be enough to start playing around. Incidentally, it seems that gwl has guix as a propagated input: I had thought this leads to some hard-to-debug issues?
<civodul>jlicht: yeah, well not that terrible, but it's suboptimal
<civodul>but it may be that the "gwl" package is a bit old, no?
<civodul>i think rekado & roelj made quite a few changes lately
<jlicht>Some time ago I updated biber to 2.12, which works quite well, but it seems our current biblatex packages are compatiable with biber < 2.12. Would it make sense to push a downgrade to biber, or should I rather wait until the next round of texlive updates?
<civodul>rekado_ would know better, but i'd say that if the current biber is unusable in practice, it's probably a good idea to downgrade it
<civodul>according to the principle that something that works is better than something that doesn't :-)