| 27 Jun 2025 |
 Christian Theune | at some point i need to find a kernel developer, get him a beer and figure out why folios seem to be something that keeps popping up in bugs ... | 10:09:06 |
 raitobezarius | folios is one of the most complicated technical debt payment ongoing in the kernel | 10:10:58 |
| raitobezarius | so it's very normal that they're exploding in many ways given the lack of fstests that can simulate realistic workloads and the classical CI discussion when it comes to the kernel | 10:12:07 |
 emily | learning that Linux filesystems don't get deeply rigorous automated testing for every release is like nerd Santa | 10:13:19 |
 uep | I mean, quite honestly, that's one of any number of reasons to use zfs | 10:16:51 |
| uep | With all the obvious irony that carries | 10:17:20 |
| raitobezarius | (plot twist: ZFS don't get deeply rigorous automated testing for every release neither :P — though they have a generous manual test suite — ZTS — which is run on every staging release manually by ZFS leadership) | 10:18:10 |
| raitobezarius | as always, I recommend: https://lwn.net/Articles/1015320/ to learn more about folios (a lot of good backlinks) | 10:19:18 |
| uep | I know, zfs releases rather than every kernel. That's part of the irony | 10:20:35 |
| raitobezarius | Speaking of the wolf, David answered | 10:26:48 |
| raitobezarius | with "How do I use Nix on Fedora?" | 10:26:52 |
| emily | the two words every Fedora user loves to hear: "disable SELinux" | 10:28:13 |
 raboof | we'd like to have a simple static website for the NixNL community/meetup. could we serve that under i.e. nl.nixos.org or would it be better to put it somewhere else? having it on 'shared' infrastructure seems nice, so that it can be transferred when the current people go MIA (like happened with https://www.meetup.com/Amsterdam-Nix-Meetup/...) | 13:46:30 |
| 28 Jun 2025 |
 sterni | Another weird one: https://hydra.nixos.org/build/301060494/nixlog/1, remove-references-to is added to nativeBuildInputs unconditionally in haskellPackages. Can't reproduce this failure. | 09:57:34 |
| 30 Jun 2025 |
|  sinan changed their profile picture. | 02:11:25 |
|  atagen joined the room. | 03:05:47 |
| raitobezarius | hexa (signing key rotation when) could I bother you with a bump to the front with NixOS 25.05 for the new Lix bumps? | 12:25:16 |
 hexa (signing key rotation when) | smol? | 12:25:57 |
| raitobezarius | ye | 12:26:06 |
| hexa (signing key rotation when) | bumped | 12:26:44 |
| raitobezarius | <3 | 12:26:48 |
|  Roman Nefedov joined the room. | 20:18:38 |
| 1 Jul 2025 |
|  djacu joined the room. | 03:26:53 |
| djacu | Hey Infra Team
In case you haven't seen the recent post on discourse, the Marketing Team is preparing this year's community survey. I am reaching out to teams to see if there are any questions they would like to add to the survey to better serve the work you all do. More details in the post linked below.
https://discourse.nixos.org/t/community-feedback-requested-2025-nix-community-survey-planning/66155 | 03:27:21 |
 Jonas Chevalier | One question, but that's more of a personal one; would people be interested in being able to track their personal usage of the cache? We could introduce an optional API key system that would enable that type of accounting. | 08:44:10 |
| emily | to enable better analytics for decisionmaking or for consuming by yourself? | 09:06:42 |
| emily | for the former, I think there'd be more uptake if effort was put into doing it in a privacy-preserving way like the work done by Go and Divvi Up | 09:06:50 |
| emily | (actually, this might make no sense, since the cache already sees every request and who is making it, and totally-anonymized stats are already published) | 09:35:48 |
| emily | (but I can imagine cases where you might want to combine stats about requester with stats about requests. but privacy-preserving analytics ingestion stuff is probably not relevant here given the architecture of the cache. publication is another matter) | 09:36:22 |
 Emma [it/its] | wouldnt it make more sense to do this on the client side? | 09:36:33 |
