IRC channel logs
2025-11-22.log
back to list of logs
<ieure>You don't need to exit the subshell and run `guix shell' again. <NaN23>Hello everyone, I may need your help :) On my Guix System /var/guix/profiles/system points to a non-existing link. When doing a system reconfigure I get the warning the provenance cannot be determined and it stops because of an error parsing a (empty) derivation. I did boot a previous generation but the behavior does not change <NaN23>Any ideas? Will try older generations now and check the irc logs the next days. I would be very happy about any hint :) <ieure>Is there some way to get the default value for a a field in a configuration record type? <flurando>is there any recommended way to change the login shell for root account? I know we can specify nologin from (guix system shadow) but seemingly there is no way to customize the root account. <flurando>I wish to disable the root account login, now wondering if just my sudo would work, and whether this crashes the shepherd services <meaty>hmm... the package I'm making can't find opengl via cmake ("Could NOT find OpenGL (missing: OPENGL_opengl_LIBRARY)"), even when I add mesa to the inputs... <meaty>ah, mesa has no cmake accomodations. patching to use pkgconfig instead works <flurando>oci-service-type is really confusing, I have tried many ways but still could not get the network right. <flurando>I configured one with direct configuration and simple-service, both tried, both failed... <flurando>Now seems to me that whether or not the one-shot docker-network service generate networks defined in oci is pure luck. <flurando>Basically speaking, the command line is all correct, but my specified network is not generated <drl>does anyone understand why i can't install guix. I'm getting faild to install and lits 4 packages <flurando>Yes, if you happend to have a pc which does not tell you for sure that it supports linux-libre <drl>oh is there a work around? <flurando>if it does not tell for sure, it won't support linux-libre, and guix only support linux-libre, boom! <Rutherther>drl: what's the error and how are you installing it? <drl>Failed to install the following packages. Manual intervention is required: <drl>guile-avahi - exit status 1 <drl>guile-json - exit status 1 <drl>guile-lib - exit status 1 <drl>guix - exit status 8 <drl>im just trying to install it on arch linux <flurando>There is... Wait, you are not doing system install, but binary install! <Rutherther>flurando: well they said guix, not guix system, so naturally yes they are installing guix <drl>i also tried installing guix on fedora and that worked <flurando>Maybe it would be better to just install guix using the official binary installatin document. <flurando>I have never used arch, besides a week or so on WSL years ago. So I am not able to help. <drl>i tried that on arch and debian and nothing <flurando>drl: But you could even install guix on Github Runner, with an action. So there should not be any problem. <drl>i'm trying it now again <flurando>drl: Wait, one thing is really importent. DO NOT use the 1.4.0 manual anymore, it is broken from nowadays guix. <flurando>drl: Refer to the devel version and use the latest binary as possible. <drl>I'm new to guix. thanks for the help <flurando>I was checking why my wordpress oci service always 125 error, well, it amuzingly append localhost when tag only contains wordpress... <flurando>Bad news is oci does not seem to provide any method to disable this auto prefixing <Rutherther>yes, you need to provide the full tag, ie. docker.io/wordpress <flurando>found solution, for wordpress in oci, use library/wordpress instead <rrobin>e.g. locally guix build --check --no-substitutes --no-grafts python-pytest-doctestplus <tplaten>Today I'll continue on adding new packages to guix <nmeum>how do I best create general files and directory as part of my operating system declaration? for example, for my nginx-configuration I want to create the /srv/www.example.com directory. guix home has home-files-service-type is there something similar for guix system? <Rutherther>nmeum: special-files-service-type is the closest equivalent. You can do your own as well of course if you had some special requirements on it that this one doesn't cover <Rutherther>ie. not sure if creating symlinks is appropriate for nginx sites <tplaten>When I try to build guix I get make[2]: *** [Makefile:7971: doc/images/service-graph.png] Error 1 <tplaten>I managed to get Overte running on Debian (x86 only for now, on ppc QTWebEngine is missing) -> next is to get Overte building on Guix <meaty>is there a way to have a package retrieve only certain git sub-modules? The repo I'm packaging has a tiny submodule with no build system of its own, and another submodule that is ffmpeg <ieure>meaty, Just rummaged in the code, and I don't think so, it looks like an all-or-nothing switch. <ieure>meaty, You can set #:recursive? #f, stick origin/s for the submodule/s you need into the package inputs and manually move them in place. Or set #:recursive? #t and delete the ones you don't need (though this is wasteful of bandwidth). <meaty>ieure: you mean, (origin ...) records can go in the input field? <gargantua_kerr>Is there a way to cache the build-deps for a package and not rebuild the world everytime? <gargantua_kerr>I'd like to keep building the target package multiple times but not the builddeps <ieure>gargantua_kerr, That's how it should work. It's actually quite difficult to get Guix to rebuild things which have already been built. Can you share more info about your issue? <gargantua_kerr>whenever I do a "./pre-inst-env guix build <pkg> --keep-failed" I see a huge number of "compiling" logs against builddeps and each build takes >1 hour <ieure>gargantua_kerr, What package? Can you paste a log? Are you switching branches in between builds or something? <ieure>gargantua_kerr, I think you're misunderstanding the output, and what's likely happening is that you're switching branches or changing the .scm files in some way. The messages you're seeing are Guile compiling the package definitions, not Guix building the packages. <gargantua_kerr>ieure: could be guile thingy, but it takes just a really really long time :) Is there a way to cache it at least for subseq compilations? <ieure>gargantua_kerr, Okay, my hypothesis was incorrect. Those are dependencies bundled with your zola package. For reproducability, artifacts from one package build are not accessible from another. <gargantua_kerr>Also if I modify a package scm and re-compile it still seems to not work. It did on the master branch but then I changed to a new branch to commit something and then my changes don't take effect. <ieure>gargantua_kerr, So, a) this is an artifact of the zola code and how your package is defined, and b) if you want to change that, you need to unbundle all that stuff, so it's not built along with your package. <gargantua_kerr>I think that is /probably/ not an option due to rust being heavily version dependent and statically linked. <ieure>"Also if I modify a package scm and re-compile it still seems to not work." <ieure>Depends on your modifications? <ieure>I need more information, like a paste of what you're seeing, to give much help. <gargantua_kerr>seems to not work here <- it is not taking up my changes even if I do syntactically wrong stuff <ieure>That's not how it should work, or my experience. You'll have to share a paste of what you're doing. <ieure>gargantua_kerr, The specific build failure in https://dpaste.com/8T3D6K3XZ is the install-completions phase not finding the zola binary, which it needs to run. But there may be another issue underlying why that's the case. <gargantua_kerr>ieure: If I add in wrong syntax to the corresponding scm file, it still goes that far and reports the build as failed. This started to happen after I did a `git checkout -b fix-zola` from master. <ieure>gargantua_kerr, What is "wrong syntax?" Can you paste a diff of those changes? <ieure>If you have a branch up somewhere, I can try to reproduce. <ieure>gargantua_kerr, Building that fails for me. Difficult to say exactly what's happening. Does it work as expected If you `make -j12 && ./pre-inst-env guix build zola --keep-failed'? Or `rm gnu/packages/rust-apps.go && ./pre-inst-env guix build zola --keep-failed'? <gargantua_kerr>ieure: does it throw a syntax error for you? Let me try to rm the go file and rebuild. <ieure>gargantua_kerr, Yes. ice-9/boot-9.scm:1685:16: In procedure raise-exception: Throw to key `match-error' with args `("match" "no matching pattern" (unbound-variable "resolve-interface" "no binding `~A' in module ~A" (shared-mime-info (gnu packages freedesktop)) #f))'. <ieure>The code you pasted must not be what's in the repo you're building from, then. I don't know what else would cause that. <gargantua_kerr>ieure: I think I'll do a clean rebuild which is gonna take time. Does guix have a CI somewhere so I could test a cleanup somewhere? <ieure>gargantua_kerr, PRs get build in CI, but it's been my experience that it happens too slowly to be very useful. <gargantua_kerr>I have a PR, and when I open up other PRs I see no CI information anywhere <ieure>gargantua_kerr, That's the "too slowly" part. <gargantua_kerr>I come here from debian packaging experience and the CI there is quite fast and useful. So I am probably spoiled by that at this point. <ieure>lol, just noticed that guix-cuirass-bot is labeled "First-time-contributor" <ieure>Oh, interesting, this is buggy! It doesn't know what PR it's building. <ieure>I generally reuse the librewolf-updates branch for every update, instead of making librewolf-145.0.1-2 or whatever. So it looks for the first PR from librewolf-updates and puts the build status there, even though it's a totally different PR. <csantosb>From my side, I'm not sure to understand what exactly is going on with this ci bot, see #4291 for example <csantosb>It correctly builds 15 packages ... then it gets crazy. <ieure>csantosb, I dunno. I run my own Cuirass machine and generally build stuff before PR'ing. But it would be nice if CI was reliable. <Rutherther>yes, they have to be so that they are signed by a committer <tplaten>Overte is difficult to package for guix. So many dependencies are missing or not found by CMake even if in the input list <plattfot>Anyone know how to fix false positives like this? `<stdin>:17236:0: warning: possibly unbound variable `serialize-alpha-mode'` when I evaluate a buffer with geiser in Emacs, I'm getting them for fields in the `define-configuration' that are using a (serializer ...) option. <janneke>how to avoid a build to "time out" after 24h? it has been making progress all the time, afaics and was at 67%...grmbl! <janneke>ah, there's a --timeout (me only had to deal with max-silent-time, never had a build that took so long...) <janneke>i suppose using --timeout=0 is what i want... <janneke>hmm, possibly it's safer to use --timeout=345600, or go read the code <janneke>istm that bayfront uses 48h, i don't seen timeout 0 being used...but you'd prolly never want that on a build farm... <benjaminwil>hi guix, i made a pull request to package a rust program last week. it successfully builds and i believe i have done everything i need to do re: the pull request checklists. but no one from team-rust has reviewed or merged the pull request. have i missed a part of the process or have i done something wrong? i see that other team-rust tagged packages have been merged recently, is why i am wondering.