!UNVBThoJtlIiVwiDjU:nixos.org

Staging

316 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.05 | Review Reports: https://malob.github.io/nix-review-tools-reports/107 Servers

Load older messages


SenderMessageTime
18 Dec 2025
@adam:robins.wtf@adam:robins.wtf left the room.12:29:30
@k900:0upti.meK900 OK reverted xsimd, can anyone else check if thrift builds for them on aa64? 16:03:30
@k900:0upti.meK900It locks up in some test for me16:03:41
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/46913023:13:47
@hexa:lossy.networkhexaA bit sad that we missed the c-ares security update23:14:26
19 Dec 2025
@ghpzin:envs.netghpzin Anyone looked at kdePackages.libkleo ?
https://hydra.nixos.org/build/316811546
(pulled with plasma6 module by default from kde-pim)
Adding gpgme,gpgmepp,libgpg-error to extraPropagatedBuildInputs makes it (and next things) build, but does not feel right.
I assume at least qgpgme should work instead of gpgme
09:25:18
@k900:0upti.meK900This is new and weird09:26:36
@k900:0upti.meK900Why did this work before09:26:39
@k900:0upti.meK900Did we touch gpgme this cycle?09:26:45
@ghpzin:envs.netghpzinYes, updated to 2.0: https://github.com/NixOS/nixpkgs/pull/45189809:27:05
@ghpzin:envs.netghpzin Yes, updated 1.24.3 -> 2.0.1:
https://github.com/NixOS/nixpkgs/pull/451898
09:27:26
@ghpzin:envs.netghpzin Yes, updated gpgme: 1.24.3 -> 2.0.1:
https://github.com/NixOS/nixpkgs/pull/451898
09:27:45
@ghpzin:envs.netghpzin Yes, updated gpgme: 1.24.3 -> 2.0.1:
https://github.com/NixOS/nixpkgs/pull/451898
Actually that PR changed qgpgme too.
09:30:48
@k900:0upti.meK900It should pull qgpgme via autodeps09:35:45
@ghpzin:envs.netghpzin You mean the other way around qgpgme should pull gpgme and other things ?
Or that qgpgme should be in one of the generated kde files ?
11:05:32
@ghpzin:envs.netghpzin You mean the other way around qgpgme should pull gpgme and other things ?
Or that qgpgme should be in one of the generated kde files ?
Seems like before that PR they were all in one package (qgpgme,gpgme,gpgmepp), so it was not a problem.
11:09:19
@k900:0upti.meK900No, I mean libkleo should pull qgpgme via generated autodeps I think12:08:44
@k900:0upti.meK900 But maybe I'm wrong 12:08:48
@ghpzin:envs.netghpzin Another weird thing is, libkleo is not the only thing that has qgpgme in dependencies.
But all other things seem to build fine, so are they not using it or just find gpgme in some other way.
12:12:34
@ghpzin:envs.netghpzin Another weird thing is, libkleo is not the only thing that has qgpgme in dependencies.
But all other things seem to build fine (at least ones that are not blocked on other deps broken on staging-next), so are they not using it or just find gpgme in some other way.
12:14:04
@ghpzin:envs.netghpzin Another weird thing is, libkleo is not the only thing that has qgpgme in dependencies.
But all other things seem to build fine (at least ones that are not blocked on other deps broken on staging-next).
So are they not using it or just find gpgme in some other way.
12:14:18
@k900:0upti.meK900 I think the gpgme setup is pretty cursed 12:19:51
@k900:0upti.meK900Anyway feel free to leave it alone and I'll take a look when I'm less migraine13:31:44
@ghpzin:envs.netghpzin Thank you.
If nothing else works as mentioned adding gpgme gpgmepp libgpg-error into extraPropagatedBuildInputs seems to at least build libkleo and all other things depending on it.
13:34:14
@k900:0upti.meK900I don't know why it wants all three13:34:59
@k900:0upti.meK900Maybe gpgme needs to propagate the other two?13:35:06
@ghpzin:envs.netghpzin As I understand all these things (including qgpgme) except for libgpg-error were one and the same before that update PR.
So there was never a question of propagating, it was just a bundle with all cmake .pc files and everything together.
13:37:06
@ghpzin:envs.netghpzin As I understand all these things (including qgpgme) except for libgpg-error were one and the same before that update PR.
So there was never a question of propagating, it was just a bundle with all cmake, .pc files and everything together.
Not sure how person doing that PR decided on how split should work.
13:37:44
@k900:0upti.meK900 @dotlambda thoughts? 13:38:19
@ghpzin:envs.netghpzin As I understand all these things (including qgpgme that added qt things on top) except for libgpg-error were one and the same before that update PR.
So there was never a question of propagating, it was just a bundle with all cmake, .pc files and everything together.
Not sure how person doing that PR decided on how split should work.
14:02:46

Show newer messages


Back to Room ListRoom Version: 6