<sughosha>Has anyone tried plymouth in Guix? It is packaged but I don't know how to make it work.
<sughosha>If anyone is using Plymouth please let me know how.
<mange>Looking around the internet, it sounds like we'd need a system service for Plymouth. Nobody has contributed one, nor have I been able to find anyone who has written one, so I think you might have to write your own service if you'd like to use Plymouth.
<eliza>ty! i've been slowly losing my sanity trying to migrate my nixos+home manger config to flakes so i thought i'd give guix a chance lol
<abrenon>that's great ! I know a (very) little bit about nix but I've never tried flakes so I won't be able to give much feedback on that but enjoy guix
<abrenon>do you know there's a home manager in guix too ?
<futurile>I'm trying to use `guix refresh` to look for packages that I can update. Is there a way to tell that command to only check a section of the archive? I was hoping that `guix refresh --manifest=gnu/packages/shells.scm` would work but it clearly doesn't like the package definitions as a package manifest.
<eliza>abrenon: i've heard vaguely of it, but i'm not sure how it compares
<oliverp>Hm so it was true pleasure attending the Guix Online Summit during the weekend :)
<oliverp> does anyone has any idea about where the wonderfully updated roadmap was published?
<phf-1>Hello Guix! I have a question regarding Cuirass. Let `pkg' be a Guix package. Assume that `pkg' needs a service (e.g. a database) when executing the tests. How to setup the environment and `pkg' so that this service is available when executing the tests?
<mothacehe>Hello phf-1, Cuirass is just a glorified derivation builder. If `pkg' needs a service when running the test, you need to start in manually in the test phase I guess.
<sneek>Welcome back mothacehe, you have 2 messages!
<sneek>mothacehe, apteryx says: no ETA on rsync, but it's currently at (xfr#32698611, ir-chk=955547/33654336), so it unless it scans and adds yet more directories bumping up the total files, it should be done somewhere about somewhere tomorrow
<sneek>mothacehe, civodul says: hi! your talk videos are missing from fosdem.org, perhaps you need to approve them or something?
<mothacehe>phf-1: for instance, if you have a look to the cuirass package definition in (gnu packages ci), you will see that ephemeralpg is setup to provide a pg database during the tests.
<phf-1>mothacehe, So it's necessary to add e.g. postgres in the inputs field for the tests to run? It will make the package quite large I guess, isn't it?
<sughosha>Hi, I am about to configure `guix home` for the first time. As I read in the manual, the profile would be `~/.guix-home`. Will I be able to delete `~/.guix-profile` if I suceed with the home profile?
<abrenon>I would imagine developers to watch a particular package or set of packages they are familiar with or need for their work, but I don't see why in general that would match a whole package module of guix
<abrenon>if there's a way to automatically extract the list of its packages from module in guile, I don't know it, but should I really need it, I suppose I'd write a regex based on the (define-public …) statements
<abrenon>there would possibly be a couple special cases to handle, but I guess that's still better than maintaining a separate list of those packages within a text file
<acrow>efraim: Thank you for your comments. Changes have been submitted to rhino. :)
<phf-1>I guess cuirass should run as a specific user... which one?
<tschilptschilp23>Hi Guix! I'm literally unable to update root user's guix, or do not understand the concept. Is it possible that without setting root user's PATH after 'guix pull' it will stay with the initial (?) commit forever?!
<gnoo>tschilptschilp23: why not use your user's guix? and no, after doing `guix pull' , it will update the commit but guix package -u will update the packages
<podiki[m]>tschilptschilp23: are you on guix system? many (most?) of us don't bother updating root's guix as you just use the user one for everything
<gnoo>why doesn't guix have mirrors for packages ?
<nckx>Guix has historically been ‘harder’ to mirror for operators who expect to simply point rsync at a server and be done with it. Some work has been done in that direction, but I think SJTUG uses custom software instead. ‘why doesn't guix have mirrors for packages ?’ is a loaded nonsense question.
<tschilptschilp23>podiki, gnoo: yes I'm on guix system, and what you suggest is how I actually work on my machine ;) But -- if I create a vm with 'guix system image [...]' it uses the 'not-updated' root commit (and it does not seem to respect setting root user's guix PATH). This ends up in having a vm booting with the 'new commit' (from the user who created it), but seing an older guix version initially. This is a little frustrating, and therefore I try
<tschilptschilp23>to 'update' root user's guix (without setting a PATH), as the commits of that one and the one set in the VM map 1:1.
<nckx>tschilptschilp23: ‘sudo -i guix pull’ should do it right, as should ‘sudo su -’ and running ‘guix pull from the shell it gives you. The problem is that ‘being root’ is a very complex concept. You can have root privileges without ‘being’ root, which is what ‘sudo’ does by default (equivalent to ‘sudo -E’), and things like HOME will still be set to /home/tschilp.
<nckx>It's not that complicated. ‘sudo -i COMMAND’ should be equivalent to ‘sudo su -’, ‘COMMAND’. ‘sudo su -’ and ‘su -’ are identical, but the latter is a bit trickier since you'll have to enter root's password instead of your own, and root might not even have one.
<podiki[m]>or you always forget root's password because you used it exactly once, when setting it :)
<podiki[m]>they were (or at least ones I was there for), but might be a bit until they are available
<podiki[m]>also not sure if they will be posted somewhere or just in the bigbluebutton instance?
<tschilptschilp23>nckx, podiki: In my desperation I now did 'su -', 'mv .config something', 'exit', 'sudo -i guix pull'. Now 'sudo -i guix describe' or 'su -' followed by 'guix describe' make me happy. But 'su', followed by 'guix describe' still makes me cry...
<nckx>su is not a user, it's a command, and you're calling it in a way that gives poor results. We're missing why you so sorely want to ‘su’ in the first place.
<nckx>‘su’ is not a nice environment compared to ‘su -’.
<nckx>And it's certainly not ‘root's environment’.
<nckx>It's a hell-mix of… things. Run ‘env’ in both ‘su’ and ‘su -’ and diff the results, or just look at ‘echo $PATH’ in both ‘su’ and ‘su -’ shells to see how badly they differ.
<nckx>tschilptschilp23: In (or outside of?) these guix vms, what are you using ‘su’ for and are you sure it's the right tool for the job?
<nckx>…and if you don't mind me piling on the questions: why? 😉
<tschilptschilp23>What I'm trying to say -- if I create a qemu-qcow2 disk using 'guix system image' on an updated guix system, and afterwards start this built image with qemu, the 'guix describe' returned to the ssh-d in unpriviledged user (inside) does not point to the commit the 'builder' (outside) sees on his/her profile, but to the one outside only sees after issuing 'su' followed by 'guix describe'.
<tschilptschilp23>Why? I want to use this feature because I find it terryfying attractive, but like this I cannot properly use it ;)
<roptat>that's because the guix that's in the qemu is the one that's describe in a package definition, so it can't point to your current guix, but only to an earlier revision
<roptat>that's something we want to work on though, because it's annoying
<nckx>It definitely is (there are/were even cases where there were 2 nesting dolls, and one could get a guix that was 2 updates out of date).
<nckx>tschilptschilp23: Isn't that just coincidence?
<abrenon>roptat: what's the roadmap for creating the subtitles for the videos ?
<tschilptschilp23>roptat, nckx: and yes, if I knew the config ahead of time, I wouldn't have to hop into that machine, play around inside and bother you guys with my 'su' problems :) Thanks for your input
<abrenon>I'm a bit burried within work this week but I hope to have more time from this weekend on
<nckx>tschilptschilp23: Since I do everything from a local ~/guix checkout, what I've done in the past is make a local commit updating the ‘guix’ package to the latest upstream commit, pull, and deploy. It's manual and tedious though. Also benefits from keyring privilege.
<nckx>I wonder if there are cases where --with-commit=guix=foo works around that…
<nckx>podiki[m]: I never realised pci.ids was a bundled database (by the same author, but still)! I think it makes sense to create an uncompressed pci.ids package on master, make your packages use it, and update pciutils to do the same on c-u. WDYT?
<nckx>On ‘modern file systems’, manual .gz compression won't win you much anyway.
<abrenon>nckx: : D and so is the time I spend writing this article…
<jpoiret>tschilptschilp23, nckx: I've been working on making current-guix work in (hopefully) all cases so that we're able to replace the guix package with it in the default configurations
<jpoiret>also, currently, the nested dolls issue happens when you use the installer, since when creating a guix iso you get the N-1 version, and that version when running `guix system init` gives you the N-2
<podiki[m]>...I don't know what that means but sounds fancy/complicated :)
<apteryx>nckx: I was thinking pciutils must offer some API to get at its data? so that whether it's compressed or not is not a concern for its users
<podiki[m]>so in that case we'd want to keep a version of pci.ids for pciutils, maybe freezing that on core-updates when it gets frozen in the future? (or whenever CI building starts for it)
<podiki[m]>Arch has uncompressed pci.ids for what that's worth; the few packages I have that specifically want that file don't seem to handle the .gz version (did not investigate how exactly it is loaded though)
<podiki[m]>apteryx: I need to look, but I think some software wants to grab the pci.ids directly, rather than I would guess parsing lspci or something? just guessing though
<nckx>I did not read your mail as ‘use an API nicely’, rather just ‘read the file directly’.
<helaoban>hello guix, I'm running into an issue when trying to adding the global channels file (/etc/guix/channels.scm) declaratively via an etc-service-type service
<apteryx>rekado: hmm, I'll feel bad if there's an issue that will forces you to go to the MDC tomorrow :-) we can wait a bit later this week
<apteryx>when your energy supply has been replenished a bit!
<helaoban>on the latest pull of guix, the /etc/guix directory is already populated with some files. trying to add a file to /etc/guix via etc-service-type errors out with "error: symlink: file exists: "/etc/guix"
<helaoban>is adding to an /etc subdir not supported via etc-service-type if that directory already exists?
<helaoban>apteryx: re patch 49610, that's exactly what I'm trying to do.
<podiki[m]>PotentialUser-95: I have multiple profile loading in my .profile (as outlined in the cookbook), but not much else that I can think of. I'd like to make my prompt show when I'm in a guix shell environment, but have been lazy
<balbi>hi, is it possible to define a package in `guix' which doesn't support a particular architecture? For example, define a package that won't build for aarch64. How can that be done? Thank you
<podiki[m]>balbi: yes, there are some examples, use (supported-systems '("x86_64-linux")) for example, so it only is for that
<podiki[m]>there's probably an easy way to do the inverse, just what is not supported, but don't have an example handy
<apteryx>helaoban: testing changes is time intensive; if you have an interest in it, I can only encourage you to apply it locally and trying it, and reporting your success. This will give more confidence to those who have to apply it.
<apteryx>or catch problems that need to be resolved beforehand :-)
<helaoban>apteryx: np, I can do that. Is a simple reply to that patch thread saying "this works for me" enough or is there a more formal process for that?
<apteryx>podiki[m]: can you give a spin to your mangohud package with the new imgui package?
<apteryx>podiki[m]: yeah, pciutils provides a library to do lookups, e.g. char *pci_lookup_name(struct pci_access *a, char *buf, int size, int flags, ...)
<apteryx>so we could open an issue with mangohud suggesting them they use it instead of reinventing the wheel
<podiki[m]>apteryx: I had tried before for mangohud, but needed a change to find the library (it tries with cmake or pkg-config files), so I'll have to see what change is needed, probably just need to tell meson specifically where to find it?
<podiki[m]>corectrl is another package that wants just pci.ids (I have a package for it but not submitted yet)
<podiki[m]>oh, I think meson you can use find_library with explicit 'dirs' argument
<apteryx>there's no formal process, but when we as a reviewer are confident that both the code and behavior is OK (reviewed/tested) we often leave a LGTM to let the author/committer know we trust this to be good to merge to the best in our opinion.
<podiki[m]>anyway, I'll figure that out, and does the pci.ids change from 54069 sound like what we'll do?
<podiki[m]>so I can sort out the imgui version/build for mangohud, and then use the new hwdata package proposed if that's what we're thinking (with pciutils change for core updates to use the more up to date pci.ids from hwdata)
*podiki[m] off to run (literally) but will continue the hacking later
<pranavats>Hello. I really need some help recovering a guix system installation. I think I somehow damaged my luks partition. I had an LVM on Luks partition, with a single encrypted physical volume. I wanted to install devuan on a logical volume I created in the omly volume group on that physical volume. I opened the devuan installer and at the manual partitioning step, I could not find a way to decrypt the luks part
<pranavats>ition to choose logical volume as root. I clicked on "configure encrypted volume" option. It asked me if I was satisfied with the current layout before continuing to configure it, and I continued with a "yes". But I never wrote any changes to disk. And aborted the installation. Now cryptsetup errors out with "not a valid luks device" when I try to open it. And obviously grub cannot boot into my guix system
<pranavats>I just wanted an opinion on diagnosing the situation before trying to recover (using photorec) the backup of that header from an old flash drive which has since been formatted.
<pranavats>apteryx: The partition is still recognized as lvm2 physical volume by gparted.
<pranavats>I wonder if there is any way to make a copy of the damaged header.
<pranavats>apteryx: Or maybe photorec can recover the header?
<pranavats>jpoiret: I wonder if you have any suggestions to help with my situation.
<PotentialUser-86>I have a relatively newbie question: what could probably be the reason that my system cannot login with the normal user account. I mean when I try to login from tty or graphical interface, after entering my password, the whole screen "refresh", and I'm being asked for username again. root does not have this problem. roll-back does not help. The
<apteryx>it'd be nice if 'guix style' would print a rationale of why it did nothing w.r.t. input simplification
<apteryx>I'm looking at "./pre-inst-env guix style --input-simplification=always gnunet", for example
<feng>Hello, how to avoid input password when run xfpm-power-backlight-helper
<shcv[m]>any idea why my wireguard service isn't auto-starting / how to make it auto-start?
<shcv[m]>also, how to prevent my guix-sd from going to sleep?
<podiki[m]>any meson users here? failing at what should be easy, adding an include path to a package definition (originally it was a subproject, so I'm patching that to use the package input)
<tschilptschilp23>PotentialUser-86: if it is a completely new system, it might help to run ~sudo herd start user-homes~. I also experienced this once after a fresh install -- turned out that my user-home had not been created, which led to the effect you describe.
<disposabled[m]>when I try to start guix-daemon, I get, "guix-daemon.service: Failed to execute command: Permission denied"
<podiki[m]>apteryx: seems the imgui version we have now isn't linking properly for mangohud, I don't think it is the version (I tried with 1.81) but something with how it is built?