<sneek>leungbk, efraim says: looking forward to it! ludo's crate import fixes worked for me
<sneek>leungbk, rekado_ says: The CRAN importer retries imports from different repositories. If a package isn’t found on Bioconductor it will retry to import from CRAN. Same for imports from Git which are retried on Bioconductor (and then CRAN).
<bluekeys>Hi guix. I've just installed emacs-geiser. How do I load it?
<xavierm02[m]>I have a problem with pdflatex. I think it's running mktexfmt every time I compile my latex file, which takes a long time, and doesn't seem to be run by the pdflatex of my colleagues. Is this normal? How can I fix it? https://paste.debian.net/1098732/
<roptat>civodul, I forgot I answered to that thread ^^'
<roptat>it looks good to me, I can take care of pushing these patches this evening
<apteryx>is it possible to have geiser evaluate at the REPL only when my cursor is at the end of the line? I'd like if when my cursor if before a closing parenthesis, RET would give me a line break to nicely format statements rather than jump to eval. Paredit is kind of unusable with the Geiser REPL as it is
<apteryx>like, what how does Emacs handles indentation of packages, given that we use (put 'package 'scheme-indent-function 0) ? It seems the first level (package\n(first-level field is still indented normally (2 spaces) but that 2nd level + nested fields/expressions are indented at one space.
<apteryx>OK, when scheme-indent-function is set to an integer, the indentation code of Emacs in (lisp-mode.el) executes lisp-indent-specform
<nexgen2>Can you please help me with a few questions about GUIX compared to Debian
<nckx>civodul: No shame, it's your job. ;-) Re: our Russian friends: I can ping them through the LAN (when you ping them, you're just pinging my shitty residential router), but I can't SSH into them (‘Connection refused’) :-/ I'll have to hook up the USB TTY this evening to find out what's wrong. Surely ssh-daemon can't have crashed on both…
<nexgen2>Are all 100% of GUIX packages reproducible?
<nckx>Something like that is what I was referring to above, but somebody still needs to write it. You can test individual packages using ‘--check’, it's not far from that to automation & a pretty HTML report.
<nckx>Main blocker I see (apart from writing the code) is that you need double the CI capacity to provide up-to-date pretty stats.
<nckx>We're not swimming in free CPU cycles as it is.
<nexgen2>Can you please just give an idea about how much percent of packages are not reproducible
<nckx>‘Reproducible’ means different things. It's often narrowed down to ‘bitwise reproducible packages’, which can be very important, or completely irrelevant. It's often overemphasised.
<nexgen2>what you meant under 10% non reproducible?
<nckx>I care that my two servers with identical Guix system configurations do exactly the same thing. I don't give a whiff about timestamps in libfoo. It's just an easy shortcut, sometimes, to check whether two systems are identical.
<nckx>Going for 100% source(-equivalent) bootstrapping, as Guix does, is IMO far more important than the overhyped ‘let's get together & compare our bits’ approach. Those bits after the fact don't mean much. Which isn't to disparage the Debian reproducibility folks' work, bit-reproducibility is good, but it's not currently resting on any foundation.
<nckx>mbakke: Won't that only work if you haven't downloaded substitutes from that server?
<nckx>So I've started a ‘build everything again and check it’ script on my substitute server, but that's a) not scientific, I'm just curious b) will be a single snapshot in time and c) will take a hell of a long time 😛
<nckx>nexgen2: I think that's lower than average but not implausible.
*nckx wonders which item differed in nexgen2's analysis.
<nexgen2>well, I already indicated MES advantage on the forum where I am comparing GUIX to Debian
<nckx>nexgen2: A lot of current ‘reproducibility’ is just: if I feed source code into this huge binary blob [e.g. Debian], and you feed the same source into the same blob, do we get an identical new blob? That's all those reproducibility numbers mean.
<nckx>nexgen2: Sure, I understand (and I agree with what I assume is your response, although I'd state it less… Russian ;-) ) The whole premise of ‘usefulness’ is just so subjective. I mean, you don't want to know what I hear said about plainn software freedom by people not in our bubble.
<nckx>This is the same thing. ‘Eh, who cares’. That's not something you can sanely argue against. It's a dead end.
<nckx>Which is to say I can't; I backtrack and try another avenue.
<nckx>GNUtoo: I didn't know there was an (unrelated) raw-content field in Guix's wrappers or I would have used a different word. However, the docs for nginx-location-configuration say that it takes a ‘list of strings’, not whitelisted fields, so you should be able to add it there at least: (body (list "autoindex on")); or so.
<GNUtoo>Note that if you care about privacy too you might need additional measures
<nckx>quiliro: I get ‘Note: file is write-protected’ because ‘guix edit’ tries to ‘edit’ files in the store by default [this is indeed unfortunate, I dream of an elegant copy-on-write solution some day], so you'll have to point emacs-guix to a writable checkout first.
<nckx>quiliro: I never use guix edit, I just… edit ~/guix. With emacs, of course.
<rekahsoft>Hi all, when using 'guix system docker-image ...' what would a minimal os file-system configuration look like? I notice there is a %container-file-systems variable exported from the file-systems module, however I can't seem to get it to work when using (file-systems %container-file-systems).
<nckx>quiliro: If this is about jami, I see that 201904 includes a ‘Sets up video streams upon receiving the first video frame’ fix so yeah, might be worth trying.
<rekahsoft>nckx: all good, I was just playing with it today as I wanted to build a little sample python project that is managed with guix to show a friend
<rekahsoft>There are actually two slightly different ways to produce docker images from guix (at least from what I can tell). One is 'guix system docker-image ...' and the other is 'guix pack -f docker ...'.
<nckx>rekahsoft: The former creates a complete operating system, the latter an ‘application bundle’ (application + dependencies, or basically a big static binary). Maybe you knew that already, but I don't think either is redundant or the overlap huge?
<nckx>I do think all your questions are perfectly reasonable and not having a clear introduction in the manual is a bug. Which would be nice to report, if you'd have the time. Hint hint 🙂