<singpolyma>It's not a competition :) xhtml5 is part of HTML5 spec
<cbaines>civodul, no problem :) I still need to get the qa-frontpage to look at the blocking information for the branch issues, but yeah, I think having a clear list will help with speeding up making big changes
<reily>I'm having some trouble getting guix home working on a foreign distro with Gnome and GDM, where Gnome and GDM are installed and configured using the foreign distro. Attempting to log in to a Gnome session results in a gray screen for about half a second, and then I get sent back to the login screen without an error message. However, if I login on a terminal and run ~gnome-shell --wayland~, Gnome starts fine. Has anyone else encountered
<reily>this issue? I am aware that some issues have come up with XDG environment variables, but mine seem to be set correctly, and I would think that would impact terminal and GDM launched sessions equally.
<HexMachina>reily: I had an issue like that once that was due to python being installed in my guix profile and it being a different version from the foreign/host distro version. It's a bad idea to install python in your default profile on a foreign distro
<lw>Hello, I'm new to guix. I'm confuse about something. I'm trying to run a `sudo make install` build of st. But, it says I have no harfbuzz installed. I just installed if, although, I can't issue harfbuzz in the shell afterwads. Although, the binary is under /gnu/**/harfbuzz
<zamfofex>I feel like you shouldn’t be using ‘sudo make install’ at all!
<zamfofex>A more Guixy solution is to apply patches to the ‘st’ package and install that. (I use st myself, and that’s what I do.)
<zamfofex>If you’re not using Guix Home, a very simple solution is to install st like this: guix install --with-patch=st=customization.patch st
<lw>Hm, interesting, i just issued `make install` and now it gives i don't have `ctype`, but stopped complaining about harfbuzz
<lw>How would I change the `config.h` of the `st` guix installs?
<zamfofex>You should write a patch file that customizes st to your needs, then apply it with the ‘--with-patch’ option.
<lw>That do make sense to me, but seems a hassle for now (because I'm not proficient with writting patches)
<zamfofex>You can usually use a tool that does that for you!
<lw>Do you think it would be straight foward to take my config.h and write a patch?
<zamfofex>If you have ‘st’ from git, you can write ‘git add . && git diff --staged > my-patch.diff’, then use the generated the ‘my-patch.diff’.
<zamfofex>Otherwise, you can use the ‘diff’ command, but it takes a zillion options (and thus is a bit less straight‐forward to use).
<lw>yeah, unfortunatly, my st is my own repo, and there are no tracks of changes except the head
<lw>I create the repository afterwards, when the build was already complete
<zamfofex>Well, if you cloned st from git (as oppose to, say, from a tarball), the command I wrote above should work: ‘git add . && git diff --staged > my-patch.diff’
<lw>I will try to install the other `ctype` dependency and use `make install` (as it seems using `sudo` makes the command use another foreing environment that doesn't have any packages I installed with guix)
<zamfofex>Hmm, perhaps ‘--with-git-url’ is the actually correct one.
<zamfofex>Note that it’s not usually sensible to want to mix Guix packages with ‘sudo make install’ like you wanted. I wouldn’t say “impossible”, but it’s probably going to give you a lot of trouble overall.
<adanska>Hey guys! I'm trying to add gdm with wayland support to my config, but gdm is already defined as a service in %desktop-services. What is the best way to redefine gdm in my services configuration?
<cbaines>civodul, /gnu/store/npjr640n7l1w9l1zkpx9w8ljias1gl5x-qgis-3.30.1.drv builds for me locally
<evilsetg[m]>@adanska:libera.chat: whoops, I meant to address you above but I misspelled your your name.
<lurdan[m]>hi, I'm trying guix home environment with guix binary installed on debian bullseye, and have some question.
<Guest99>Evolution in guix is outdated by like a year. Where can I submit request to have it updated? Guix version is 3.46 while upstream is 3.48.
<lurdan[m]>I found there are 3 types of guix profile, current-guix-n, guix-home-n, guix-profile-n at /var/guix/profiles/per-user/user/. PATH env is set automatically includes all three profile's latest bin/, so I can exec all packages under which profiles. So, guix command requires to set GUIX_PROFILE env. which I should choose to set?
<lurdan[m]>Another question, is about PAM. I installed swaylock with guix, and it seems that trying PAM authentication using /etc/pam.d configuration, which for debian's pam. swaylock uses guix pam library, so it fails (they differ in modules, config syntax, ...). I wish I can configure swaylock to use guix pam correctly, but How?
<mekeor-not-authe>hello guix :) does it make sense to install podman via guix on a foreign distro (debian testing)? i did so. now, when i run "podman network ls", why do i get this error?: command required for rootless mode with multiple IDs: exec: "newuidmap": executable file not found in $PATH.
<mekeor-not-authe>(background information is that i got a new computer for work, now running debian+guix instead of a proprietary operating system! yippie! :))
<rekado>berlin’s firewall now allows SSH on a different port; we should change that in our configuration too
<civodul>cbaines: ah that's good; i'm reconfiguring overdrive1 just now
<civodul>i wonder if we should set up say monthly unattended upgrades on build machines
<attila_lendvai>i have set up an nftables based rate limit on ssh. i'm not an expert in this, but i'm happy to share as a baseline if someone wants to experiment with it. with a cursory testing it seems to work
<attila_lendvai>civodul, random: i'd call catch-system-error as ignore-system-errors, or with-ignored-system-errors, or anything that suggests it'll be swallowed. (in my emacs i even have a more visible syntax coloring for such operations)
<attila_lendvai>i think it's a general issue to be resolved that there are two distinct, ad-hoc, and inconsistent namespaces to keep track of packages (scheme modules, and the reified package registry).
<attila_lendvai>what is the best strategy if i want to use `ip route add` in the post-up of a wireguard-service? looks like it is not in the path, and i can't use a file-append, because it's not a GEXP (and a #<...> gets silently printed into the generated .conf)
<mirai>or does shepherd really allow "anonymous" services to exist
<attila_lendvai>mirai, the issue is that it's allowed at instantiation time, and it leads to an error much later (in my case at the very end of reconfigure when services are started). the backtrace is not helpful, but luckily it contained shepherd-service-canonical-name that i grepped to get a clue about the underlying issue.
<attila_lendvai>mirai, the instantiation of the service object does not error with an empty provision, nor anything else until the end of reconfigure
<mirai>perhaps a (sanitizer (lambda (lst) (when null? (raise …)) lst)) on the record-type of the service would suffice to fix it?
<cbaines>ngz, like tex-team affects sbcl, but that's also been changed on master
<cbaines>ngz, so if you were to merge tex-team now, that would generate a new unseen derivation for sbcl (because of the combination of the master and tex-team changes), so it and all of it's 1615 dependents won't have substitutes)
<ngz>cbaines: OK. So, do I need to rebase tex-team on top of a green flagged commit and let the CI build again?
<apteryx>civodul: :-) so that's likely the problem/bug, right?
<civodul>apteryx: looking at fork+exec-command, i'm skeptical this can happen; we'd need a reproducer
<cbaines>ngz, I've sort of given up at this point. There's little value of trying to follow a process for branches if that process isn't being followed, and other changes are just pushed to master.
<civodul>apteryx: could you check what you have in ~/.local/state/shepherd/shepherd.log?
<ngz>cbaines: You shouldn't give up :) I think branch are a promising way to process patches, but the community needs time to use it properly.
<cbaines>ngz, you've already rebased several times, so we're just going around in circles. We may as well just stop and join the crowd pushing oversized changes directly to master.
<civodul>cbaines: don't give up! we need to have a discussion all together i guess!
<attila_lendvai>i still think my analysis in https://issues.guix.gnu.org/53580#4 is valid (although i haven't looked very closely on the more recent changes in shepherd). it's not a bug per se, because start GEXP's should not throw errors, but life happen.
<ngz>cbaines: To tell the truth, I have no problem rebasing an n-th time.
<cbaines>I'm hoping that the restructuring in #63459 will make things a bit easier to grasp, as I think it better groups the "what to do with changes" stuff and just references it from the commit policy
<apteryx>OK. I'll get up to speed with this patch when I get a chance to read it carefully, thanks
<apteryx>ACTION must vanish back into the $work abyss
<apteryx>weird, the shepherd bug doesn't go away with a session restart. even starting shepherd by hand leaves me a nonexistent /run/user/1000/shepherd/socket
<pistrie>hi there. Im interested in trying out Guix, but I ran into three issues. 1) is there a reason that GNOME is an older version? 2) how do I use wayland with GNOME? 3) how do i declare my packages? Is the `guix install` command going to add it to some list? I think I would prefer to declare my packages in a file like how you declare your packages in
<VesselWave>lw: next install or try in shell. Just change `build` to `install` or `shell`
<lw>VesselWave: So, `guix build: warning: failed to load '(st)': no code for module (st)`
<lw>./st/st.scm:1:0: warning: module name (my st) does not match file name 'st.scm'
<pistrie>jackhill yes i mean from the standard packages. so in nixos theres a configuration file where you declare which packages you want on your system. If I declare the neovim package and rebuild the system i will have neovim available to me
<lw>VesselWave: guix build -L ~/dotfiles/guix/st st
<lw>Not quite my build I guess, but seems like it partially worked
<johnabs[m]>Hi guys, I'm having some issues with LaTeX, namely the package ninecolors seems to be missing. I've never gotten this error before, and it seems that it should be included in texlive, but it's not present when I run kpsewhich. Has anyone else had this issue?
<VesselWave>lw: You should have a path relative to what you specify in -L. So if your file is ~/dir/dir2/dir3/st.scm and -L is `~/dir/dir2`, you should have (define-module (dir3 st)
<nutcase[m]>Hi, is anyone here happy with his/her flatpak installation on a guix system and able to share it? I have problems with xdg-desktop-portal / dbus, I think. Links in a flatpak app don't open in my browser.
<carmenshea[m]>nutcase[m]: Hello. Flatpak runs fine on my guix install. I have both xdg-desktop-portal and xdg-dbus-proxy. You'll also need to have dbus launching on the start of your windows manager (I'm running sway). My flatpak apps are Firefox, Session Messenger, Thunderbird, and Skype. All run fine.
<mekeor>i once tried one application via flatpack. after finding out the requirement of dbus, it worked fine~ish :)
<mekeor>since then, i have this as last line in my ~/.xinitrc: dbus-run-session -- ~/.xmonad/xmonad-x86_64-linux
<carmenshea[m]><nutcase[m]> "Hi, is anyone here happy with..." <- This is the line I use to launch D-Bus when Sway loads. This is in my .bash_profile [ "$(tty)" = "/dev/tty1" ] && exec dbus-launch --sh-syntax --exit-with-session sway
<nutcase[m]>carmenshea[m]: I launch it with `[ "$(tty)" = "/dev/tty1" ] && exec dbus-run-session -- sway` Do you know the exact difference?
<nutcase[m]>and did you install flatpak, xdg-desktop-portal and xdg-dbus-proxy in your home profile or via guix install ...?
<mekeor>nutcase[m]: comparing "man dbus-launch" and "man dbus-run-session", the first sentence of the DESCRIPTION section differs by dbus-run-sessions also "start[ing] a specified program in that [launched] [dbus-]session."
<carmenshea[m]>mekeor: In this case I'm absolutly NOT an expert. I just copied that line...voila it worked.
<nutcase[m]>carmenshea: my ps says there is a dbus-daemon --system and also a dbus-daemon --session running. I assume, that it won't change much, but I can try. How did you install flatpak from guix repository? Did you install it via `guix system`, via `guix home`or via `guix install`?
<pistrie>Can anyone tell me the correct way to installing packages? On NixOS you can use a config file where you declare which packages you want installed on your system. Then you do a system rebuild and the packages will be installed on your system. Does Guix have a similar system? I've heard that the two are pretty similar in design philosophy
<carmenshea[m]>nutcase[m]: Follow the link that I sent for the flatpak install via guix. From there you'll need to go to Flathub, find the app you would like to get and install using their install command suggestion...then launch using their launch suggestion.
<nutcase[m]>carmenshea: My problem is not installing flatpak apps. I have flatpak apps installed on my guix system. My problem is that a click on a link to some web page in a flatpak app container doesn't open a window of my (non-flatpak) browser
<mekeor>pistrie: yes, you can specify a list of packages that should be available system wide. it's the "packages" field of the "operating-system" record.
<carmenshea[m]>I've got a client coming in...I'll touch base a little later. I will help where I can. Cheers
<mekeor>pistrie: if you want to specify a list of packages that should be available in your user profile, you can either use a manifest.scm or use "guix home".
<mekeor>pistrie: last but not least, you can of course just install packages into any guix profile, e.g. your user profile, with "guix install hello"
<pistrie>thanks! would you be able to link me to some documentation so i can read up on it myself? Isnt `guix home` or `guix install` imperative instead of declarative? Basically what I'm trying to accomplish is that I have an overview of the packages installed on my system
<mekeor>pistrie: guix-home is declarative, just like manifest.scm
<mekeor>pistrie: "guix install" would be a little-more imperative-ish approach. but you can always type "guix package --export-manifest" to get a manifest.scm, and thus, an overview, (including package transformations, btw)
<lilyp>for the serializer kwargs, I can somewhat see the necessity when going to the ini serializer, but I think (serializer-options) might be more neutral in language and possibly broaden the applicability
<mirai>I'll pass on the chatgpt offer :) since it's a SaSS that demands signup
<lilyp>regarding the earlier issue of serializing multiple fields together you might also want to think about whether it's possible to stitch something together using G-Expressions