<dftxbs3e>I would be so much more active at sending contributions if it wasnt done with git-send-mail - really I never used it and it always makes me uneasy because apparently there's bugs in debbugs too that prevent you from sending multiple patches at once..?
<nckx>dftxbs3e: Thanks. After a year I have no idea if that question was bullshit or no longer relevant, but it would be nice to have an answer.
<nckx>dftxbs3e: Not sure if it's a bug or a design flaw but yes, debbugs makes git send-email look worse than it is. There's a documented work-around, that's all I can offer.
<roptat>no, just set it in the network service you use
<roptat>all you need is to make sure the IP of your resolver is going to be routed through the VPN
<roptat>if you use network-manager, you'll need to configure your connection to use that resolver (whatever you choose), but you can't do it through guix config, you'll have to do it on a per-connection basis
<raghavgururajan>roptat: But network-manager-service-type doesn't have an option like that?
<mbakke>I've pushed another revision now, let's see..
<cbaines>mbakke, I added a feature yesterday where you can give the Guix Data Service two revisions, and it'll tell you which packages have broken between those two revisions (assuming it knows about enough builds to work that out). Once I start building staging stuff, I'm hoping this will help get a better sense of changes.
<mbakke>cbaines: that sounds amazing, it's my #1 missing feature from Hydra
<rekado_>apteryx: it’s probably in the Guile bug tracker now, so you can’t find it on issues.guix.gnu.org
<lafrenierejm>Just (attempted to) submit 37 patches to bug#44762 via git-send-email, which was my first time using send-email. Is anyone available to do a quick sanity of one of the emails to see if I need to resubmit?
<apteryx>rekado_: oh indeed it's in the Guile tracker, with ID 20272
<jayspeer>has anyone tried installing guix system on an old machine? I'm talking thinkpad x60t old
<kozo[m]>mothacehe Hello, I got stuck while testing out your PBP patch. these are the steps I took: 1) Git clone 2) git checkout <hash> 3) guix environment guix 4) curl the patch 5) git am the patch 6) ./bootstrap 7) ./configure --localstatedir=/var 8) make 9) Echo command 10) Finally, when I run the ./pre-inst-env command, I get: no code for module (gnu system images pinebook-pro).
<roptat>(it's a laptop, and it used to have a "vista ready" sticker on it, so that might give you an idea of its age :))
<mjsb>Good evening dear Guixlings! I was testing the script installation for the upcoming v1.2-rc2 on a Fedora 31, and the script completed well, then i rebooted but running guix commands feedbacks "guix pull: error: failed to connect to `/var/guix/daemon-socket/socket': No such file or directory"
<jayspeer>roptat: what kind of media have you used to install it? usb 2.0 is painfully slow (though I've managed to install debian this way) and cd is almost usable (but not really)
<mjsb>I checked a thread which suggests to start the guix-daemon, but running "sudo systemctl start guix-daemon && systemctl enable guix-daemon" won't start the daemon
<jayspeer>civodul: aren't those things defined automatically when sourcing from .config/guix/current/etc/profile and .guix-profile/etc/profile?
<jayspeer>maybe sourcing those files for the remote process could be a hacky solution
<nckx>jonsger: Thanks. Still building /gnu/store/kbpgcz6j52cca9mnvsgf4yps816w7j1g-vim-8.2.2017.drv here, still hasn't failed. Interestingly (...perhaps) I'm also on Wayland. Sway. Although that really shouldn't affect the build environment at all.
<civodul>jayspeer: not quite, it lacks GUILE_LOAD_PATH
<jayspeer>civodul: mine .guix-profile/etc/profile has it, if I have guile installed
<rekado_>I didn’t know about the OpenBSD songs. ‘100001 1010101’ is rather Rush-like.
<civodul>BTW musicians, we're (hopefully) releasing on Monday, which is Guix anniversary
<civodul>that can give ideas about the theme for the song
<dongcarl>Question for y'all: If I want to build clang-8, but with my-llvm-8 (say with a patch applied), can I use --with-input=llvm-8=my-llvm-8, and all the clang-runtime and clang itself will be rebuilt against my-llvm-8?
<dongcarl>My concern is that for procedures like clang-runtime-from-llvm, the INPUT gets rewritten, but when the procedure is evaluated, the "llvm" argument is still the normal llvm-8 and not my-llvm-8, but perhaps I'm being paranoid
<civodul>dongcarl: hey! it should replace llvm@8 with my-llvm@8 everywhere (note "@", not "-")
<civodul>if in doubt, you can check with "guix graph --with-input=llvm@8=my-llvm@8 ..."
<dongcarl>civodul: Help my understand the mechanism here: let's say I do `--with-input=llvm@8=my-llvm@8` and try to build `(clang-runtime-from-llvm llvm-8)`, the input llvm for the resulting clang-runtime would be replaced successfully, but note that in `clang-runtime-from-llvm`, it refers to `(package-native-inputs llvm)` and I'm wondering if _that_ would
<dongcarl>also be replaced with effectively: `(package-native-inputs my-llvm-8)`
<kozo[m]>How many modifications do I need to make to the example cuirass code from the manual to have it work? I have added the code to my publish server and I can connect to the cuirass-web page but it doesn't have any elements or packages to build. Do I need to add a manifest file somewhere?
<apteryx>indeed it was! My match pattern needed to be made into: ((name package output ...) ...) ;; added output ...
<db48x>pretty odd that you would end up with fonts that have letters but not numbers
<db48x>you should file a bug with as much information about how you got into that situation as possible
<kozo[m]>Are there other areas of documentation for Cuirass than section 10.8.22?
<cbaines>mbakke, I made the necessary changes to the Guix Data Service so it's actually possible to compare master and staging and find broken builds. Keep in mind that it's limited by the build information the Guix Data Service has.
<dongcarl>apteryx: I was able to reproduce with guix time-machine --commit=207c3c594e22b678ddcea8ebc78f19b839612187 -- build --cores=0 --max-jobs=96 -e '(@@ (gnu packages commencement) binutils-mesboot0)'
<cbaines>civodul, as for the broken build link, yeah, that page doesn't account properly that the build is actually for a different derivation which generates a common output. I'll fix that... The link on the derivation page works
<cbaines>On linking to builds, I also should start storing the actual build ID for Cuirass, as that would mean I could generate better links...
<civodul>ah isn't it that it links to ci.guix.gnu.org/build/xyz.drv instead of /build/123?