IRC channel logs


back to list of logs

<the_tubular>Well my first comment with podman is that it does not create a policy file by default.
<the_tubular>Otherwise it seems to work, but I've done very little testing
<podiki[m]>question about unbundling (program has dependency source): should I replace the source files with a guix package of the source? or try to remove the source and have it build with the guix package of the (compiled) library?
<the_tubular>Umm, trying to run an image from I get : Error: writing blob: adding layer with blob "sha256:a2abf6c4d29d43a4bf9fbb769f524d0fb36a2edab49819c1bf3e76f409f953ea": ApplyLayer exit status 1 stdout:  stderr: potentially insufficient UIDs or GIDs available in user namespace (requested 0:42 for /etc/gshadow): Check /etc/subuid and /etc/subgid:
<the_tubular>lchown /etc/gshadow: invalid argument
<arjan>do I need to be subscribed to guix-patches to be able to submit patches?
<podiki[m]>though guix mailing lists will hold your first message for moderation first, not sure about patches
<arjan>ah I subscribed after sending my first message and just noticed it went through
<the_tubular>I'm confused ...
<the_tubular>The errors seems know, but OP, closed it saying it's a systemd error ...?
<podiki[m]>the_tubular: no idea if this is related, but you saw the comment in the podman package code of a needed user setup?
<the_tubular>Not I was actually reading the issue right now
<the_tubular>Unlucky :/
<podiki[m]>in better news, I successfully unbundled a library, but a bit of pain in the steps involved
<the_tubular>I reran the command to make sure and I get this : mount: /sys/fs/cgroup: none already mounted on /proc.
<the_tubular>Is this normal ?
<the_tubular>mount shows it mounted : none on /sys/fs/cgroup type cgroup2 (rw,relatime)
<the_tubular>So, yeah ... Unlucky ...
<the_tubular>I also ran podman migrate, but same error
<the_tubular>You think that deserves a bug report ?
<the_tubular>I'm unsure if it's guix or podman's fault though
<the_tubular>Also goodjob podiki[m] :)
<Kolev>Improing my dotfiles. Using a combination of Guix Home and Stow.
<Kolev>Will this Makefile work?
<akirakyle>Is there anyone here who might be able to help me debug this issue that I just submitted?
<singpolyma>Kolev: is the reason to use stow because it's not safe to put secrets in the store?
<Kolev>singpolyma: Because I'm just inserting a file verbatim, not declaring anything.
<singpolyma>Kolev: guix home can do that, though, right?
<Kolev>singpolyma: Yes, but it's more overhead than just using Stow, IMHO.
<Kolev>singpolyma: Feel free to send a patch to put all the Stow files into the home config.
<arjan>managed to create a issue with the cover letter, but now my email provider refuses to deliver the rest of the patches to because that does not support TLS, will try again later with TLS requirement disabled
<the_tubular>I got podman as root working :) . But I think the root-less could use some work
<podiki[m]>and thanks; hopefully just a few more unbundles to do and then I can submit openrgb (control lights like case fans)
<podiki[m]>woop I think that's it, just got to polish it up and will get it submitted
<Kolev>error: ("PS1" . "$ "): source expression failed to match any pattern
<akirakyle>How do people manage the root guix version versus their user account's guix version? Do people generally update them together? I seems like it isn't possible for root to have no guix version since I run into the issue described here:
<drakonis>you don't have to manage that
<akirakyle>manage what?
<drakonis>the root account's guix version
<podiki[m]>the only "sudo" I do is for reconfigure, all other guix commands are with regular user; I think that's what everyone does on a guix system
<akirakyle>do you just leave it at an old guix version then?
<akirakyle>I mean leave the root's guix at an old version?
<Kolev>Any Guix Home users here? I'm having trouble getting my env. vars to work.
<drakonis>root's guix is the same version as the system, no?
<podiki[m]>akirakyle: when you use sudo it will use the user's guix version (from the env I think, preserved by default for guix); but I'm not sure the details
<akirakyle>Not necessarily I think, root can have a guix version of it's own (under /root/.config/guix/current)
<akirakyle>podiki[m] can you check if you have something under /root/.config/guix?
<podiki[m]>I don't think you need sudo -E (is that the option?) to preserve environment for sudo on a guix system
<podiki[m]>guix pull; sudo guix system reconfigure /path/to/config.scm will work just fine and is the recommended way I think
<podiki[m]>akirakyle: does not exist
<podiki[m]>I've never done a root guix pull or the like
<podiki[m]>I think doing things as root on a guix system leads to confusion and there is no need to
<akirakyle>Hm interesting, I might've messed my system up then by doing guix stuff as root for awhile
<Kolev> (environment-variables (list ("PS1" . "[\[\033[01;32m\]\u@\h\033[00m\] \[\033[01;34m\]\W\[\033[00m\]]> ") ("PS2" . "\[\033[33m\]>>\033[00m\]"))) ;; error: ("PS1" . "$ "): source expression failed to match any pattern
<podiki[m]>the only sudo previledges you need is to to reconfigure and should use the user guix version to have the up to date version
<akirakyle>I didn't realize that when I started so now I'm trying to clean up my root guix but running into the issue I linked above
<podiki[m]>how do you get that error? running what?
<drakonis>but why though?
<podiki[m]>drakonis: why what?
<akirakyle>Well my first mistake was I didn't understand the difference between sudo -i and sudo su
<drakonis>i meant running everything as the root user
<akirakyle>Then I was working out of root running guix pull
<akirakyle>I'm still learning
<akirakyle>Now I'm trying to go to what you describe as the typcial guix workflow
<akirakyle>But now with no root guix, when running reconfigure I get the same error as reported here:
***jonsger1 is now known as jonsger
<drakonis>try pulling then?
<akirakyle>Yes doing that works but now I have a root guix, which as I gather, isn't typical
<podiki[m]>sure, but nothing wrong I would say
<podiki[m]>just won't get used as you won't run root's guix ever
<akirakyle>Except take up space :(
<podiki[m]>it is all in the same /gnu/store and deduplicated
<podiki[m]>you could do some guix gc and try to remove everything; not sure how to completely clean it out exactly, maybe someone else will know (maybe try the help list, for posterity too)
<akirakyle>But then it'll be an old version after guix pull as my regular user and take up extra space
<podiki[m]>I don't think "guix" itself is very big
<podiki[m]>but maybe askthe list about removing all root's guix stuff; you won't be the last to do that I'm sure
<Kolev>I have IceCat in the system decl. but not every user has IceCat. 😕️
<akirakyle>I somehow am not encountering that issue anymore after doing a guix pull as root, then doing sudo guix reconfigure, then deleting old generations, then deleting the gc root for root at /var/guix/profiles/root (and the symlink at .config/guix/current). I can now sudo guix reconfigure just fine and no longer have any guix as root! Don't know why this
<akirakyle>particular sequence of operations fixed that issue, but it did
<arjan>managed to submit all remaining patches to debbugs
***califax- is now known as califax
<akirakyle>Anyone here use sway? I'm having trouble starting sway: I get the error 00:00:00.017 [ERROR] [wlr] [libseat] [libseat/backend/logind.c:267] Could not activate session: Interactive authentication required.
<akirakyle>Sway on guix 1.3.0 works fine
<akirakyle>I think the issue is related to this patch:
<akirakyle>I'm new to the whole elogind/no systemd thing
<akirakyle>lfam are you Leo Famulari?
<lfam>akirakyle: Yes
<sneek>Welcome back lfam, you have 1 message!
<sneek>lfam, ss2 says: I may have found a solution to the module failures in Samba. I hope to post a patch soon.
***duds-_ is now known as duds-
<akirakyle>Anything I can do to help debug besides git bisect I did?
<lfam>akirakyle: Can you use `guix system shepherd-graph` to inspect the config.scm being used for this test?
<lfam>I'm not sure how to find it but someone else can help figure out how to inspect the operating-system declaration used in 'tests/'
<lfam>You can install or use `guix shell` to get xdot, and then pipe that command to xdot for a visual representation
<lfam>`guix system shepherd-graph gnu/system/examples/desktop.tmpl | xdot -`
<lfam>Something like that
<lfam>I don't have an aarch64 computer and I haven't tried it in QEMU yet
<akirakyle>I wouldn't suggest qemu aarch64 emulation, it's painfully slow
<lfam>We need to figure out if there are really two definitions of xorg-service-type, or if it's some other bug
<akirakyle>So I'm doing guix system shepherd-graph of the failing test operating-system in gnu/system/examples/desktop.tmpl?
<lfam>I seem to remember that test uses that template?
<lfam>Do you have a copy of the Guix Git repo?
<akirakyle>Yeah I think that's the one the test is failing on
<lfam>The test is failing while building the Guix package itself, and that package is defined here:
<lfam>The package is based on Git commit 2a49ddb513476cd45ebca618ffb0b9e381c1e497
<lfam>So, you can do this to extract that particular revision of this desktop.tmpl
<akirakyle>Should I do this in a ./pre-inst-env in the guix at that commit?
<lfam>`git show 2a49ddb513476cd45ebca618ffb0b9e381c1e497:gnu/system/examples/desktop.tmpl > desktop.tmpl`
<lfam>And then run the graph command on that file
<lfam>That's the first thing to check: Is the operating-system declaration actually wrong or not?
<lfam>If not, then there is some other bug that only seems to manifest on aarch64 :/
<lfam>I would also check the bug-guile and guile-devel mailing lists for recent discussions of aarch64 bugs
<lfam>Basically, we want to reproduce the bug outside of the package-building container, so that we can inspect it more easily
<lfam>And, you can also check out that revision of the Git repo and run the tests there
<lfam>With `make check`
<lfam>It will probably take a while
<lfam>Isn't there a way to only run a particular test? I don't recall
<akirakyle>Yeah running it now
<lfam>I'm curious what kind of computer you are using?
<lfam>I'm also trying to get a sense of how people are using Guix on non-x86_64 computers
<akirakyle>I'm running guixsd on a m1 macbook air inside qemu which has support for the cocoa Hypervisor.framework api which lets it do native virtualization
<lfam>Ah, were we talking about this here a couple days ago?
<lfam>Or was it another M1 user?
<akirakyle>Yes that was me
<lfam>So the test fails on the Honeycomb LX2 as well, so at least it's not some exotic issue with the M1
***daviid` is now known as daviid
<akirakyle>That's good! Was this a separate build you started? I was looking at to see if this would fail since this is the first "boot-stripped" guix that I identified as failing the make check here
<lfam>I didn't go through the CI interface, but simply did `guix build $hash-guix-$version.drv` on the appropriate system
<lfam>You can run only this set of tests with `make check TESTS=tests/`
<lfam>That build you linked to is pretty old and I doubt it will actually be run at this point
<lfam>It's revision 13 of the Guix 1.3.0 package, and we are currently on revision 17
<akirakyle>Isn't it necessary to be run because of the boot-strippping process?
<akirakyle>Is there some mechanism that the CI uses to ignore outdated but pending builds?
<lfam>For your first question, that package would be necessary for users who haven't updated.
<lfam>To your second question, all builds are supposed to be carried out. The aarch64 build farm support is still nascent, so we will have to cancel old builds that users are probably not actually going to use the results of anymore
<lfam>Look at "Pending builds": <>. There are approximatly 80000 pending builds, and I know that almost all of them are queued builds for aarch64
<lfam>We can't keep up right now
<akirakyle>That must be annoying to have to manually cancel builds as the aarch64 nodes can't keep up
<lfam>We are still building the aarch64 capacity
<lfam>Part of that is software support in Guile
<akirakyle>I appreciate that there's even aarch64 support and look forward to the substitute availability improving!
<lfam>We are hoping it gets better real soon
<lfam>Right now people are investigating why Cuirass has trouble on aarch64, which causes the build machines to stop building
<lfam>And upstream in Guile:
<lfam>So, help is wanted!
<akirakyle>Well I'm hoping to make a full switch to guix from nix for my dev environment and if my emacs habits are any indication, I have a lot more fun digging into and debugging lisp than the nix dsl!
<akirakyle>On that note, you wouldn't happen to use sway?
<lfam>No, I'm using i3
<lfam>Old school ;)
<akirakyle>I'm trying to be a wayland citizen, but life can be hard on the bleeding edge :)
<akirakyle>I think this update ( that happened between 1.3.0 and now between may have broken something since now sway won't start for me on guix and I get this error: [ERROR] [wlr] [libseat] [libseat/backend/logind.c:267] Could not activate session: Interactive authentication required.
<akirakyle>(among other errors but I think they're all due to this one)
<akirakyle>And now I'm trying to understand elogind
<lfam>Did you report it on the mailing list yet?
<akirakyle>Not yet, was trying to see if I could make any progress debugging first
<lfam>You could CC the author of those patches. They might understand what's happening
<lfam>I think they are here too, jpoiret
<akirakyle>Good idea, or even better if jpoiret can chime in in real time :)
<akirakyle>lfam good news, I think, the test does fail for me in the git checkout
<lfam>Okay, that's "good" :)
<lfam>So then, can you use the graph command I mentioned?
<lfam>Also, can you redirect the output of the graph command to a file and send that file to the bug ticket?
<lfam>Something like `guix system shepherd-graph gnu/system/examples/desktop.tmpl > graph`
<akirakyle>Yep, although I think I should use the ./pre-inst-env here?
<lfam>Hm, I don't think it's necessary
<lfam>But I'm not sure
<lfam>Yes, you should use it I think
<lfam>You might have to enter a Guix development environment to do `./pre-inst-env guix system ...`. At least, I have to do that
<lfam>So, `guix shell -D guix` and then run the command
<akirakyle>That's what I entered to run the tests
<akirakyle>I'm getting this error trying to use /pre-inst-env: guix system: error: failed to connect to `/usr/local/var/guix/daemon-socket/socket': No such file or directory
<lfam>That means the Guix that you built from Git wasn't configured properly
<akirakyle>Oops I think I forgot to follow some directions
<lfam>Enter the development environment and do `./configure --localstatedir=/var && make `
<lfam>The localstatedir defaults to /usr/local/var, but your Guix installation almost certainly uses /var
<lfam>Then it should work
<akirakyle>Yep I skipped over that part in the manual
<akirakyle>I just emailed the graph to the issue
<lfam>Another thing you could try would be running `./pre-inst-env guix system vm gnu/system/examples/desktop.tmpl --dry-run`
<lfam>It should show the same error
<akirakyle>Indeed it does
<akirakyle>I really can't wait for extra aarch64 build capacity. I tried to install xdot and guix started trying to build the whole rust bootstrap chain which I imagine would take quite a long time to compile
<lfam>I'm building that revision of the Git checkout now and I'll compare the service graph on x86_64 with yours
<lfam>I think I know where the problem will be
<lfam>The desktop services module does something different on x86_64 vs aarch64:
<lfam>The sddm-shepherd-service provides xorg-service
<lfam>Somehow this other version the service graph provides it twice, indeed
<akirakyle>Ah, is that comment still true though, that rust isn't available on aarch64?
<lfam>Does anyone know?
<akirakyle>Well this would seem to me to say aarch64 rust is supported:
<akirakyle>The commit 49599fab56 that added that was made Dec 8 and references this thread for the reasoning:
<apteryx>akirakyle: still true, mrust doesn't build on non-x86_64 for now
<sneek>apteryx, you have 1 message!
<sneek>apteryx, lfam says: I found this leftover patch from the last release. It might still be useful: <>
<akirakyle>I think based on the times of my git bisect breaking between guix version 13 and 14 that would likely be the culprit commit
<lfam>apteryx: I don't think that old patch is still useful. I tested the installer script and IIRC it fetches all the keys in one round
<lfam>akirakyle: Yeah, I'm thinking this test failure is some fallout from that commit
<apteryx>lfam: I think the only thing that may have changed in the installer is that it now proposes to fetch automatically the keys
<akirakyle>I wonder how rustc was bootstrapped on aarch64? I guess guix bootstraps rust through mrustc?
<lfam>apteryx: Yes, the experience for users is much better now
<lfam>The annoyance I described doesn't occur
<akirakyle>lfam I'm going to try removing that check and see if the tests pass
<apteryx>OK, good! Feel free to close it then!
<lfam>apteryx: Is there a but ticket? Or just a sneek note :)
<lfam>But ticket
<apteryx>ah, nope, no ticket anymore it seems
<apteryx>at least not on guix-patches
<lfam>apteryx: I found the patch while pruning old Git branches
<lfam>akirakyle: I replied to your email with the graph from x86_64 and rendered PNGs of both graphs
<lfam>It should help illustrate what's wrong
<lfam>Both GDM and SDDM services provide xorg-server
<akirakyle>That commit is definitely the culprit then, I just commented out the whole if block and the test passes
<lfam>So where is the 2nd definition of xorg-server coming from on aarch64?
<lfam>That 2nd xorg-server depends on dbus, host-name, user-processes, and udev
<lfam>That sounds like gdm-shepherd-service: <>
<lfam>So, it's still being used on aarch64. Why?
<lfam>Is use of GDM hardcoded in the gnome-desktop-service?
<lfam>That would explain it, since gnome-desktop-service-type is used in desktop.tmpl
<akirakyle>That makes sense to me, although I'm still getting used to all this in guix so not the expert here
<apteryx>I think civodul had replaced gdm by lightdm for non-x86_64 systems; but haven't checked the details
<lfam>I think he used SDDM in commit 49599fab564f203b8e92d32e9b28c99e99849bfb
<lfam>akirakyle and I are trying to figure out #52908 / #52943, where the Guix test 'tests/' fails on aarch64 because xorg-server is provided more than once in the service graph of desktop.tmpl
<lfam>This breaks the build of the guix package on that platform
<lfam>Somehow it looks like GDM is still being used in that case
<lfam>Or rather, SDDM and GDM are both being used
<apteryx>is 'guix import crate system-deps' working for someone? I get error: string->semver-range: unbound variable
<lfam>I think you need to install guile-semver
<apteryx>ah, yes, that was it, thanks
<lfam>I always use `guix environment / guix shell` to make it available for this importer
<akirakyle>lfam I think I maybe figured it out "set-xorg-configuration" is used explicitly in desktop.tmpl and it includes gdm-service-type in desktop.tmpl independent of the login manager set in %desktop-services
<lfam>Oh really?
<lfam>I see, via login-manager-service-type ?
<akirakyle>It's passed in as a default optional value to set-xorg-configuration, so I think desktop.tmpl just needs to explicitly set this opional to the sddm service type
<lfam>Should it set that option in all cases, or only when not on x86_64?
<akirakyle>I'm new to guile too, so can the #:optional support a conditional, since that might be the cleaner way of doing this so the desktop.tmpl isn't touched with a conditional
<akirakyle>Otherwise I don't see a way of avoiding a conditional on not x86_64 in the desktop.tmpl file, which is maybe not desired since it gets included in the docs
<apteryx>akirakyle: #:optional can take any valid expression, unless I'm missing something
<lfam>I think we should feel free to adjust desktop.tmpl
<lfam>If I understand correctly, this file is only used by the set of tests under discussion, so it shouldn't be too hard to find regressions
<lfam>And I think it's the right place to put such a conditional, rather than in the set-xorg-configuration procedure. Like, these kinds of workarounds for growing pains of the distro should be in things like examples, templates, and not in service definitions themselves
<akirakyle>Does it make sense though for gdm-service-type to be the default argument for set-xorg-configuration?
<akirakyle>I feel like this may be a trap someone can easily fall into themselves when trying to write something like desktop.tmpl and customizing %desktop-services
<lfam>It's a good question
<akirakyle>Maybe it isn't so much of an issue since set-xorg-configuration is documented in the manual
<lfam>I think it does make sense, since GDM is the default for desktop-services-for-system (previously %desktop-services)
<lfam>And, almost all Guix users are on x86_64
<lfam>So, it's a default that usually does the right thing
<akirakyle10>Alright, testing a patch to desktop.tmpl
***akirakyle10 is now known as akirakyle
<DiffieHellman>Hello, why is the Guix release signed with a gpg key that has someone's gmail listed? I obviously can't trust that signature.
<DiffieHellman>*LiveDVD release
<lfam>Whether you trust a PGP signature is totally up to you; it's a social issue. All the software does is create a mechanism to prove that a signature was made by a person that had access to the private key
<DiffieHellman>Sure, but if a person uses gmail and adds it to their signature, I feel that they're incompetent.
<lfam>That's nice
<DiffieHellman>Are the latest images signed?
<lfam>How PGP is used in this context has nothing to do with email
<DiffieHellman>Sure, but I don't trust someone who loves to use gmail not to leak their private key.
<lfam>You never email your private key when using PGP for email
<lfam>So, how would it be "leaked" in this scenario?
<lfam>I don't think the latest / nightly images are signed, btw
<DiffieHellman>If you love those proprietary services, you probably love that proprietary software.
<lfam>Software freedom is not a matter of security
<DiffieHellman>Of course, but if you lack software freedom, you lack security.
<lfam>Additionally, there's no such thing as a "nonfree service" according to GNU canon: <>
<lfam>Eh, that's a matter of opinion
<lfam>Anyways, you can put anything you want on a PGP key. It's not a relevant way to assess the security of some operation
<lfam>Similarly, I doubt that you are actually Diffie and Hellman
<DiffieHellman>I'm the key agreement protocol
<lfam>Anyways, we do make an effort in terms of security. But Guix is *not* a "security distro" or anything like that
<DiffieHellman>You make a lot more effort than most.
<podiki[m]>you can just build the image yourself from a local guix
<lfam>Sure, but the Guix git repo is largely written by people using gmail
<lfam>So what can one hope for
<DiffieHellman>podiki[m]: Instructions?
<podiki[m]>the install.scm file is in guix, but you can also grab that separately from the git tree (pointing to the version included in the running guix is not difficult, but adds a step)
<podiki[m]>otherwise that "gnu/system/install.scm" path doesn't make sense
<podiki[m]> (or from whatever commit you want, e.g. 1.3.0 version)
<lfam>Of all the commits made to Guix, the top email server used by committers is (18 committers) followed by (12 committers) and then a few dozen personal domains, many of which use gmail
<DiffieHellman>Looks like I'm gonna need to review that source
<lfam>So you could say that gmail is intimately involved in the communications of the project, which does use an email contribution workflow
<lfam>You might also look at Linux itself
<lfam>I think any project that still uses email will have a plurality of gmail accounts
<DiffieHellman>There's a reason I carefully configure my Linux build in menuconfig
<DiffieHellman>install.scm is looking good so far
<akirakyle>lfam: unfortunately I jumped the gun a bit on blaming set-xorg-configuration, I still get the build failure when the services for desktop.tmpl is just set to %desktop-services, so there's at least more going on here
<lfam>What command did you run?
<akirakyle>I've just been modifying desktop.tmpl trynig to get the test to pass
<lfam>So, you're running `make check`?
<lfam>I thought that set-xorg-configuration was definitely the problem
<lfam>I wonder what it could be
<lfam>Are you sure it's testing your changed file?
<lfam>Like, give it some bogus value and see if it crashes in a different way?
<akirakyle>It may be there are multiple problems including set-xorg-configuration
<akirakyle>It's definitely testing the changed file since it gives me the appropriate error when I forget a paren
<akirakyle>I'm also hitting my debugging limit for the night, so I think I'll pick this up tomorrow. I feel like I'm understanding things better though so hopefully with some more debugging I can send it a patch that fixes this
<lfam>Can you send a quick summary to the bug tracker?
<lfam>Lotta new CO2 sensor drivers in linux 5.16
<lfam>Sign of the times
<DiffieHellman>guix system: error: image: unknown action huh
<VidarReturns[m]>I'd like to know where I can get a translation layer to convert Nix packages to Guix language
<DiffieHellman>I installed guix as a package on Gentoo. What do I have to do to be able to build images of guix?
<lfam>I wonder why `guix shell gcc-toolchain` gives me GCC 11
<lfam>I expected GCC 10
<lfam>VidarReturns[m]: Guix used to have a simple Nix importer, but it became less and less useful until we removed it
<lfam>DiffieHellman: Check how to use the image function of `guix system`: <>
<lfam>Answering my own question, because when matching packages by "name", "gcc-toolchain" does resolve to the latest revision of the gcc-toolchain packages
<DiffieHellman>lfam: I typed exactly `guix system image -t iso9600 gnu/system/install.scm`,
<lfam>It's only when asking the UI for "gcc" that you'll get gcc-toolchain-10
<lfam>DiffieHellman: You have the file in question, 'gnu/system/install.scm'?
<DiffieHellman>guix system --help doesn't have an 'image' option. I have guix-1.2.0 installed apparrently
<DiffieHellman>So the command is; `guix system disk-image -t iso9600 .....` huh?
<lfam>Your version of Guix pre-dates `guix system image`
<lfam>It had `guix system vm-image`
<lfam>You should check `info guix` and look at the section "Invoking guix system"
<lfam>If the manual isn't available in your installation, you can check the source of the old manual here, but it's kinda hard to read: <>
<lfam>If I were you, I'd try to update to a newer version of Guix
<lfam>That one is pretty old
<DiffieHellman>Okay, lets install sys-apps/guix-1.3.0-r2. Why is it masked?
<lilyp>DiffieHellman: There's no sys-apps/guix in Gentoo proper, which overlays are you using?
<sam_>you would have to actually share the mask message/full emerge output.
<sam_> tells you why :)
<DiffieHellman>It's compiling now just fine, I was just questioning why it was masked, as it's not a -9999
<sam_>(normally it *tells* you though, e.g. "masked by: package.mask")
<lilyp>It has the ~amd64 ~x86 keywords, so it's only lightly masked
<sam_>no, it's actually in package.mask (as linked)
<sam_>that's why emerge output would've been helpful
<DiffieHellman>I read the reason soon after
<sam_>it's because guile-3 is masked too
<sam_>too much stuff breaks with 3 sadly
<N0lim>Hi, how do i add a package to the general channel
<opalvaults[m]>N0lim: clone the Guix repo, create a definition for a package, test it, and when you think its good to go add it to whichever package group you think it should go in and voila!
<DiffieHellman>Hmm, why is GUILEC so slow?
<opalvaults[m]>guix build --install-from-file=nameofyourpackage.scm for testing
<opalvaults[m]>I think you do PR's through the mailing list or something I'm not sure how it works on Savannah
<N0lim>I have already installed the package and checked it with guix lint ( )
<DiffieHellman>Guix is failing with; error: getting attributes of path .... No such file or directory? On guix pull or installing?
<DiffieHellman>`guix pull: error: getting attributes of path `/gnu/store/09gicgfmzh6cwhg0fylzv4x5ywc5f3ya-gcc-mesboot-wrapper-4.9.4': No such file or directory`
<tissevert>hi guix
<tissevert>(and happy new year to everyone)
<DiffieHellman>Installed, how do I compile with -march=native and -O3?
<jpoiret>what do you want to compile with -march=native and -O3? Guix is mostly guile, so there is no similar flag
<jpoiret>well, apart from the guix daemon which is c++
<DiffieHellman>The programs that are installed.
<jpoiret>depends. Note although that you won't have any substitutes for anything if you do that
<jpoiret>there is a very recent addition of "tunable" packages, but it's mostly for scientific libraries and programs
<jpoiret>otherwise, you can simply inherit whatever package you want, change its build process and then rewrite the dependency tree using `package-input-rewriting`
<DiffieHellman>I don't really like binary packages myself
<jpoiret>well, packages in Guix are reproducible (mostly, some specific languages don't cooperate well), so we have sort of a higher assurance in this regard
<jpoiret>if that's your concern that is
<jpoiret>anyone know if there's any rationale behind using srfi-34/35 instead of builtins? Should we strive for portability with SRFIs whenever possible?
<mekeor[m]>DiffieHellman: you might be able to write a manifest, and for each C/C++ package, you might modify the compiler flags.
<mekeor[m]>i.e. you run `guix package -m manifest.scm` and manifest.scm contains something like `(packages->manifest (cons* (map (lambda (p) (package (inherit p) <some code to modify compiler options here>)) (list foo bar)) baz qux))`
<jpoiret>mekeor[m]: if you want to compile dependencies like that, you also need to rewrite the dep tere
<jpoiret>tree *
<yewscion>Good Morning, Guix!
<mekeor[m]>jpoiret: oh right. maybe one could iterate through the set of official guix packages built with the gnu-build-system and add -O3 to the compiler flags :D
<mekeor[m]>yewscion: hi :)
<jpoiret>i don't think there's an easy and general way to do that, packages using the gnu-build-system could very well be using a compiler that's not gcc/clang
<mekeor[m]>jpoiret: a different topic: you have been writing about polkit, dbus and network-manager on the help-guix mailing list. your e-mails went in depth but i still don't have a clue what you are actually suggesting we can practically do about the issue that we can't get non-root users on guix system to run network-manager tools using user groups.
<jpoiret>mekeor[m]: well, the forwarded mail didn't include what you were actually trying to do, the replies only go so far
<mekeor[m]>jpoiret: i did not start the mail-thread. i didn't respond to it either. but i face the same or a similar issue: e.g. i can't connect to a wifi per `nmcli device wifi connect SSID password SECRET`. it results in `Error: insufficient priviledges`.
<jpoiret>oh, alrigh
<jpoiret>are you in a graphical session?
<mekeor[m]>jpoiret: yes. (i start xorg as a user and run xmonad as window manager.)
<jpoiret>I suggest running /libexec/polkit-gnome-authentication-agent-1 from polkit-gnome alongside it then
<jpoiret>(it shouldn't pull in anything gnome related)
<else->in the `channels.scm` there is the possibility to reference a specific commit – i would like to use a tag instead but it does not seem to be possible. any other way i can "set" a tag as version for a channel?
<mekeor[m]>jpoiret: is that included in the polkit-gnome package?
<lilyp>there is (branch ), so if (commit tag) doesn't work you might want to lobby for (tag tag)
<mekeor[m]>jpoiret: also, why do i need although polkit is running already? :)
<jpoiret>well, you need a polkit agent for polkit to be able to ask you to reauthenticate
<jpoiret>that's what my last mail touches on
<mekeor[m]>jpoiret: will i need to run that as root?
<jpoiret>no, as yourself inside your graphical session
<mekeor[m]>jpoiret: i see
<else->could `guix channel update` be a possible remediation?
<mekeor[m]>jpoiret: it works. thank you. would you like to add this to the mentioned e-mail-thread or should i do it?
<mekeor[m]>jpoiret: also, i don't know what the libexec-directory is for. but i think it'd make sense for this binary to be callable from the shell. so i think it needs to and should be put into the bin-directory if possible?
<jpoiret>well, libexec is kind of a weird convention, I agree, but that's how upstream is packaged. I don't think the whole GNOME stack would behave well if we rename it
<mekeor[m]>else-: a remediation for solving your problem, i.e. for using tags?
<jpoiret>well, you can always add that to the ML, but the thing is, we don't know what they're trying to achieve. I personally thought they were working on a script that uses nmtui somehow, but it might just be them trying to use the program as is.
<mekeor[m]>jpoiret: or maybe it can be placed twice :)
<jpoiret>well, in the end you'll want to start it automatically, not through the shell, so i don't think it would change much, you can just type the whole path to the executable
<mekeor[m]>jpoiret: right. so for me, only remaining question is: who'll share this knowledge with the mailing-list? :D
<jpoiret>well, I'm waiting on a reply from the others, and if this particular bit is needed I will share of course mention it :)
<jpoiret>although in the short/mid-term i am planning on writing a couple blog posts about the desktop stack, including dbus/polkit and friends
<jpoiret>but that'll be in a while, i need to switch my website to a guile-generated one :)
<mekeor[m]>jpoiret: i'm pretty sure that the original poster of the email-thread will be glad to hear about the gnome-polkit-auth-agent :)
<lilyp>jpoiret, mekeor[m]: IIUC the point of libexec is that it ought not to clutter your shell
<lilyp>you can still call those commands normally, but you often have to go through rather specific hoops to make them do meaningful things, hence why they're hidden
<arjan>what is a good way to specify package outputs in a guix home configuration? (map specification->package+output (list "git:send-email")) still results in git:out
<arjan>got it working by using (map (compose list specification->package+output) (list "git:send-email")) based on specifications->manifest
<dsmith>Can anyone tell me what happed just before the bot died?
<dsmith>Maybe something porcupirate did?
<awb99_>are there some emacs experts here?
<awb99_>i would like to use in my guix emacs config
<awb99_>it seems that guix emacs package config sets up straight package manager
<awb99_>but I don't know how I can add my own startup emacs config
<awb99_>i guess I have to modify somehow the corgi config so that it gets loaded after the guix emacs bootstap code did run
<lilyp>awb99_: Guix' bootstrap code ought to run between early-init and init if memory serves
<awb99_>thanks lilyp
<awb99_>do you know which file I need to create so that I can load custom code?
<lilyp>Well, the corgi thing they provide there is a template you're meant to fill in.
<lilyp>btw. with custom, do you mean your own code or do you mean stuff for emacs' custom interface?
<awb99_>i think cori as it is will not be ideal for guix
<awb99_>so my idea is to copy parts of the Cori code to a emacs code file that forms part of my config
<awb99_>i just don't know which files would get executed by emacs
<awb99_>i guess this is decided by the guix emacs bootstrap system
<lilyp>Doesn't corgi have regular Emacs packages? What happens if you simply (require 'corgi)?
<awb99_>I am emacs beginner
<awb99_>i have no idea how I can add a non emacs package
***jonsger1 is now known as jonsger
<lilyp>awb99_: how you can add an emacs package to guix or how to add an emacs package within emacs?
<lilyp>anyway, I'll be eating for a while, so take some time to sort out what you're trying to achieve in the end
<awb99_>i want to execute some .el file in start of emacs
<awb99_>This .el File will configure my Emacs
<podiki[m]>awb99_: that sounds like your standard .emacs or init.el (emacs startup file)
<podiki[m]>perhaps searching for how that is used will be helpful
<awb99_>thanks podiki for the link. i was 100% sure that I read the guide annual on it. and now it turns out I missed that part. thanks
<tissevert>I kept my configuration from a previou install and I fear it's not quite right
<tissevert>is there a way to regenerate a clean .bashrc and .bash_profile for my user ?
<tissevert>(and then add my own config back to it)
<dcunit3d>hey is there some way to generate the `(operating-system ...)` definition of a system from the command line (similar to `guix describe --format=channels` for channels)
<dcunit3d>on most distributions, you can look at /etc/skel, but it may be different on Guix System
<podiki[m]>tissevert: not sure, maybe create a new user to see theirs? or maybe is in the guix source somewhere if it is customized for guix (not sure)
<tissevert>thanks for the good advice !
<podiki[m]>dcunit3d: not that I know of, but you can get it for a current running system
<podiki[m]>tissevert: I think mine are vanilla (I use zsh) I could paste those if you prefer
<tissevert>I had forgotten about /etc/skell, indeed there seems to be what I need there
<dcunit3d>tissevert: you may also want to look at /etc/profile because the initial profile loading stuff occurs there
<tissevert>no, don't worry about it
<dcunit3d>podiki[m]: how do i do that?
<tissevert>it's just that I have no problem with my PATH, but started digging into how GUIX_PYTHONPATH was populated
<tissevert>then read /etc/profile and noticed it was supposed to insert stuff in my PATH
<tissevert>which wasn't there
<podiki[m]>dcunit3d: I think it is /run/current-system/configuration.scm
<dcunit3d>ahhhh that seems familiar. i figured this out before, but i thought it was a command. thanks!
<tissevert>so I'm surprised it isn't more broken than it is, and I thought I'd try and look at what was supposed to be defined to see if there was anything important missing
<excalamus>good afternoon, Guix
<tissevert>hi excalamus
<podiki[m]>dcunit3d: welcome! and of course previous system configurations are around too, see guix system list-generations
<excalamus>looks like Guix has a wiki now, nice
<dcunit3d>tissevert: you may want to put some of the language-specific stuff in a profile/environment. it depends. after my /etc/profile or gnome-shell have loaded, i don't actually have a python in my PATH
<dcunit3d>i'm a guix/python noob though.
<podiki[m]>excalamus: which wiki?
<tissevert>I think it's supposed to be handled by guix directly
<excalamus>it's linked from the main page
<tissevert>I'm actually looking to replicate python's behaviour for a different language build-system
<excalamus>sorry, that's the Top level
<podiki[m]>oh right, I've seen that one
<excalamus>looks like there's a community wiki too because of restrictions on the other
<tissevert>I hate it when everything's working and I have no idea why ^^
<tissevert>apparently, /etc/profile gets sourced correctly when I enter an environment but I have no idea why
<excalamus>it's pretty sparse. Looks like there was a documentation meetup. These are things I'm super interested in. Hopefully they continue and I know about them ahead of time
<podiki[m]>those are announced on guix-devel usually too
<excalamus>I need to start paying attention there again
<podiki[m]>the community wiki....well, the original author is no longer in this channel
<podiki[m]>I browse the mailing lists a lot but haven't subscribed, don't think I have a workflow (yet) to deal with a mailing list in my inbox
<excalamus>I'm not up for admin duties, but if there's a legit wiki, I could move (and complete) some tutorials on packaging
<excalamus>ha-ha, silly me, I don't have https set up.
<gnoo>excalamus: love that you have a links page :)
<podiki[m]>I think more tutorials and examples in the official cookbook would be great
<excalamus>last year I was seeing if it's possible to make a step by step guide that uses guix-time machine
<dcunit3d>tissevert: in the docs, the way GUIX_PROFILE is set before sourcing the $GUIX_PROFILE/etc/profile script doesn't export the variable. that might be related to what you're seeing (it tripped me up quite a bit at first)
<excalamus>new years resolution:finish them :)
<excalamus>gnoo, ha-ha, glad you like it :)
<dcunit3d>so the shells/processes that spawn from it inherit some of the env. it's set up, so that you can modularly load profiles/environments while retaining a minimal profile to load on-to
<tissevert>dcunit3d: yeah, that's tricky
<excalamus>podiki, my challenge is just figuring things out at this point. But I've also gotten bogged down figure
<excalamus>ing out how to make the blog presentable
<dcunit3d>tissevert: i think direnv mixes in with guix pretty well. i've seen it in some users dotfiles. i haven't had a chance to try it yet.
<tissevert>but I don't see that $GUIX_PROFILE/etc/profile sourcing either in /etc/bashrc nor in /etc/profile
<gnoo>nice, i've just started using guix and already love it. Especially the idea of graft packages seems interesting...i'll probably try to patch some stuffs
<dcunit3d>hmmm. for me it happens in /etc/profile in the loop "for profile in ..."
<tissevert>that project sounds nice, I started trying to make my config more modular, but not to that point
<excalamus> is the cookbook in texi?
<tissevert>hmmm you're right, it's in /etc/profile
<tissevert>so my issue is, I can't see what is sourcing /etc/profile
<dcunit3d>there's a comment above it that says to arrange it so one comes before the other, & I had to swap the order of them.
<excalamus>hmm, looks like it
<dcunit3d>hmmmm, i can't remember what sources that. it gets loaded very early on. it might be the earliest shell that the system loads. that info is in the bash man pages where it talks about the order of files loading.
<tissevert>so it doesn't depend on my .bash_profile ? that'd be contrary to bash's behaviour
<tissevert>"from /etc/profile and ~/.profile, in that order"
<tissevert>I'm just mistaken about bash's specifications
<dcunit3d>you can test how guix system is modifying those variables at login with the VTTY's. login to one, insert some echo's, switch to another VTTY and login
<tissevert>it works because that's the way it's supposed to work
<tissevert>my profile shouldn't source the system's, the systems sources mine
<vivien>Thank you for fixing 0ad ♥
<tissevert>thanks for the pointers everyone, that helped me clear my false ideas
<attila_lendvai>is it possible to tell git-fetch to retain the .git/ directory?
<attila_lendvai>the build system of the app can invoke git to extract the version from the git tags
<attila_lendvai>s/can/wants to/
<lfam>attila_lendvai: It would break the model where source origins are content-addressed. Because the .git directory is always changing as the upstream project development proceeds
<lfam>You'll have to patch the build scripts
<attila_lendvai>lfam, oh, right, that makes sense, thanks!
<lfam>I wish I had an example for you but I can't think of any... it's a common roadblock!
<jacereda>Is there some service that can execute some arbitrary commands at boot as root? I need to invoke a setpci command in order to make screen brightness adjustment work.
<podiki[m]>is there an example of using the new search-input-directory (or -file) for a #:configure-flags?
<jpoiret>jacereda: yes, boot-service-type defined in gnu/services.scm can be extended with gexps that are evaluated at boot
<lfam>podiki[m]: What are you trying to do?
<jacereda>jpoiret: great, thanks
<podiki[m]>lfam: I need to set a configure flag (meson build) to a directory of an input....I guess I'm failing at where to put the lambda since I need that to grab the "input" label right?
<lfam>podiki[m]: Think of search-input-file as a replacement for `which`
<lfam>Instead, you want to use (this-package-input "foo")
<lfam>Let me find you an example
<lfam>Check commit 2f5b529480f2f32a917a6e99a20d2acdc11bc5dd
<lfam>It uses it in #:make-flags, but "same difference"
<attila_lendvai>lfam, i'm rewriting the build system of the project also (Idris2), so it's not too bad. i have two env variables to set that makes git optional.
<podiki[m]>lfam: thanks! yes, that's what I want, time to bust out a gexp...
<lfam>podiki[m]: The salient points of this example are that arguments becomes a (list ...) and you have to put the value of #:make-flags in a G-expression using #~
<phf-1>Hello #Guix! I'm running GuixSD on a thinkpad t570 but have no sound...
<lfam>podiki[m]: The use of cons* in this example is probably not something to copy
<podiki[m]>lfam: time to put that reading of gexps in the manual to good use
<lfam>It's basically like Scheme quoting, podiki[m]. With a Gexp for quoting, unquoting, and unquote-splicing, but gexp-y
<lfam>And variants for native-inputs as opposed to regular inputs
<podiki[m]>yup, after finally reading the manual it seemed much easier
<podiki[m]>and understanding when it happens
<lfam>pfh-1: What did you try so far?
<lfam>phf-1 ^
<lfam>phf-1: And what kind of environment are you using? The Linux console? An X server? A desktop environment? Wayland? Etc?
<phf-1>guix install alsa-utils, guix environment --ad-hoc alsa-utils; alsamixer
<phf-1>thanks for answering :)
<phf-1>guix install pavucontrol
<phf-1>things seems alright except sound. playing vlc but no sound
<lfam>Do you have any audio files handy? You can get mpg123 with `guix shell mpg123` and then test it with `mpg123 -o alsa my.mp3`
<lfam>The output of that command will be useful for debugging
<phf-1>ok, trying that now thanks.
<lfam>I guess you'll need to use an mp3
<lfam>Anyways, I spent some time fixing some sound issues and that's my test command
<podiki[m]>lfam: got it working, and hooray for me for my first proper gexp usage
<lfam>Awesome podiki[m]
<lfam>podiki[m]: The only extra bit I remembered is that there is this-package-input and this-package-native-input, so make sure to use the right one depending on which type of input it is
<podiki[m]>good to know
<phf-1>lfam: well, that's odd.
<phf-1>it seems ok so far :/
<lfam>So, it works when using ALSA, or at least the ALSA plugin of Pulseaudio?
<lfam>But, not with any of your other programs?
<phf-1>mmhh... I just downloaded some mp3 from the internet archive. Then mpg123 -o alsa my.mp3. The output seems fine: no error message.
<phf-1>but no sound
<phf-1>(the terminal output)
<lfam>The next step is to check alsamixer
<lfam>The "master" output should be turned up and unmuted
<lfam>Make sure to choose the right "card" with F6
<phf-1>that I did too. F6 to choose the sound card and M to mute or not
<lfam>Okay, and then with pavucontorl
<lfam>Similar check
<lfam>I would choose the right Configuration in pavucontrol. For me it's Analog Stereo Duplex
<lfam>Then I go to Output Devices and choose the right Port
<lfam>And make sure it's turned up
<lfam>If that still doesn't work, I'd check `dmesg` for mention of driver problems :(
<lfam>What kind of computer are you using?
<phf-1>I did pavucontrol too
<phf-1>thinkpad T570
<lfam>I feel like the sound should work on a recent-ish thinkpad...
<lfam>I mean, I think it should be supported by linux-libre
<lfam>Can you do `lspci | grep Audio` and tells us what it says?
<lfam>I feel like somebody else had weird issues with sound hardware in recent weeks
<lfam>I wish I could remember a search term for the logs
<phf-1>sorry for the delay, I have to jump around the two computers
<lfam>Does anyone else have any ideas?
<lfam>No worries phf-1
<lfam>Maybe check on this? <>
<lfam>You could also show the full output of `lspci -v`
<lfam>It should give some more useful info
<lfam>At least, the audio section
<lfam>Also, I am now googling things like "Sunrise Point-LP HD Audio linux no sound"
<phf-1>I'm checking the alsamixer thing above
<lfam>It's definitely worth a try
<phf-1>auto mute enabled !!
<lfam>Is it working now?
<phf-1>just looking at the post 2sec :)
<phf-1>Raaa, still no sound
<phf-1>ok well, thank you for looking into it. Will dig around again.
<phf-1>too bad because `guix install ardour' was so smooth :)
<lfam>Hm :/
<lfam>It's weird
<lfam>I would also double-check that your applications (such as VLC) are using the correct output device
<phf-1>Well VLC says: built-in audio analog stereo which matches the pavucontrol data
<phf-1>Well, thank you very much lfam, it was fun to dig around with you :) If I find a solution, I will post it.
<Kolev>I finally got Guix Home to accept my $PS1!
<lfam>Okay phf-1. If you stick around I bet there will be other people who use the Thinkpad T570
<the_tubular>Built:        Wed Dec 31 19:00:01 1969
<the_tubular>I like guix lol
<Kolev>Unix people are baffled by Guix. “Just compile this and that.“ – “That would require packaging the program.“ – “What?“
<nckx>Unix people are easily baffled.
<jacereda>I sent my first patch an hour ago to updating the patch to add a mbpfan service, but I can't see it in the mailing list archives. states it's updated every 15 minutes... can anyone confirm it's lost?
<tex_milan>Hi people. Anyone using cups to print? How did you solve the "unable to locate printer" problem? Cups can find the printer when adding it into configuration, but then when I try to print it tells me this error. Reminds me the same problem I had on NixOS. Some timeout issues... Might be the same problem here?
*the_tubular baffled
***phf-1 is now known as phf-1[afk]
<rekado_>tex_milan: I’m using Guix System with CUPS and a Brother laser printer
<mekeor[m]>i'm using guix system with cups and a kyocera printer. in my system-declaration i enabled cups' web-interface and added my user to the "lp" and "lpadmin" groups. i then used localhost:631 to add the printer. it works like a charm
<lfam>jacereda: It's likely being held for moderation if it's your first message
<lfam>It should be released soon
<tex_milan>rekado_: Do you have any non-standard configuration?
<tex_milan>the problem on NixOs what with avahi and solution was to use mdns4. Not sure if anything applies here...
<jacereda>lfam: ok, thanks
<attila_lendvai>is it a justified/reasonable expectation that /usr/bin/env will be present on future Guix installs? IOW, shall i get into unreasonable struggles to avoid using it?
<lfam>It's reasonable
<lfam>It was considered to be a necessary violation of the functional model in order to help people use shell scripts
***phf-1[afk] is now known as phf-1
<karrq>hmm can anybody help me? I'm trying to use `guix refresh` to update some dependencies from upstream but when I run I get "mkstemp: Permission denied" and `strace` reveals that the denied permission is returned when trying to open the package definition file in the store with RDRW... I'm in foreign distro as user
<awb99_>my init.el files are not being executed by emacs
<awb99_>is there a way to find out why not?
<awb99_>i guess that straight.el package system used in guix is doing something
<awb99_>so This way my init.el file is not executed
<jacereda>awb99_: emacs --debug-init ?
<tex_milan>i got it working. not sure if adding of this "(name-service-switch %mdns-host-lookup-nss)" helped, or it was just a lucky print and get the same problem later again...
<awb99_>thanks jacereda
***Server sets mode: +Ccntz
<phf-1>lfam: I've just rebooted and vlc works now !
***awb99__ is now known as awb99_
***iyzsong- is now known as iyzsong
***sneek_ is now known as sneek
<attila_lendvai>i think using (git-checkout (url (dirname (current-filename)))) as the source of a package used to work prior to the c-u-f merge, but it now fails with: "guix build: error: Git failure while fetching /home/alendvai/workspace/idris/idris2: reference 'refs/remotes/origin/main' not found" -- it shouldn't have any expectations wrt origin and main (the dir holds the checkout of a custom upstream, and a custom branch)
***ns127 is now known as ns12
***marwan8 is now known as marwan
***darosior1 is now known as darosior
***brettgilio3 is now known as brettgilio
<attila_lendvai>and the alternative i tried, git-reference to a local path, also doesn't work
<attila_lendvai>the error is the same
<kiasoc5>im trying to update zrythm which now requires libbacktrace. i added (gnu modules debug) to music.scm but got a long error message.
<kiasoc5>im not sure why there are undefined variables when the other modules are defined already
<kiasoc5>any tips?
<attila_lendvai>err, no, the error is: "fatal: '/home/alendvai/workspace/idris/idris2/' does not appear to be a git repository"
***Inline is now known as Guest1020
***Guest1020 is now known as Inline
***Noisytoot_ is now known as Noisytoot
<jacereda>I've added the following service to fix brightness on my macbook pro: `(simple-service 'fix-brightness boot-service-type #~(execl #$(file-append pciutils "/sbin/setpci") "-v" "-H1" "-s" "00:01.00" "BRIDGE_CONTROL=0"))`. Guix won't boot now, it complains IIRC with a "setpci not tainted" message... Any idea what that means?
<jpoiret>jacereda: if i'm not mistaken, you'd rather have to add a service that extends boot-service-type, not a new boot-service-type
<dcunit3d>why doesn't guix system ship with GCC? if I add gcc-toolchain, should I do so within a profile that is loaded only when i need GCC?
<jpoiret>yes. Many other *nix distributions don't ship with gcc by default as well
<jpoiret>you can also use `guix shell gcc-toolchain`
<jpoiret>to launch a shell with a profile containing gcc-toolchain loaded
<dcunit3d>cool, would you recommend isolating that into its own profile?
<jacereda>jpoiret: oh, so I'm overriding the boot-service-type... so I should use service-type instead of simple-service-type, right?
<jpoiret>if you use `guix shell`, no need
<dcunit3d>i see. thanks!
<jpoiret>jacereda: you're not overriding the boot-service-type, there's already one by default. You have to extend it, see the manual for more info about extending it.
<jacereda>jpoiret: good, thanks for the pointer
<jpoiret>I mean, see the manual for more info about extending services in general.
<jacereda>jpoiret: according to the documentation, `simple-service` extends a service, so I'm lost again, I don't know what's wrong with my attempt :(
<jacereda>maybe I should use `shepherd-service-type` instead?
<jacereda>or rather, `shepherd-root-service-type`
<excalamus>when doing a system reconfigure, I've been seeing a warning about "List elements of the field 'swap-devices' should now use the <swap-space> record". When I look at the reference that the warning gives, it only seems to explain what a swap space is. I already know that. What I don't know is how to update my config to the new syntax.
<excalamus>what I have is (swap-devices (list (uuid "29be12c9-6439-4987-9e46-02ac200761f2")))
<jacereda>excalamus: I think it's (swap-devices (list (swap-space (target (uuid ...
<excalamus>okay, cool, thanks
<excalamus>any tip on how the heck I'd figure that out?
<lilyp>info guix?
<jacereda>I found it in guix.texi, search for swap-space
<excalamus>lilyp, the (guix) operating-system Reference just says "A list of swap spaces"
<excalamus>okay, I see it in there now for (guix) Swap Space
<lilyp>excalamus: *Note Swap Space::
<lilyp>Sure looks like a link to me 😉️
***jonsger1 is now known as jonsger
<jpoiret>jacereda: oh whoops, looks like I was mistaken
<Kolev>jacereda: What is guix.texi?
<jpoiret>can you check the system that doesn't boot, and see if its /boot.scm looks proper to you?
<jacereda>Kolev: the sources for the info manual
<jpoiret>guix.texi is the source for the generated info manual
<jpoiret>you can always look up the manual from the master version at
<jpoiret>or inside your guix install with `info`
<Kolev>Why is everybody writing Markdown?
<Kolev>Grave accent is not a quote.
<jpoiret>you never use `` in shell commands, but you do use quotes very often
<jpoiret>well, you could use `` but rarely in practice
<Kolev>“""“ 😈️
<Kolev>vldn[m]: error in initialization thread: Success!
<jacereda>jpoiret: this is the first thing it executes: `(begin (execl "/gnu/store/1nwlhs58rr7pxpbyi8h9apgb3r0q4c5a-pciutils-3.7.0/sbin/setpci" "-v" "-H1" "-s" "00:01.00" "BRIDGE_CONTROL=0") (begin (use-modules (guix build utils))...`, which looks right to me, but maybe it's too early in the boot sequence?
<jpoiret>boot is executed after the system has pivoted its root filesystem, so things in the store should be available without any issue
<Kolev>Perhaps I should break down and use `code` for the Matrix users.
<jonsger>is there a particular reason why Guix doesn't use something like e.g. 2015-2020 instead of 2015, 2016... in the copyright headers?
<singpolyma>jonsger: what if you need to skip a year where you don't want it to be copyrighted? :troll:
<excalamus>okay, I think I see how I can make sense of the warning hint. I think the thing tripping me up was that I didn't equate records with objects nor understand that they were basically structs.
***robin_ is now known as robin
***phf-1 is now known as phf-1[afk]
<attila_lendvai>argh! the nix sandbox doesn't have /usr/bin/env... and so did i break the idris build on nix. luckily, there's a CI.
<attila_lendvai>actually, it also breaks on guix. there doesn't seem to be a /usr/bin/env in the builder's sandbox
<jacereda`>In case anyone wants to execute some `setpci` at boot, `(simple-service 'fix-brightness activation-service-type #~(execl #$(file-append pciutils "/sbin/setpci"...` seems to work, I don't know why it failed with `boot-service-type` :(
<robin>attila_lendvai, the build process rewrites shebang lines but it may not be early enough in the build process if e.g. building with autotools
<attila_lendvai>robin, the output of idris (a compiler) is a wrapper shell script, and the tests are run using a binary produced by idris (called runtests), and this is that fails.
<robin>attila_lendvai, i use a phase, (add-before 'bootstrap 'patch-bootstrap-shebangs (lambda _ (patch-shebang FILE) ... #t), there's probably a better way
<attila_lendvai>robin, i'm afraid i'll need to do something like that between build and check. thanks!
<robin>oic, you'd want to generate a wrapper before the test phase then, i think
<robin>s/gen.*wrapper/patch shebangs/
<jacereda`>Anyone using isync+notmuch? Do you use a mcron service for that?
<ngz->Here is a part of the Guix manual: "each extension designates [...] and a procedure that, given the parameters of the service, returns a list of objects to extend the service of that type." I cannot make sense out of it. Isn't there a verb missing somewhere?