!UNVBThoJtlIiVwiDjU:nixos.org

Staging

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

Load older messages


SenderMessageTime
16 Jun 2026
@tfc:matrix.orgtfcit would be a bit of a shame if we couldn't have that because CI (re)builds them unnecessarily11:40:53
@leona:leona.isleona* is it important that it gets built by hydra? I mean we can still provide it in Nixpkgs11:40:55
@tfc:matrix.orgtfcnot important that hydra builds it11:40:59
@leona:leona.isleonathat's my suggestion for that https://github.com/NixOS/nixpkgs/pull/53239618:16:35
@leona:leona.isleonaeven makes GHA eval ~1.89% faster ^^18:17:15
18 Jun 2026
@r-burns:matrix.orgr-burnspython3.pkgs.fakeredis fails some tests on staging-next-26.05, bumping to latest seems to fix it. Bump doesn't seem to cause breakage on master so potentially could merge to master -> backport 26.05 -> merge into staging-next-26.05 if that seems cleaner than a cherry-pick.00:40:45
@hexa:lossy.networkhexa master -> release-26.05 sounds fine to me 00:42:19
@hexa:lossy.networkhexaprobably another fallout from the valkey 9.1 update that surely had no breaking changes00:42:57
@hexa:lossy.networkhexaRedacted or Malformed Event00:43:05
@r-burns:matrix.orgr-burnsRebuild count might be bordering a staging target though, I'm seeing 501 although they are mostly small python packages00:52:51
@r-burns:matrix.orgr-burnshttps://github.com/NixOS/nixpkgs/pull/53283600:56:27
@hexa:lossy.networkhexathat could be as low as 10100:56:45
@hexa:lossy.networkhexa49200:57:06
@hexa:lossy.networkhexa😉00:57:09
@r-burns:matrix.orgr-burnsI did a local nixpkgs-review rev HEAD that reported 50100:57:14
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/actions/runs/2772939480300:57:26
@debtquity:matrix.orgdebtquityhmm?01:06:39
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/528906#issuecomment-470786351401:07:13
@debtquity:matrix.orgdebtquityso if i update valkey, i need to individually update all of these small python libs too?01:07:19
@hexa:lossy.networkhexayou need to test them01:07:26
@hexa:lossy.networkhexaat least some of them01:07:43
@hexa:lossy.networkhexathe ones that are prone to breaking01:07:48
@hexa:lossy.networkhexalike python3.pkgs.valkey01:07:51
@hexa:lossy.networkhexa you can collect them into passthru.tests 01:08:17
@hexa:lossy.networkhexaand the build valkey.tests01:08:22
@hexa:lossy.networkhexaRedacted or Malformed Event01:08:30
@debtquity:matrix.orgdebtquity

will just invoking the problematic downstream packages work?

https://github.com/NixOS/nixpkgs/blob/d1a55f0c7b921d541c6142994c96fbd7f1fa562e/pkgs/by-name/va/valkey/package.nix#L110-L113

  passthru = {
    tests = {
      redis = nixosTests.redis;
      python3-valkey = callPackage python3.pkgs.valkey;
    };
    serverBin = "valkey-server";
  };

???

01:26:27
@debtquity:matrix.orgdebtquitysurprised there's not much there at the moment, guess the previous maintainers had it in their head?01:28:00
@r-burns:matrix.orgr-burnstried a nixpkgs-review and it OOMed after about 125 builds, but didn't see any failures other than the preexisting python3.pkgs.jupytext from that sample. Will try again later01:34:42
@flashonfire:lithium.ovhguillaumeI can try a local nixpkgs review if it's needed06:56:31

Show newer messages


Back to Room ListRoom Version: 6