| 1 Jun 2026 |
 éclaire | deleted the nix store volume and then i have to reinstall. which is annoying since it basically forces redownloading everything | 21:32:20 |
| éclaire | * | 21:33:06 |
| éclaire | * deleted the nix store volume, ran the security delede-generic-password command, and then i have to reinstall. which is annoying since it basically forces redownloading everything | 21:35:15 |
| éclaire | * deleted the nix store volume, ran the security delete-generic-password command, and then i have to reinstall. which is annoying since it basically forces redownloading everything | 21:35:22 |
|  Asterto joined the room. | 22:10:53 |
 zoë (@blokyk) | firefox simply displays "Cannot complete request," and using curl only returns Suspected harmful pattern; if legitimate, contact AFNix infrastructure team. | 22:35:34 |
| zoë (@blokyk) | * firefox simply displays "Cannot complete request," and using curl only returns Suspected harmful pattern; if legitimate, contact AFNix infrastructure team.
(tested with this url)
| 22:37:25 |
| 2 Jun 2026 |
|  kiffeuse4life67 changed their display name from missbehaves to kiffeuse4life67. | 07:45:25 |
 raitobezarius | OK, I know what is the fix | 07:47:40 |
 Sofie 🏳️⚧️🐾 (she/her) | I want to make my nixos infrastructure more stable Is there a way to handle key deployment, encryption of secrets and disk encryption in an centrally managed way? For example, how are servers deployed in a data center? | 08:10:14 |
 K900 | PXE, usually | 08:10:58 |
| K900 | As in, everything netbooted as much as possible | 08:11:06 |
| K900 | And secrets stored in something like Vault | 08:11:24 |
| K900 | Also #offtopic | 08:11:31 |
| Sofie 🏳️⚧️🐾 (she/her) | In reply to @k900:0upti.me
Also #offtopic oh, yeah | 08:12:03 |
|  Bart joined the room. | 09:42:56 |
 truh | Is there some known problem that would lead to lix failing to acquiring inputs when the flake is not in the root folder of the git repo? | 14:59:20 |
| raitobezarius | If it was present since 2.18, it's likely yeah | 15:00:01 |
| truh | I switched from https://git.lix.systems/lix-project/nixos-module/archive/2.93.3-2.tar.gz to pkgs.lixPackageSets.stable.lix; (2.94.2) today | 15:01:53 |
| raitobezarius | So this is something new? | 15:08:53 |
 just1602 | Is there known bugs that prevent stable to be the latest 2.95, especially since the 26.05 upgrade? | 15:10:50 |
| truh | yeah, but it seems to be working with nix run 'https://git.lix.systems/lix-project/lix/archive/2.95.3.tar.gz' -- flake update again. I still get some warnings warning: could not update mtime for file '': No such file or directory which may be related. | 15:11:00 |
| raitobezarius | That's really surprising, is the Flakes repo public? | 15:29:57 |
| raitobezarius | I'm not aware of any | 15:30:02 |
| raitobezarius | But now that 26.05 is released, we cannot really upgrade the stable pointer | 15:30:11 |
| raitobezarius | IIRC, this was on purpose because we only bump one version at a time | 15:30:28 |
| raitobezarius | So 2.94 is stable for the lifetime of 26.05 and 2.95 is latest | 15:30:37 |
| raitobezarius | Then 26.11 will have 2.95 as stable, etc. | 15:30:46 |
| truh | No unfortunatly it's private. There is also other weird stuff in some of the flake inputs like submodules in submodules and git-lfs which might be a contributing factor. I've tested all the 2.94.x releases and they all fail, 2.95 works. Checking 2.93 right now. | 15:35:38 |
| raitobezarius | If I have a public reproducer, I can dig into it | 15:35:49 |
