<vagrantc>maybe someone can confirm? i gotta run...
<guix-vits>mbakke, janneke: `ls /gnu/store/*linux-libre*/.config`. Not only in gnu/packages/aux-files/linux-libre/, but also there the k-configs are... Just those are dot-files. Probably i need to alias ls, adding -a by default.
<xelxebar_>Our bison is old, at 3.5.3. I tried bumping to the laste (3.6.3), and holy bajeezus, `guix refresh -l bison' wants to update 3713 dependents...
<apteryx>xelxebar: did you check which bison version is used on the core-updates branch? That's the place such update would need to happen.
<apteryx>sneek later tell xelxebar did you check which bison version is used on the core-updates branch? That's the place such update would need to happen.
<nckx>Everything's possible in principle 😉 If a package statically links perl, for example, or if some references to /gnu/store/old-perl are ‘obfuscated’ in some way so the grafter can't find & rewrite them.
<nckx>xelxebar: For that case you can simply create a bison-3.6 package and use ("bison" ,bison-3.6) in your poke package.
<nckx>Switch to ,bison when it's updated to 3.6 next core-updates.
<royball>hello guix. i am also getting that same grub.cfg error (for both guix system vm and guix system reconfigure)
<royball>looks like there are a couple minor tweaks to get it working again.
<royball>i can submit patches for the tweaks that worked for me, if y'all don't mind goofy commit-messages.
<nckx>…grub.cfg error? Oh dear. I'm currently reconfiguring my system. Is there a pleasant surprise waiting for me at the end?
<thorwil>civodul: hi! i should provide the motivation: i had a build error with clementine, there’s an open ticket. can’t be reproduced. todays ‘guix pull && guix package -u’ got me the substitute.
<janneke>nckx: you and royball found/fixed my grub.cfg typos? so sorry!
<thorwil>so i would have liked to trigger a local build with the least amount of fuzz. ideally without removing the package and a garbage collection run that will get rid of much of the build machinery, again ...
*janneke didn't see the actual conversation about that, only something here and the patches on master
<civodul>thorwil: you can try "guix build clementine --no-grafts --check" to rebuild locally
<civodul>janneke: i think it wasn't in our timezone
<janneke>civodul: the worst part is that i found and fixed these typos this weekend ... and apparently i lost them
<janneke>juggling branches and updates...wip-hurd-vm / wip-hurd-vm-new or so
<thorwil>civodul: thanks, it’s busy now :) doesn’t --no-grafts apply to build dependencies, too?
<janneke>on a more positive note, "guix build hello" now progresses until coreutils-final with wip-hurd-vm
<thorwil>civodul: is this enough for a report? ‘guix build: error: derivation `/gnu/store/003z966hxvb6hs17sjq4fcwshcqvafxa-clementine-1.3.1-2.4619a4c.drv' may not be deterministic: output `/gnu/store/2vpsjrx7q7wx9715cpc2y1vg5xy7hbfw-clementine-1.3.1-2.4619a4c' differs’
<sneek>Welcome back guix-vits, you have 1 message!
<sneek>guix-vits, nckx says: The Guix System equivalent of /proc/config.gz is /run/booted-system/kernel/.config . It always matches your running kernel. Unlike /proc, it doesn't require loading an otherwise useless module into kernel memory as root.
<janneke>is that documented somewhere (eh, besides this channel's logs?)
<NieDzejkob>I sometimes encounter libraries that need other libraries in the profile to use them during compilation (either because of headers or linking). Is it appropriate to move the dependencies into propagated-inputs?
<leoprikler>i found that even if you do, you have to manually supply those inputs
<guix-vits>janneke: if you about .config, then probably no (will be cool if someone with good English append this to the Cookbook).
<NieDzejkob>I'm not familiar with the glib ecosystem, any specific examples? I observed that linking with igraph (statically? this is only triggered by rw 0.8) needs zlib, lapack and openblas, moving these to igraph's propagated-inputs makes it work
<mbakke>Bryophyllum: unfortunately the network configuration facilities in guix are still somewhat rudimentary :/
<mbakke>Bryophyllum: if you feel like getting your feet wet with guix hacking, it should not be too difficult to extend dhclient-service-type to write a configuration file where you can specify additional DHCP servers
<guix-vits>Bryophyllum: IDK. What about a firewall trick like that: "udp dport 53 redirect to :5353" (using some app that serve the DNS thingy)?
<janneke>nothing to see here... "<janneke> mbakke: oops -- but i'm looking at master right now and it looks like i cannot build a hurd system anymore -- investigating" => make clean-go
<mbakke>s/DHCP servers/DNS servers/ in my previous message :P
<guix-vits>janneke: doing `guix system vm --target=i586-pc-gnu --no-grafts gnu/system/examples/bare-hurd.tmpl` on <guix 141b5c1> i got: "configure: error: this is the gnu os, host cannot be linux-gnu". What had i did wrong?
<Bryophyllum>mbakke: Right. I've peaked at the source code, and it wouldn't be too hard to define an extra variable and append it to the fork+exec line. I have a lot of free time on my hands, so I might do that as well, but I must learn GNU Guile first
<Bryophyllum>guix-vits: I was thinking of a simpler approach: overriding the resolv.conf after it's created by dhclient, but I couldn't make it work.
<civodul>janneke: it'd be a Shepherd service that spawns qemu with the image as an argument, and the image would be the return value of system-disk-image or whatever it's called
<mbakke>Bryophyllum: sounds great! Don't hesitate to ask here about anything, it's a pretty helpful and knowledgeable crowd :-)
<janneke>guix-vits: you're not doing anything wrong, per se, but currently only "guix system build" and "guix system disk-image" are supported
<janneke>civodul: ah...not for CI, but just for us mortals -- to always/easily have a Hurd VM ready
<mbakke>janneke: we could launch that service on all the CI build nodes, and then we'd have a Herd of Hurds available for CI
<guix-vits>janneke: cool. Through someone (:P civ*dul) omit "how to use" part in the post, so i going to "ook? ook!" the disk-image usages (Manual 8.16).
<janneke>well, maybe someone can fix the post by adding a reply
<Bryophyllum>mbakke: That's the spirit! ^^ I'm going to leap at a chance while we're still at it: would there be a reliable way to configure a simple-service to overwrite the resolv.conf file after it's created by dhclient? This seems hacky at best, but should do *for now*.
<Bryophyllum>I'm thinking of something similar to systemd units, where it can be specified after which service my service should be executed.
<tibbe_>Hi, after some time I wanted to start writing C++ code on my Guix machine again. But compiling almost any C++ program fails somewhere in the standard library headers. I am using the g++ from the gcc-toolchain package. Is this a known problem or am I doing something wrong?
<civodul>tibbe_: there was a report recently but i don't know what's going on
<nojr>leoprikler: thanks, another question, when setting up a dev environment it only needs `guix environment -l guix.scm`? I am using this on a repo online which provides `guix.scm` but when I try to reach for `./pre-inst-env` it says says No such file or directory
<leoprikler>Assuming that you have a clean checkout of the code and the guix.scm is well-written, such a thing should not happen.
<leoprikler>"pre-inst-env" is rarely part of a clean checkout, though, usually you'd have to ./configure first
<nojr>leoprikler: thank you, I think in my case the provided guix.scm is a bit old, that may be it (12 months Guix has changed since then)