<shcv[m]>so, I'm still having problems with guix not updating fully; doing a plain `sudo guix system reconfigure wsl-config.scm` gives me the error "no code for module (gnu system images wsl2)", but I've run a `guix pull` and it works if I use time-machine: `sudo guix time-machine -- system reconfigure wsl-config.scm`
<shcv[m]>the first line of `guix --version` is weirdly "guix (GNU Guix) 0"
<Grimpper>Hi. Could anyone help me figure out how to add elements to a list in guile?
<Grimpper>I would like to add elements to the inputs of a guix package, is this good: `(inputs (alist-cons inputs gtk atk))`?
<pkill9>how many wayland compositors other than sway are packaged in guix?
<jts>hey y'all, me again. i'm trying to figure out a weird gexp error. I'm being told the symbol gexp doesn't exist, which seems improbable since the macro #~ is being expanded into gexp and also `(guix build gexp)` is imported in this module. any insights?
<sneek>jts, nckx says: I think I've trawled through every single ‘rtl8812au’ project on GitHub (I'd say beyond, but really, it always ends up on GitHub). They all have firmware files, even if the names change. Sorry.
<sneek>jts, nckx says: I've requested removal from H-node. Such a pity, they even explicitly documented a Guix System configuration…
<jab>slightly off topic...the MNT reform now can run on an FPGA. That's pretty cool! And they have a test one that has 8GB of RAM.
<euandreh>jts: maybe where you're staging the code into you also have import the module?
<euandreh>jts: also, isn't it `(guix gexp)` instead of `(guix build gexp)`?
<jts>you are correct that it is `(guix gexp)`; the file has it right, my brain just got it wrong XD
<jts>What do you mean by where I'm staging the code into I also import the module?
<jts>I seem to have resolved the issue by turning the arguments argument into an explicit `(list ...)`
<rushsteve1>Hello, I was wondering if there was any chance someone had a package definition for Python 3.10? I've been trying to write one myself with little success.
***LispyLights is now known as Aurora_v_kosmose
<PotentialUser-24>Hello this is a question pertaining to GuixSD. I am wondering how I can change my desktop environment? Usually in GDM there is a gear icon in the bottom right of the login menu where you can click it and change installed desktop environments. I'm not seeing that widget though I have installed Gnome. In the initial install process I selected to
<PotentialUser-24>install XFCE and did not install gnome so I installed gnome after with Guix and want to use gnome as my desktop environment now instead of XFCE. Am I missing something?
<MaNI>I'm unable to reach ci.guix.gnu.org - my ISP has this to say "As per our upstream transit providers, the owner of the destination prefix 184.108.40.206/16 needs to do an RPKI's ROA record as that is missing,.. Also checking from the various IRRs ( RADB/RIPE, it seems that a new origin AS has been created in the last few weeks, thus appears to be two origin AS's of the same prefix.. Thus we had asked you to confirm to us if you have any commercial relations with the
<MaNI>destination network as it would be easier for you to raise with them to have them digitally sign all their prefix including 220.127.116.11/16."
<MaNI>is there an email address I could give them to make contact with someone for this?
<efraim>MaNI: you can email the information to rekado <at> elephly <dot> net and they'll make sure it gets to the right people
<efraim>If a channel depends on another channel and I pull a historical version of a channel, do I get a time appropriate version of the dependency channel or do I need to specify that one in the channels.scm file?
<henk-utrecht>hi guix! Maybe somebody knows the answer to this quick package-definition question: how can I use the version string of the package inside of a lambda? It overlaps with guile 'version' procedure and unquoting does not work.
<jpoiret>henk-utrecht: can you paste.debian.net the relevant code?
<nckhexen>You're close with unquoting, and the problem is probably that your code (lambda) is in a gexp, not a quasiquote.
<minima>i'm creating a 'guix.scm' in a project's folder, what would you say some differences are between using a manifest file ('specifications->manifest') vs an abstract package definition ('native-inputs')?
<minima>am i understanding correctly that those are two possible alternatives
<jpoiret>you'll have all the inputs of the package in the dev environment, not only the native-inputs
<jpoiret>don't conflate what some other distros call "build-time" dependencies and native-inputs. Native vs. non-native only specifies whether the thing should be built for the host machine or for the target machine when cross-compiling
<jpoiret>other than that, there shouldn't be any difference. Some people even use both at the same time
<jpoiret>ae_chep: host is where you're building, which might not be the same as the computer you'll want to use the thing on (the target)
<ae_chep>target is the user, host is the builder. Got it
<minima>jpoiret: but i suppose defining an abstract package might give more flexibility in terms of... well i'm not sure in terms of what but i suppose you can perform any task while defining the package?
<henk-utrecht>as you might see, I'm trying to use the package version to replace a string in a setup.py file, because it depends on a file that is not available.
***Dynom_ is now known as Guest7382
<henk-utrecht>nckhexen I don't think I'm in a gexp, it's in a package definition, or am I wrong? I tried '#$' but that is not understood by 'guix build'
<numerobis>Hi #guix! very small update on the gitolite issue I brought up yesterday: the repository does get created on `git push`, but the symlinking of the hooks fails because the "hooks" folder is absent in the bare repository. If I manually create the hooks folder in the bare repository, and then run `gitolite setup' manually, then everything works well.
<numerobis>Surprisingly, when I create a bare git repository manually as the gitolite user, then the hooks folder *is* there. Not exactly sure what's happening.
<nckhexen>henk-utrecht: Indeed, you're not in a gexp (then you'd have ‘(arguments #~(list …))’ instead of ‘(arguments `(…))’, which is why ‘#$’ isn't understood. The bug is you're calling version as a proceduce ‘(version)’.
<nckhexen>Ah, and write (package-version pplacer) because reasons.
<nckhexen>Reasons being the package *you* are writing does not have a version field. ‘inherit’ isn't magic like that — you can refer only to fields that actually exist; inheriting won't actually bring them into scope like that.
<nckhexen>So the brackets can stay, but for an unrelated reason.
<nckhexen>Also unrelated: don't add #t, it means nothing and has long been deprecated.
<nckhexen>Packages are records, which are like structs, or objects, or whatever you want to call them. If you have a <package> foo, the way to get a field from it is using package-<field>, e.g., (package-name foo), (package-version foo), (package-build-system foo), …
<nckhexen>(package (inherit buz) (stuff…)) is shorthand for (package (name (package-name buz)) (version (package-version buz)) (build-system (package-build-system buz)) (stuff …)).
<nckhexen>For all fields, not just those 3 examples.
<nckhexen>Redefining it works, but is redundant, but let's focus on the more serious problems for now.
<henk-utrecht>sorry for not understanding, if you write (inherit buz) is a shorthand for version (package-version buz), then I expect the version to be inherited
<nckhexen>It is. (package (inherit hello)) is a valid package, and if you inspect it you'll see that it has a version (and a name, and a description, and…). But that doesn't mean that the ‘version’ variable is suddenly bound within the package definition.
<nckhexen>But I have to go, which is why I was pressing you for your other problem :) Good luck with it, whatever it was! o/
<numerobis>Another update: it seems that gitolite in guix uses a git executable from the "git-minimal" package, which for some reason does not create the hook folder when creating a bare repository. I think the issue would be resolved if the "normal git" was used instead. I expect that other users of gitolite on guix experience the same issue.
<rekado>MaNI: I received an email from Seacom; I’ll pass it on to the network team.
<apteryx>nckhexen: I've sent some email to poke the others
<davidl>cbaines: nice, Ill try adding it to master and see if it works!
<xd1le>can guix home let you run shepherd services on a foreign distro?
<xd1le>reading the documentation, I'm not sure, but seems not
<rekado>xd1le: you can use “guix system container” for that
<henk-utrecht>hello people, I'd like to ask one more thing: I'm installing a 'python' based guix package, with a package definition using python-build-system. The package uses setup.py. Every time building fails with error 127, indicating 'python' executable is not found, which I understand, because the python (3) package only provides a 'python3' binary. Am I
<imtheonewhodudes>good afternoon guixers, does anyone here have any experience in doing a master thesis on guix? i'm currently ponderating doing something like that, something useful for the guix community and having someone share their experiences could be quite helpful
<imtheonewhodudes>Franciman: on the topic of guix. My idea was really porting the guix system on the pinephone but i'm not really sure it's "enough" for a master thesis and whether it'd be better to do something more academic
<unmatched-paren>the_tubular: > “As is hopefully clear to everybody, the major version number change is more about me running out of fingers and toes than it is about any big fundamental changes,” Torvalds wrote in his release announcement.
<sektor[m]>Guix is a nice crash course in Scheme, that's for sure.
<old>sektor[m]: To package management also and build system also!
<tricon>all three, yes. i've enjoyed it. it's the most excited i've been about an OS in a long time.
<old>yes! Guix solves soooo many things I had with other distros. The experience for a programmer/student/researcher has been a breeze
<old>I wish more people could understand that and adopt it instead of saying "but docker"
<florhizome[m]>unmatched–paren I saw some video talking about a new scheduler api which should make power saving more easy
<jab>old: I think just from a casual use case guix system in awesome! I have had debian and ubunt updates break...then had to re-install. I think I have have some issues like that with guix, but they are really rare.
<rekado>davidl: we have jupyterlab in the guix-science channel