IRC channel logs
2026-06-08.log
back to list of logs
<PotentialUser-69>Hello, is there a way to clean up the guix shell profile cache under /var/guix/profiles/per-user/<user>/profiles before the automatic 7 day expiry? <graywolf>PotentialUser-69: `rm' command works fine <graywolf>ieure: the issue was reported by someone else, than hidden (or deleted?) after some time, and I was not sure how to stay part of the conversation <ieure>graywolf, I see. I don't know, then. <graywolf>anyway I will just leave it be, install a stopgap to my tree and wait for security team to sort it out <apteryx>cbaines: fyi, the singapore mirror appears to average at 5 MiB/s, peak around 8 MiB while downloading a large file (qtdeclarative-6.9.2-debug 867.8MiB) from Japan on a 1gbit connection. <yaircul>So I can use a mirror istead of ci or bordeaux servers? <apteryx>trev: fyi, commit 83369786f95 adds emacs-magit-difftastic <apteryx>I'm trying it now, it looks useful (but very slow, so maybe enable it only when needed by manually M-x magit-difftastic-mode) <mlxdy>Is it possible to run appimage on gnu guix? <apteryx>trev: "difftastic is used for display only — git's own unified diff stays the source of truth for every applied patch"; I guess that's why it doesn't improve my use case <optimal>at the moment it lives in a single file on the repo, selectron.scm, and i've tried to comment things <old>optimal: I think you want to put this in #guile :-) But thanks I'll take a look! <apteryx>trev: this helps the most so far: diff --anchored='(define-public' <apteryx>err, git diff --anchored='(define-public' <apteryx>and now that this is understood, switching algorithm to histogram does as well as git diff --anchored='(define-public' <oliverD1>Hi I was just wondering is there a way to customize guix so that when the guix package -u command runs out of space it garbage collects instead of terminating. I should really get a better laptop but is there a way? <bdunahu>there might be a better way, but maybe you could write a script and make use of exit codes? <bdunahu>it probably depends on if the exit code for no space is unique <apteryx>packaging node.js stuff means packaging one function at a time, in many cases ^^' <tobtoht>is there any way to disable the default profile hooks? <PotentialUser-87>Hi, I am currently trying to learn about GUIX OS. Are there any ressources you'd recommend, that deliver GUIX - knowledge bite siced? I'd be very interested in literature aswell as videos. <kratacoa>PotentialUser-87: you might want to also look for Futurile's blog posts <kratacoa>or SystemCrafters videos if you prefer that format <kratacoa>But generally the manual should be good as an introduction on its own <PotentialUser-87>Cool! Thank you! i'll look into the cookbook and watch system crafter's videos at home. The manual is a bit tough for me, especially as english is only my second language. <identity>PotentialUser-87: the manual is available in, at least, Simplified Chinese, French, German, Spanish, Italian, Brazilian Portuguese and Russian, with the cookbook having an even longer list of translations <apteryx>do we have an API to get a list of tags in from a git repo? <apteryx>I need to guess otherwise for an importer, which is not nice <identity>apteryx: maybe check what the generic-git updater does <apteryx>good idea. I seem to recall it maintains a cache of checkouts <apteryx>I see a private (define* (get-tags url #:key prefix suffix delim pre-releases?) in (guix import git) <stephen0>Is there a method for having nix packages declared in the guix home config? <stephen0>Anyone using the nix home manager on their guix system? <stephen0>All my neovim/treesitter/rtp/parser issues disappear if I nix-shell -p neovim. <ekaitz>stephen0: i have neovim and treesitter working pretty well in Guix, no nix involved <stephen0>runtime path in neovim -- the tree sitter issue I'm having is related to various parsers that are all in the runtime path not being found <stephen0>ekaitz: do you use lazy nvim or is everything declared in your home configuration or ..? <ekaitz>stephen0: I have the grammars installed via guix <ekaitz>ACTION has to go, but will be back soon <stephen0>I had tried that, but maybe there were remnants from the previous attempt in the way... <stephen0>My issue seems to be with nvim-treesitter, which I only have as a dependency for other plugins. Maybe I can do without those plugins and just rely on vim-treesitter. <stephen0>coincidentally I only sacrifice org mode <ekaitz>stephen0: nvim-treesitter is archived, and it only manages installation if I recall correctly <stephen0>can't seem to trick it into finding org -- added tree-sitter-org to system packages, which is where neovim is, but checkhealth in neovim doesn't see org as installed <ekaitz>stephen0: did you guix pull recently? <bjc>i'm no longer able to build gcc-13.3.0 on hurd because runpath validation is breaking for some reason <bjc>(native build, not cross) <randomguixuser>Hey folks, last time I asked about installing a Chromium-based binary, I finally managed it, but then I uninstalled it because I realized it was running very poorly. Thanks to ekaitz and ieure for their help. <randomguixuser>I have an old project in what i'm bouncing back. That is a rust project based on wasm-pack. Among other things I have a crate for which in old days I used `wasm-pack build` to building it. <randomguixuser>The thing is I don't understand how to install the `wasm32-unknown-unknown` cross-compiling target. Or in a broader way how to install an extra rust target for cross-compiling. <randomguixuser>On a regular unix-like OS, such as ubuntu or arch, you have `rustup` and just do `rustup target add ..` and that's it. <randomguixuser>But, on guix is different, rustup is not available and rust installation is manage by guix. <randomguixuser>Here I simply inherit the original rust package, pass it the pre-compiled tarball for the compilation target as input, unpack it, and place it where the documentation says. <ieure>randomguixuser, I don't have a great answer for you, but nonguix has some Rust WASM toolchain stuff for their Firefox package. I've attempted to rip it off a bit and contribute to Guix, but it's using some pretty old versions of stuff and I ran into issues when I updated it. <randomguixuser>ieure: Don't worry— that someone actually read all that stuff I threw up in the chat is a lot. I'm going to take a look at these tools in Noguix, but they seem to be tools for the WASI runtime environment; I'm not sure if I could use them. Anyway, if I manage to implement the build target for `wasm32`, I'll share it here. <randomguixuser>Actually, I'd also like to contribute a little in that direction, although I still need to get more comfortable with Guix <ieure>randomguixuser, They build both WASI and a Rust WASM toolchain. <ieure>I think you pretty much have to have a stdlib for a cross-compiler to be useful, no? <randomguixuser>@ieure Something like, I guess? I mean, as far as I understand, the binary that rustup installs when you add the build target is exactly that: the stdlib but compiled for the cross-target (if I understand correctly). The problem is that when you link it, the Rust compiler recognizes it as incompatible. <randomguixuser>The thing is, I need the `wasm32-unknown-unknown` build target, but in that Noguix package I see `wasm32-wasi` and a few others that look similar—I'm not really sure if they're the same thing. <ieure>randomguixuser, Yeah, okay. Fair enough. <randomguixuser>I'll keep looking for things, and if I make an interesting discovery I'll share it here.