<thomasd>looking at guile-emacs build failure on core-updates, it fails because of the libjpeg version check, but I don't understand how that check can fail
<tmssen>Hi, trying write a definition of wkhtmltopdf; and figuring out how to package and contribute packages. I have a definition I think is getting close to useable-ish, but running 'C-c . b' in emacs in guix-devel-mode gives me 'ERROR: In procedure #<procedure 57ac8e0 at <current input>:76:14 ()>: Unbound variable: wkhtmltopdf'
<tmssen>how can it not be bound? I can call guix build wkhtmltopdf outside emacs, it gives me other errors but recognizes the definition, I think...
<rekado>snape: that requires that you are subscribed to the list(s) and have a copy of the messages.
<rekado>what I wrote downloads the mbox, turns it into a maildir, indexes that and opens mu4e on that maildir.
<rekado>this allows me to unsubscribe from guix-patches because I can fetch the emails on demand.
<efraim>I wonder if there's some ncurses program that will do that, I'm currently mostly downloading the mbox and opening with mutt
<thomasd>I think a dependency of your pacakge is grafted, therefore yours is grafted as well
<thomasd>indeed you will end up with both versions in the store. (though I suppose the ungrafted version can be garbage collected afterwards)
<erliphant>thomasd: thanks. This is interesting because it seems that I need this second package if I want to use this build for substituting. But I don't get it if I export the environment I built it in
<erliphant>thomasd: what i'm doing is building on one machine and exporting it to a central server where I run "guix publish". However, the export is incomplete because it is missing this graft.
<civodul>erliphant: grafts are always computed locally
<civodul>on purpose: the assumption is that it's faster to compute it locally than to download it
<erliphant>I see .. but that means that it needs the package source to be available?
<erliphant>civodul: I don't really want builds to run on all my production hosts. There are firewalls etc that mean that they won't be able to connect to source repos. I'd like to build centrally and publish the changes. Is this not possible with grafts?
<civodul>erliphant: the grafting process is purely local, it shouldn't require access to the internet etc.
<civodul>and then users graft the replacements locally
<erliphant>civodul: I see.. the problem is that I don't think that the graft ends up in the environment, so I can't export as a substitute. Maybe I should look to the --missing flag to transfer the build.
<erliphant>civodul: rather than relying on the environment as the closure of packages that should be exported
<erliphant>thanks rekado and civodul - this information has been very, very helpful.
<civodul>erliphant: you could try 'guix copy' also
<amz3>kyamashita: if if guix package -i something inside the environment, does it update my profile?
<cbaines>Does anyone know a way of adding actions to a shepherd service defined through Guix? I've had a look, and it looks to me like the shepherd-service-file doesn't support that yet. I'm also quite unsure how to implement it, as getting the g-exps and make-actions macro to work together looks quite tricky...
<cbaines>(I also noticed that the shepherd docs are wrong about actions, where it says "(It actually is a hash currently.)" it looks like a list to me)
<amz3>so, I changed guile-2.0 to guile-2.2 for guile-cairo in gtk.scm and I get the following error during 'make check' ;;; ERROR: failed to create path for auto-compiled file "/tmp/guix-build-guile-cairo-1.4.1.drv-0/guile-cairo-1.4.1/tests/unit-tests/./api-stability.scm"
<amz3>when I run, guix build -K guile-cairo, it fails too. BUT, if I 'cd' into the build directory and do 'make check' it says all tests passed
<kyamashita>amz3: Did you load the build's environment variables, too? `source /tmp/guix-build-guile-cairo-1.4.1.drv-0/environment-variables`
<jorgesumle>ERROR: In procedure mount: mount "/.rw-store" on "/gnu/store": Invalid argument
<jorgesumle>There was another line before the error ->>> herd: exception caught while executing 'start' on service 'cow-store'
<ng0>it's been years since I've used modular kernel insteads of costum build ones (or had to care about its effects).. now switching disks in between core2duo systems works. and I assumed that the same disk could be used in an i7 system, as we don't apply any architecture specific options.. but I'm getting dropped straight back to the uefi/legacy boot screen
<ng0>I was able to boot from the installer of Guix. So I assume that a system build on core2duo is incompatible with i7 in some way. correct?
<ng0>I just had 10 minutes with this system, so maybe the previous dangerous cyber-pathogen still has some leftovers on there which are still in the way.