<stefanX2ovic>I am using GuixSD with the latest 239.1 version. I plan to send update patch to guix-patches when the next version is released, because I need recent version for wlroots (Alpha), sway (Beta), and mako.
<ng0>stefanX2ovic: wingo used to do that, but upstream development has moved to github.
<ng0>i don't know if "#guix on irc.freenode.org" is still appropriate
<stefanX2ovic>ng0: I am aware of wingo's involvment. But I am wondering whether to make github account for this simle bug.
<ng0>pick a high frequency contributor of the elogind repo and send them a patch or message?
<ng0>or maybe whoever looks like the maintainer these days
<ng0>since it is picked from systemd the "contributors" list in github might be misleading
<apteryx>is there a way currently to duplicate my current guix version to another machine?
<apteryx>I tried guix copy, but you still have to guix pull thereafter and I'm not convinced of the gain.
<roptat>apteryx: you need to find you current guix version and send it to your other computer with guix copy
<roptat>then you run guix pull, but it doesn't have to build anything since you already sent everything
<roptat>(run guix pull --commit=... to get the exact same commit as your first computer)
<apteryx>roptat: I did guix copy --to=my-other-machine realpath ~/.config/guix/current, and it did copy a bunch of things, then I ran guix pull --commit with that commit but wasn't sure if it made a big difference. I should time it!
<lsl88>roptat: I had a similar problem before, but it is weird, I tried with the commands that demotri mentioned by that time and I don't know why it is still not getting the latest version. Maybe I should ask about that. When I wrote in guix-devel, it worked for me then