| 18 Apr 2025 |
 SigmaSquadron | So, updated my nixpkgs to de164564c059d29e2d913f749e7c1beb5002f7a6, and I'm getting the same failures on messagelib and mimetreeparser. | 18:39:29 |
| SigmaSquadron | KPim6::Mbox is somehow missing | 18:40:24 |
| SigmaSquadron | Did anyone else manage to build those two packages? | 18:40:40 |
| SigmaSquadron | * | 18:40:55 |
 K900 ⚡️ | Yes | 18:54:30 |
| K900 ⚡️ | Can you nix-store --verify maybe | 18:54:35 |
| SigmaSquadron | Dang it, looks like there are some corrupted links. Good catch! | 19:10:25 |
 emily | 🤔 | 19:12:11 |
| emily | do you use auto-optimise-store? | 19:12:15 |
| SigmaSquadron | I do. I thought that was only broken on darwin? | 19:13:53 |
| SigmaSquadron | ah, the kmbox path was corrupt as well. | 19:14:19 |
| emily | it's very broken on Darwin, but it's theoretically UB on all platforms, so maybe you're the first? | 19:38:23 |
| emily | Lix fixed it though | 19:38:27 |
| SigmaSquadron | this system has a faulty CPU, and it crashes every couple of days or so. I'd say the random shutdowns are more likely to cause store corruption issues than Nix bugs. | 19:39:53 |
 mjm | why not both? | 20:05:13 |
| SigmaSquadron | ¯\(ツ)/¯ | 20:10:05 |
| 19 Apr 2025 |
 FliegendeWurst | auto-optimise-store has other serious issues. If you have your store on ext4 and get close to the directory size limit, builds randomly fail, unless you activate ext4's large_dir option. | 08:02:14 |
|  jopejoe1 changed their display name from jopejoe1 to jopejoe1 (4094@eh22). | 13:01:30 |
 Sandro 🐧 | In reply to @fliegendewurst:matrix.org
auto-optimise-store has other serious issues. If you have your store on ext4 and get close to the directory size limit, builds randomly fail, unless you activate ext4's large_dir option. Can't hear you from ZFS 😂 | 14:58:56 |
| Sandro 🐧 | But yeah, if you would redo the store, it would have extra directories with prefixes | 14:59:29 |
| 22 Apr 2025 |
|  Marmar changed their profile picture. | 05:36:15 |
| 23 Apr 2025 |
|  anji joined the room. | 16:14:05 |
| 24 Apr 2025 |
| SigmaSquadron | Should the KDE team be maintaining calligra, kup and wallpaper-engine-kde-plugin? I'm preparing the meta.maintainers = lib.teams.<team>.members -> meta.teams = [ lib.teams.<team> ] migration and switching that attribute in mkKdeDerivation caused the KDE team to start maintaining these three new packages.
I know Calligra is part of Gear, so it makes sense that the KDE team maintains it, but I'm not sure about kup.
| 03:19:15 |
| K900 ⚡️ | No, those probably need an explicit teams = [] then | 04:43:19 |
| SigmaSquadron | In reply to @k900:0upti.me
No, those probably need an explicit teams = [] then Since you're also a kernel maintainer, does that apply to the custom kernels (zen, lqx) as well? | 10:20:52 |
| K900 ⚡️ | Yes | 10:23:41 |
| K900 ⚡️ | Those are absolutely not in scope for people-that-actually-care-about-kernels-and-not-rice team | 10:23:52 |
 Grimmauld (any/all) | i found qtsvg is broken on cross, and seems that is known: https://github.com/NixOS/nixpkgs/pull/314724
The PR is there, but it was never merged and now has merge conflicts. How does one go about these things? Do i make a superseeding PR? | 18:44:45 |
| K900 ⚡️ | qt cross is completely fucked | 18:54:30 |
| K900 ⚡️ | I want to say don't even bother with qt5 it's not worth it | 18:54:49 |
