!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

204 Members
57 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
18 Apr 2025
@sigmasquadron:matrix.orgSigmaSquadronah, the kmbox path was corrupt as well.19:14:19
@emilazy:matrix.orgemilyit's very broken on Darwin, but it's theoretically UB on all platforms, so maybe you're the first?19:38:23
@emilazy:matrix.orgemilyLix fixed it though19:38:27
@sigmasquadron:matrix.orgSigmaSquadronthis 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:midna.devmjmwhy not both?20:05:13
@sigmasquadron:matrix.orgSigmaSquadron ¯\(ツ)20:10:05
19 Apr 2025
@fliegendewurst:matrix.orgFliegendeWurstauto-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:matrix.orgjopejoe1 (4094@39c3) changed their display name from jopejoe1 to jopejoe1 (4094@eh22).13:01:30
@sandro:supersandro.deSandro 🐧
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:supersandro.deSandro 🐧But yeah, if you would redo the store, it would have extra directories with prefixes14:59:29
22 Apr 2025
@marmar22:tchncs.deMarmar changed their profile picture.05:36:15
23 Apr 2025
@anjix:matrix.organji joined the room.16:14:05
24 Apr 2025
@sigmasquadron:matrix.orgSigmaSquadron

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:0upti.meK900 No, those probably need an explicit teams = [] then 04:43:19
@sigmasquadron:matrix.orgSigmaSquadron
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:0upti.meK900Yes10:23:41
@k900:0upti.meK900Those are absolutely not in scope for people-that-actually-care-about-kernels-and-not-rice team10:23:52
@grimmauld:grapevine.grimmauld.deGrimmauld (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:0upti.meK900qt cross is completely fucked18:54:30
@k900:0upti.meK900I want to say don't even bother with qt5 it's not worth it18:54:49
@k900:0upti.meK900qt6 should be doable but needs someone to put time into it18:54:59
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)problem is, this goes into fctix5 -> sdl3 -> literally everything19:04:19
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)* problem is, this goes into fctix5 -> sdl3 -> literally everything gui19:04:30
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)unless you want to give up on having cross gui, fixing that is mandatory i am afraid19:04:51
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)And, fwiw, with that patch i did get past the little Qt stuff on the way to sdl319:05:24

Show newer messages


Back to Room ListRoom Version: 9