<zacchae[m]>Is there much functional difference between making an efi-raw, volatile, image that takes up the whole drive, and a normal system install (guix system image vs guix system init)? As far as I can tell, the only difference would be that the image option will make partitions for you, and you would loose the ability to make it LUKS encrypted.
<acdw>hi guixers! I am wondering what i need to tweak to move /gnu/store to say, /home/gnu/store. Due to a small disk for my /, /gnu/store won't fit there. I'd rather not have to repartition if I can help it. Thanks!
<podiki[m]>okay, so depending on what you have going, you may need to stop the guix build service in order to delete/move things (and maybe easiest if you are starting fresh)
<podiki[m]>steps: make the directory you want to use, bind it like `sudo moun t--bind /path/you/want/to/use /gnu`
<podiki[m]>then you'll need to modify the installation script of guix to not check for existing /gnu (since it does exist from the bind mount) and to move to the folder e.g. `mv /tmpdir/gnu/store /gnu`
<podiki[m]>then add it to your /etc/fstab to have in future reboots `/path/you/want /gnu none defaults,bind 0 0`
<podiki[m]>(and I have it running this way on a laptop on top of Arch, no problems, just the install needs those tweaks)
<acdw>honestly i can start fresh. so should i just like systemctl stop guix or something
<acdw>podiki[m]: ohhhh you mean like, totally remove guix, restart
<podiki[m]>well if you have stuff installed, I guess you can just move over your /gnu/store to where you want it and follow those steps
<podiki[m]>(I didn't do that, but I think should be fine, again, stopping the guix daemon first)
<acdw>i don't have anything /installed/ yet, per se... but i can try that
<podiki[m]>there is a guix package for emacs ('emacs-guix' in guix) that is helpful too
<acdw>i saw something like that somewhere... i should see how it helps out
<shoshin>hello! i just installed GuixSD on a linode instance following the recipe in the cook book. i was successful, but there were a few bumps in the road, and i thought i might contribute some additional info to the cook book article. anyone know where i might look to contribute?
<podiki[m]>shoshin: I don't know the details exactly, but I think the cookbook is treated as any other source (submit a patch against the cookbooks source files)
<podiki[m]>or else file a bug report maybe with what you encountered that needs to be changed?
<shoshin>ok. i'm looking at the sources right now and i'll see if i can find it. otherwise i'll email the list.
<podiki[m]>thanks for contributing! (I've been meaning to add to the cookbook too, so that would be a good first step for me too...)
<shoshin>its nice to have the recipes to get started. learning bit-by-bit :)
<shoshin>cool i think i found the source, thanks :)
<lfam>That 2nd link describes how to limit the amount of building you do, but unless this other channel has a build farm, there won't be substitutes for it at all, and you'll have to build whatever packages are defined there
<acdw>podiki[m], thanks! I'm trying it again here, it might've been my fault
<podiki[m]>it has built for me from that channel, but on a guix system
<podiki[m]>(and I've built it before on Arch, but different packaging)
<acdw>well, i'll keep yall posted! and possibly write a comment on that issue
<shoshin>acdw: maybe it doesn't help you, but my first experiment with Guix was on top of my debian, but i now have guixSD on a Linode instance. maybe it doesn't help to have your Emacs on a remote machine but, i'm learning a lot with a machine that doesn't go to sleep and i can leave building stuff
<acdw>shoshin: mm that's not a bad idea tho... i could at least try building the thing and make it like a ... substitute or smethig
<raghavgururajan>podiki[m]: Hi! I remembered that you use stumpwm and wanted to ask if you know how to config timedate on top-right corner and workspaces on top-left corner, like in i3, dwm etc.
<efraim>can I set the GUID on a partition when creating a disk image? where is the partition record defined?
<efraim>the record-type of partition is in gnu/image.scm
<attila_lendvai>this is driving me mad: i'm used to having a clipboard manager, and go back to previously copied texts, but when i select an older entry in the gnome clipboard history, then emacs sees NIL in the x clipboard; (gui--selection-value-internal 'CLIPBOARD) returns nil. any hints?
<attila_lendvai>it's not the internal thing, same for (gui-get-selection 'CLIPBOARD)
<attila_lendvai>hrm, this is probably a bug in gnome-shell-extension-clipboard-indicator, because after selecting one from the history, i get: $ xclip -o -selection CLIPBOARD => Error: target STRING not available
<attila_lendvai>i installed v1.3.0 (i.e. stable)... then does a guix pull get me the latest from the master branch of the git repo? i'm happy for pointers to read. my ultimate goal is to update a guix package, and test it locally.
<attila_lendvai>is it safe to just pull master as my main linux? i thought i'm only pulling the updates to v1.3.0
<attila_lendvai>sorry for all these questions, one last: what's the high-level outline of the workflow for patching a package, and trying it locally as part of my guix system reconfigure?
<apapsch>attila_lendvai: yes, it's master branch. It can be unsafe. The other day I updated my custom guix from upstream and got a mysterious "no code for module (xxx)" error
<apapsch>I tracked it down to somebody forgetting to add a Scheme file to automake config
<attila_lendvai>apapsch, hrm... and is there a way to make it more safe? i.e. pulling from the version-1.3.0 branch? but then it doesn't have any updates since the release...
<attila_lendvai>apapsch, but it's the gnome-shell-extension-clipboard-indicator that is integrated into gnome... i.e. to properly test it i need to update the entire system, not just build the package. i already have a channel set up... can i "shadow" the guix package with my own copy in that repo?
<apapsch>I don't think there is a technical way to make master more stable, it's an organizational thing
<attila_lendvai>apapsch, i managed to update the package, thanks for the hints! now, how do i designate a specific channel when i install a package? the doc doesn't seem to get me all these non-trivial use-cases...
<roptat>attila_lendvai, you can't "shadow" a package, but you could use your package instead of the default one. Like, define a gnome package that uses your package instead of your default one, and use that package in the gnome service instead of the default one
*attila_lendvai goes to eat and thinks about this... thanks!
<roptat>when you install a package with "guix install" or "guix package", it will look for all packages that have the given name and select the one with the latest version
<roptat>if both packages have the same highest version, there's no way to make it choose one over the other
*attila_lendvai has managed to update the package and needs to restart the gui
<attila_lendvai>oh well, it got worse... probably a gnome vs extension incompatibility
<apapsch>attila_lendvai: as the saying goes "out of the frying pan into the fire" :-)
<attila_lendvai>looks like none of the later releases work than what's in guix. and it's persisting the history on disk, which is even worse, i'll need to look into that too. damn, i miss gpaste, i'd prefer not to mess with this, but it's crucial for my workflow...
<roptat>oh, maybe you need the same release series as gnome itself?
<roptat>our gnome is quite outdated now, although there is some work to update it
<apapsch>gnome extensions are not sandboxed and they like to break API between releases
<roptat>it feels like everytime it gets close to be up to date, gnome releases a new version and the people working on the update focus on that ^^'
<apapsch>roptat: how do arch linux and other rolling distros achieve their up-to-dateness? more people, less manual work?
<roptat>more people, less work needed to adapt to their distro
<the_tubular>Dumb question, I'm trying to learn emacs from guix perspective, do I need to bother with ELPA, MELPA and the likes ?
<dstolfa>that's up to you, some people choose to base their emacs setup around guix, some choose to do it through various elpa sources
<ruffni>g'day! i've set up a fresh install of cuirass (with a cuirass-service). now i'm waiting for it to start building. does cuirass only trigger builds on a git repo update? is there a way to trigger new builds?
<leoprikler>for the record, guix has a marvellous elpa importer and unlike gs-elpa that one has been maintained since 2015
<the_tubular>I mean most pakcage that a a emacs noob is going to use are already going to be in the repo right ?
<the_tubular>There's hundreds of emacs package in the repo right now
<dstolfa>my experience with years of emacs (after getting really pissed off many times for my config breaking across emacs version upgrades) is that i actually just want to depend on as few things as possible, and then my configuration can survive for years
<leoprikler>but yeah, Guix should have everything to cover your needs
<dstolfa>you'd be surprised how many things emacs has built-in that is only marginally improved by third-party somewhat unmaintained things in melpa
<ss2>The thing about Emacs itself is, that is has enough to offer even before you need to consider using any plugins. At some point I went all vanilla, and had slowly added several plugins after feeling comfortable with the basics and pulled them in to appreciate the extras that the plugins offer.
<muradm>that happened when i SAK'ed on sway/gtkgreet greeter terminal without login
<muradm>i don't think it is show stopper, wayland/sway is young in under active development, there are many such issues
<pineapples>Well. This issue is not reproducible under the GNU/Linux distribution of the choice of the developer of seatd AFAIK
<muradm>at least i know how to reproduce the case, whenever i will do reboots again, i will try to look at debug logs to identify the root cause
<pineapples>at least when using the version of seatd built from the `noholdtty' branch
<pineapples>however, with this version, it's still reproducible under Guix
<efraim>I ran into the bug about cross compiling to yourself when building system images
<muradm>once we identify the root cause, we can solve it where it will be targeted, be it sway, wlroots, greetd or seatd
<muradm>since this does not happen on pure terminal with seatd/greetd, i tend to think that it should be related to wlroots/sway more than to seatd/greetd, but i'm not sure at this point of course, just speculating
<pineapples>My bet is on GNU Shepherd because, according to the system logs, it terminates `seatd` on every SAK attempt even though the latter doesn't have a file descriptor referencing `/dev/console' open
<pineapples>muradm: Hmm.. Actually, months ago when I was still troubleshooting this, the seatd developer told me that the virtual console interface (again: or whatever it is called) would be improperly handled by wlroots on unexpected Wayland session shutdowns but, if I'm correct, the fix on the wlroot's side landed in 0.14.0
<muradm>this is all because technically these processes start on tty1 which is default on boot
<muradm>with new greetd-service-type, you will be able to specify default terminal like "terminal-switch #t"
<muradm>then you will be able to set which terminal should be activated initially
<muradm>why SAK is going on "by fd#<N>" should be investigated separately, and addressed somewhere else i beleive
<pineapples>Hmm. You've got right. Also, SAKing on TTY2 didn't affect the Sway session on TTY1. Anyway, shouldn't we take our findings to the developer of seatd and confront him with them? I really can't recall him claiming this is the intended behaviour unless my memory is failing me again
<muradm>since it is not only seatd dying, and death of seatd should nothing to system, but shepherd dead will "freeze" system in the way that it is working, but stopped services are not getting restarted
<muradm>you can ssh to system if sshd remains up for instance :)
<muradm>but for me, sshd, shepherd, bluetooth everything started by shepherd is dying on tty1
<muradm>may be just use another tty as your main tty, and leave tty1 alone in terminal mode
<pineapples>muradm: Have just tried that: left tty1 alone, logged to my user on tty2, started Sway and then SAK'd it; this led to the system "freezing"
<muradm>pineapples: sudo more /var/log/messages | grep SAK