<singpolyma>opalvaults: usually DWM, I'm experimenting with others as part of my exploring, but nothing beats DWM for out of the box experience
<opalvaults>raghavgururajan: that's on my radar. very cool WM.
<opalvaults>singpolyma: I used to just pull LukeSmith's DWM config since it had a lot of things set up for me, but honestly Gnome has tiling and is super minimal visually these days so I like it. Material shell is great, for all its quirks,
<rekado_>civodul: yeah, been stuck on this treadmill for much too long.
<singpolyma>I ran all minimalist for years and am now pivoting to heavy bloat for everything, because I want my daughter's intro system to be as malleable/scriptable/accidentally programmable as possible
<rekado_>I keep finding things that need fixing...
<rekado_>and then a merge happens and there's even more...
<raghavgururajan>There is way for software to have as many features, but not being blot. Extensiblity and Modularity. Any number of features can be added by extenstion. Any those extensions can be modded in or out.
<singpolyma>I mean, vim can do that with read ! I think it is, but still nice
<jgart>the acme commands above allow me to extend to any language in my environment. That's what I love about it
<jgart>I like the terseness of the implementation in vis
<jgart>It's cleaner and feels more first class. It was thought as to how the editor would function at its core
<singpolyma>Yeah. I was about to downshift to vis when I suddenly decided to rocket to emacs instead
<patched[m]>Any way to access .git when the source origin method is git-fetch? Cmake (thinks it) needs it to fetch submodules. Is this easily fixable, or does the build system need to be modified?
<raghavgururajan>patched[m]: Yes, there is an option for git-download to recursively fetch sub-modules/sub-projects. But it is highly avoided. Generally, we package the sub-modules/sub-projects first as dependencies.
<jgart>What do people think of using repology API as a alternative backend to check for updates on packages in guix?
<patched[m]>raghavgururajan: Hmm, I think I'll have to restructure the project structure a bit then if it's to work with guix I think. Because the project is git-aware, cmake looks for .git, can't find it, and concludes it is not in git repo and exits.
<raghavgururajan>patched[m]: The recursive download is for bundling and vendoring source-code, which is very bad for security, reproducibility etc. Thats why we explicitly unbundle/unbundle stuff. This is quite normal in guix. You can look for examples in guix repo.
<raghavgururajan>patched[m]: Personally, I did them in linphone.scm and telegram.scm.
<jgart>In an ideal world I'd prefer to run Guix System on hyperbk kernel than on linux
<florhizome[m]>Well I would need a bsd -nonguix then but I find it awesome that they work towards that.
<patched[m]>raghavgururajan: It seems like a good idea. I think I'll restructure the project to allow for guix packaging. Cmake specifically complains about not finding .git (which I assume is omitted for reproducibility)
<raghavgururajan>patched[m]: Sometime cmake script checks for dependencies in the system (build-environment) and if not found, tries to fetch via git. You could try packaging the dependencies first and adding them as inputs to the main package.
<jgart>I think getting guile/guix to work on alternative kernels should be high priority for the future
<jgart>oh, think I spotted the issue with the above syntax
***lukedashjr is now known as luke-jr
<patched[m]><raghavgururajan> "patched: Sometime cmake script..." <- It doesn't, it's a personal project :^) the cmake code is pretty hacky because the focus was on getting cmake to work. So this should be a good reason for cleaning it up
<apteryx>rekado: sorry for not seeing this earlier, no objection for me, although we've lost like 20% covereage since, it seems; reading the backlock it seems the problematic commits should have been reverted, so I'm not sure why it's still at that
<apteryx>rekado: if we're going to need to go through another mass rebuild, I'd like to know so that I can slip 52269 in, and perhaps a patch to xorg.
<lilyp>raghavgururajan: you now when you'll build it, there's a stupid ld error
<rekado>apteryx: a big chunk of rebuilds is due to the php upgrade. Php has since been removed from the inputs of libsoup (better now than later) and there have been changes to librsvg to avoid other problems.
<rekado>so we won't be able to avoid this round of rebuilds.
<rekado>at least it no longer involves the rust bootstrap.
<rekado>would be nice to have a recursive "guix challenge" that takes references into account
<zimoun>is it possible to just display the ’phase’ starts and ends? Which verbosity level?
<civodul>mothacehe: re CI, thanks for the clarification!
<civodul>mothacehe: the publish issues seem to be gone now? or at least i don't recall experiencing it lately
<civodul>GC performance has improved but we need to keep monitoring and to get a breakdown of time spent in each phase (finding roots, traversing the db, rm -rf /gnu/store/trash, and "deleting unused links")
<efraim>Would it be safe to deduplicate file system extents in the store?
<nckx>You can. That's what ‘live’ means. Have you booted the installer? You can switch to a text terminal with Ctrl+Alt+F3.
<nckx>From there, assuming you have enough RAM to contain new packages or start the cow-store service on a mounted writable partition, you can install whatever you like. Possibly reconfigure? I haven't tried that.
<nckx>That's the only live system we offer. Maybe others offer others with more packages pre-installed.
<bung6[m]>How do I know if the system is compatible with hardware?
<nckx>If it ran Trisquel, it should run Guix System just fine. I also recommend having a few 10s of GiB free for /gnu/store. That's not a minimum at all, but it makes working with the system whilst getting to know it much easier.
<nckx>If it didn't run Trisquel or some parts need non-free firmware, it might not run Guix System well or at all.
<civodul>mothacehe: i think Cuirass commit 6dcf2f65cea920b9b1c265de3e2b0abe0048a08e is not quite correct because 'catch' is too high
<civodul>it should instead wrap individual 'register-gc-root' calls
<vivien>I didn’t have any other issue, and having static networking would help me a lot :)
<awb99>pine64-plus-installation-os .. will this installer work for the "old" pinephone? There is the pinephone-pro also, perhaps the plus means pro ?
<mothacehe>civodul: i'm not sure to follow you. The derivation-path->output-paths can possibly raise an exception if drv doesn't exist. So the exception need to be ignored at least at register-gc-roots procedure level, right?
<samplet>civodul: The PoG reports are back up. Thanks for the heads up!
<zimoun>samplet: some linux-libre related things had been recently added to sources.json but I do not think nixguix loader ingests it. IIRC, nixguix loader filert out based on extensions.
<samplet>We also changed to running the linux-libre deblob scripts locally, too.
<samplet>For PoG, that means that we are checking the upstream linux sources instead of the linux-libre sources. In a forthcoming report, I have data on the preservation of the deblob scripts (and other plain text sources).
<attila_lendvai>in a gexp i can write #$(file-append some-package "/bin/foo"), but how can i refer to a non-default output of some-package?
<attila_lendvai>i can use (string-append #$geth:clef "/bin/clef"), but that happens at runtime. i'd prefer the former.
<civodul>attila_lendvai: currently file-append doesn't let you choose a specific output
<civodul>roptat: we need Translation of Guix reports! :-)
<attila_lendvai>civodul, thanks! i'll settle with the latter. but then... does it make sense to package several binaries into different outputs? even though these binaries are rather different... (geth -- ethereum node, clef -- a key managemend daemon, evm -- the ethereum vm, etc). but still, does it make sense?
<civodul>mothacehe: it could be one of OUTPUTS that doesn't exist, in (for-each ... (derivation->output-paths drv))
<notmaximed>maybe file-append can be extended with an optional #:output "clef" argument?
<zimoun>samplet: I do not think the deblob scripts are preserved, yet; at least no ingested yet via sources.json and not reachable IIUC. Some discussions were floating around to move to git-fetch; which would easy both ingestion and lookup, IMHO.
<notmaximed>winning-lusers: looking at the 'l', it appears to be a symbolic link (which is fine), so you might need to check the permissions of the file it points at
<notmaximed>(also, maybe check the permissions of the parent directories?)
<jpoiret>winning-luser: can you do a paste of `systemctl cat guix-daemon.service` as root?
<mothacehe>mbakke: thanks for the django/ganeti fixes :) the ganeti system tests are repaired
<mothacehe>patchwork is still broken though, any taker?
<winning-luser>notmaximed: the real file's permissions: -r-xr-xr-x. 1 root root
<jpoiret>any eta on c-u-f, are there any remaining blockers?
<notmaximed>Due to technical reasons (world rebuilds), the ‘standard’ cmake package cannot be updated directly, but you could define a cmake-next variable with version 3.16.6 of cmake, and use that in your package definition.
<notmaximed>res0Nanz: is your guix up-to-date? I have version 3.21.1.
<acrow>Sadly -- I am confused about this oughta be basic home configuration detail.
<tex_milan1>Hello, I have bluetooth service enabled in system config, autostarting it, but when I run Bluetooth Manager as a user or root it complains about org.blueman.Mechanism not provided by any .service. Bluetooth works. Any ideas?
<acrow>tex_milan1: Yep. I see that too with xfce but it appears to be extraneous because it works.
<tex_milan1>@acrow Yeah, but really very annoying to see it every boot... Also what bothers me is it is not (manager) started automatically. NetworkManager applet is started automatically for example.
<tex_milan1>Also see that a2dp-sink profile connect fail due to protocol not available. Do you see it too?
<tex_milan1>Dec 6 20:39:36 localhost bluetoothd: src/main.c:parse_controller_config() Key file does not have group “Controller”
<tex_milan1>Perhaps guix bluetooth service generates invalid config? What is "Key file"?
<acrow>Hmmm... I agree and have struggled with it but not cracked it. Among the complications that I've encountered are that I run linux-libre on a machine with integrated bluetooth that is not supported. So, I use a ZEXMTE USB bluetooth adapter instead. I'm not certain that the error is not due to kernel mischief surrounding an incompletely supported bluetooth adapter. Could you have a similar complication?
<lfam>I do not believe that NixOS uses linux-libre by default, although I do think it is available
<Myrcy>that was the situation I last heard of with NixOS as well
<raghavgururajan>tex_milan1: We cannot provide support for stuff related to vanilla kernel, for ethical reasons. If you are facing something regarding bluetooth-stack, blueman and linux-libre, feel free to ask us.
<tex_milan1>i understand. and this has nothing to do with kernel. it is isssue in bluetooth-stack
<raghavgururajan>tex_milan1: I am afraid you'll have look at the source code of bluetooth-service-type for options.
<tex_milan1>yeah, going to hack guix. that is what bring me here, I was using NixOs, great and stable system, perfect desktop, but I wasn't able to learn their DSL... Guille is extremely simple comparing it to it.
<sneek>civodul, RhodiumToad says: re. (aif), it's worse than that, it also doesn't work at all if used inside another macro, e.g. (define-syntax-rule (foo bar) (aif bar (display it) (display "no"))) can fail with 'it being unbound
<sneek>civodul, RhodiumToad says: you're correct that a syntax parameter is the correct solution of course
<acrow>I've tried to emulate 10.9.2's example, using "guix gc -d 1m" lazy way.
<attila_lendvai>tex_milan1, if you changed code in the guix repo, then you need to commit it, set up channels that it points to your local repo checkout (as opposed to the official repo), then guix pull it, and only then guix system reconfigure
<attila_lendvai>tex_milan1, you'll need to add your pgp key to the keyring branch, add a channel-intro commit, and whatnot. it's not trivial, but once it's set up, it works. alternatively you can use qemu to test your changes, which might actually be simpler.