IRC channel logs
2026-10-06.log
back to list of logs
<apteryx>hm, while attempting a deploy: "aborting reconfiguration because commit 9a7fb4173f9b503c4cafedaa0aa4bdd9d83fc5dc of channel 'guix' is not a descendant of 4341c003d7655ac02d72aea58cda706d87d0f965" <apteryx>there's no switch to tell it to force it; 4341c003d7655ac02d72aea58cda706d87d0f965 is not a known commit, not sure where it came from <apteryx>nevermind, my guix pull was ahead of my git checkout ^^' <switchy>we should go back to svn with linear change numbers! <jlicht>switchy: followed by a guix_updated_final_really_2 ;-) <civodul>apteryx: thanks for the taking care of the store database on berlin! <apteryx>civodul: I'm almost done, but not yet <apteryx>will restart myself when done ('herd restart guix-daemon') <apteryx>running 'guix gc --verify=contents', which takes a bit of time <apteryx>mumi is using 10.5g of rss; is it leaking too? <civodul>apteryx: --verify=contents takes ages; are you sure you want to do that? <civodul>it has to read every single file of every store item <civodul>and yes, mumi consistently takes lots of memory and CPU <apteryx>OK, I'll try with just `--verify'; and now I see the repair option; I wonder if this could have worked instead of my manual sqlite commands. <untrusem>I was trying to download the latest ci build iso but it failed <apteryx>civodul: I think we can simply wait until the promised date and then take it offline <apteryx>I forgot what the promised date was, I think 2 years from the move to codeberg, so probably another year or so now. <civodul>apteryx: i would keep it online (i regularly have to check old bugs when investigating new ones :-)), but in archived or semi-archived mode <civodul>that is, arranging so we don’t spend as many resources on it <civodul>moving it to a different host would already be a relief <efraim>apteryx: I've tried in the past with the repair option and it wasn't enough <look>hi guix, is it possible to use home-channels-service-type together with the new downloaded-channels? <civodul>look: hi! i would say that the two are unrelated, no? <civodul>or what use case did you have in mind? <Nessah>Hi there, Guix. Does anyone else have issues with font-google-noto 2026.09.01? Most of my fonts had disappeared after upgrading from 2026.01.01, so I had to hold back from upgrading it specifically. <Nessah>I manage my fonts in my user profile, thankfully. <lechner>Nessah: Did you regenerate your fontconfig cache? <Nessah>I assume guix would already do that, but I probably haven't <Nessah>cause usually when installing fonts, they get added automatically <lechner>Yes, Guix should but you can also do it manually. I think it's fontconfig -c. <Nessah>there isn't a command called fontconfig installed, part of any package? <Nessah>'guix shell fontconfig' doesn't appear to add anything <Nessah>riight. so the command was fc-cache -rv. all sorted , thanks <lechner>Nessah: You found the correct command and your fonts are working? <Nessah>Only thing is, my Konsole font looked weird and I had to manually tweak it, but everything's fine now. <Nessah>Noto Sans Mono Light used to be the default. <HannahUwU>I'm having some problems: Are there substitutes for the rust-team channel? If so, where are they? <PotentialUser-20>hi all. i think i may have created a problem. while clearing away some space in my user's home folder, i deleted some legacy backups. now im noticing that on every boot, the user's home is missing symlinks. its as if i never `guix home reconfigured` at all. can i fix this by rolling back my users home only? <reyman>if someone of the team rust could help me on this, after that i could push it to codeberg <avalenn>PotentialUser-20: you just have to execute guix home reconfigure by the user <PotentialUser-20>avalenn yes, ive been doing that but everytime i reboot. would rolling back help at all? <PotentialUser-20>avalenn as in, rebooting Guix SD entirely. sorry, should have mentioned this that this is a guix system first. but it is a lot of symlinks, specifically in the user's home. <avalenn>strange, I don't see what could delete them <nocrosoft>Hi all, I'm trying to define my own fork of the helix editor in my home config. It's a rust project, and the fork has dependencies not defined in guix itself, so building fails. I generated the dependency definitions using the crate importer but I don't know what to do at this point. The lookup-cargo-inputs is a global I think? I don't know if/how <gkoebel-ext>congrats to whomever manages the guix CI stuff for staying up while most of the org is down <HannahUwU>Uh, is that why guix wants to compile everything itself <csantosb>This, and the delay to make substitutes available <HannahUwU>csantosb everything is down right now, aws has an outage, too <csantosb>Ah, I discover this right now. What a fragile world we're building. <HannahUwU>I don't know if my substitutes are working anyone willing to help me? <untrusem>this should list if you are using substitutes or not <Hannah_>tusharhero-xmpp: Nya (my browser just crashed) <Hannah_>untrusem: Yeah, I wanna know if I did everyhing right in my config. <HannahUwU>Because uhh, I am using the guix channel twice so I can have rust-team and the normal one <HannahUwU>untrusem yeah, I haven't been able to get it to work. <HannahUwU>When I reconfigure, it wants to build a ton of packages at once <nikolar>is there a particular reason why clangd isn't shipped as a standalone package rather than a part of clang <HannahUwU>untrusem i think you don't have to specify it in the cfg <untrusem>but its better to have everything define <yelninei>HannahUwU: dont combine different branches from the same channel. This does not work. If you are using a nondefault branch for the guix channel expect things to be unstable <HannahUwU>yelninei how should I get an up-to-date version of rust then? <gkoebel-ext>some days ago someone suggested I use `guix shell --container --emulate-fhs` to be able to install rustup and use rust <yelninei>you are not only getting an "up-to-date version of rust". You are getting the entire distro compiled against the rust from the other branch <yelninei>with all the rebuilds and breakages thant come with that. Thats why it is on another branch. <untrusem>I remember telling you about inferiors and other other thing <yelninei>if you just need a newer version of rust there are multiple ways and depends on what you need it for <HannahUwU>yelninei development and trying out projects from friends. <gkoebel-ext>yelninei: iirc the packaged rust in GUIX lacks IF LET so modern stuff won't compile (i.e. Halloy won't compile on GUIX's rust <gkoebel-ext>My end goal with GUIX is to get as close to "throw laptop into lake, recover on new machine" as possible. One area I'm interested for input on is dynamic discovery and generation of partition layout. i.e. if I know the partition map I want how much of a leap is it to have some bootstrapping install process discover the UIDs for the drives in my new system and go from there? I'm thinking something like 1. find devices 2. map devices to generic. <yelninei>what a nice stable language where a compiler version from the beginning of the year is already out of date ... <HannahUwU>untrusem the rust version in the main guix repo is 1.93.0 afaik <HannahUwU>yelninei have you heard of new features in languages? <gkoebel-ext>HannahUwU: you can do it in a container for the time being `guix shell --container --emulate-fhs` will give you a rustup compatible env to install into. I've not tested further than that. <untrusem>inferior, time-machine and copying to local channel and calling from that will work <untrusem>ACTION is somewhat of a rust packager in guix <Rutherther>HannahUwU: yeah sure I have a solution. Create a fork of the original project to make new features and let the old project die out <yelninei>HannahUwU: sure but projects breaking compatibility with older versions by depending on new features the second it becomes available is not how you build stable software <HannahUwU>yelninei i'm actually not that big of a rust fan. Mainly because they are ai sponsored, use ai for code and code reviews. <gkoebel-ext>yelninei: that's not really what they did. It was experimental in 1.93 so you could only use it on the unstable compiler. <untrusem>HannahUwU: ^ which solution will you prefer? <yelninei>there is rust 1.95 in guix but it not the default and hidden from the ui if that would work for you <untrusem>if that would work that we could just call it via "-e" <lechner>Hi, is anyone using a kernel with CONFIG_RUST enabled? <HannahUwU>untrusem uhm, the package came without cargo <HannahUwU>installing cargo fails because libgit2 fails <gkoebel-ext>side note on this, how do you pass the systems CA cert store to a container? <untrusem> -e '`(,(@ (gnu packages rust) rust-1.95) "cargo")' <untrusem>btw are you trying to build the package manually or making a package defination for guix, cause I don't former will yield the results you desire <HannahUwU>untrusem trying to build manually, it did work before with a project that doesn't use if let. <gkoebel-ext>is there a general way to figure out what package a command came from? on a debian system I'd use dpkg <gkoebel-ext>rustup would benefit from dependency checks in its installer <lechner>I used to publish a database to lookup files, but it didn't catch on <yelninei>Rutherther: just look at how some other projects discuss the up and downsides of updating the minimal required version of a dependency. It is not my project and people can do what they want with theirs but if one wants other people to be able to build (the latest version of) it then compatibility is something to consider <lechner>Isn't that a constant point of tension? There is no solution. <yelninei>lechner: Sure. And there may be good reason to break compatibility with older compilers but just a new syntax would not enough for me. New syntax is also tricky because the fallback would be just to not use it (yet). <untrusem>>I used to publish a database to lookup files, but it didn't catch on <untrusem>lechner: you mean the sqlite database of guixu <r13n>gkoebel-ext : Are you talking about autodiscovering UID of the drives to use in the init config? <r13n>*drives on the new device/laptop <gkoebel-ext>with the goal being of getting as close to the point of just plobbing the config file into a guix installer and having it figure everything out to replicate the system thats at the bottom of Loch Ness <lechner>untrusem / No, I used to publish a website that collected store paths from automatic submissions and made them searchable over the web. <untrusem>lechner: ohh is the source available somewhere? <r13n>gkoebel-ext : That'll be a interesting project. <r13n>Although, I prefer the installer to change the UUIDs to the ones mentioned in the config.scm . <r13n>That's be a true declarative deployment <r13n>Also, it'll be less complex to format the drive and apply schematics (partition, volume, uuid, file system, etc) as declared in config. <r13n>Or, change UUID without altering anything else. (we can do via `vgchange` command) <lechner>untrusem / It was four years ago. I'll get a hold of you when I find it. <Deltafire>feels like it should be on ipfs or something