!UNVBThoJtlIiVwiDjU:nixos.org

Staging

309 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/106 Servers

Load older messages


SenderMessageTime
20 Oct 2025
@vcunat:matrix.orgvcunatooh, it fails also on x86_64-linux08:57:35
@vcunat:matrix.orgvcunat I just confused opensshTest with nixosTests.openssh 😕 08:57:50
@k900:0upti.meK900Are those not the same thing08:58:40
@k900:0upti.meK900Oh it's openssh's own tests08:59:13
@vcunat:matrix.orgvcunatThe failure got triggered just by openssh update. Well, details on that issue.09:45:14
@vcunat:matrix.orgvcunatBTW, I generally wonder why maintainers relevant to a PR/package so often don't finish their backports and just leave the backport PR hanging indefinitely.11:53:28
@elvishjerricco:matrix.orgElvishJerriccoheh, this is kinda funky. I based my 258.1 branch on my staging-next fix yesterday since it reverts the commit. Now that that commit has gone staging-next -> staging, github still shows it as one of the commits for the 258.1 branch in the PR. Weird.12:10:30
@elvishjerricco:matrix.orgElvishJerriccoah, just pushing an update to the commit timestamps of the two new commits fixed that12:14:09
@vcunat:matrix.orgvcunatYes, you need to force-push via git or rebase in the UI or something to make it refresh the commit list.12:15:46
@eveeifyeve:matrix.orgeveeifyeve joined the room.12:41:30
@eveeifyeve:matrix.orgeveeifyevedoes anyone know when the next merge of staging to staging next is?12:42:00
@vcunat:matrix.orgvcunatI don't think so 😅12:44:09
@vcunat:matrix.orgvcunatWhy are you interested in that?12:44:25
@vcunat:matrix.orgvcunat(maybe we can answer that)12:44:33
@eveeifyeve:matrix.orgeveeifyeveI am trying to track when https://github.com/NixOS/nixpkgs/pull/453489 gets built by hydra.12:44:34
@dramforever:matrix.orgdramforeverwhen we're done merging this staging-next to master12:44:55
@vcunat:matrix.orgvcunat Well... there's also staging-next-25.05 possible. 12:45:12
@vcunat:matrix.orgvcunat I mean, we will have to do it at some point at least once. 12:45:23
@vcunat:matrix.orgvcunatAnd I don't think there will every be a "perfect moment".12:46:23
@vcunat:matrix.orgvcunat* And I don't think there will ever be a "perfect moment".12:46:27
@vcunat:matrix.orgvcunat(I'm even tempted to start it today.)12:46:49
@eveeifyeve:matrix.orgeveeifyeve

Well I was trying to build staging deps in a devshell and found this to be an issue with libedit:

error: builder for '/nix/store/hp66qyxi3s4y682xxhphz81hjmc0nm38-libedit-20251016-3.1.tar.gz.drv' failed with exit code 1;
       last 12 log lines:
       >
       > trying https://thrysoee.dk/editline/libedit-20251016-3.1.tar.gz
       >   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
       >                                  Dload  Upload   Total   Spent    Left  Speed
       >   0     0    0     0    0     0      0      0 --:--:--  0:00:03 --:--:--     0curl: (6) Could not resolve host: thrysoee.dk
       > Warning: Problem : timeout. Will retry in 1 second. 3 retries left.
       > curl: (6) Could not resolve host: thrysoee.dk
       > Warning: Problem : timeout. Will retry in 1 second. 2 retries left.
       > curl: (6) Could not resolve host: thrysoee.dk
       > Warning: Problem : timeout. Will retry in 1 second. 1 retry left.
       > curl: (6) Could not resolve host: thrysoee.dk
       > error: cannot download libedit-20251016-3.1.tar.gz from any mirror
       For full logs, run:
         nix log /nix/store/hp66qyxi3s4y682xxhphz81hjmc0nm38-libedit-20251016-3.1.tar.gz.drv
12:47:19
@vcunat:matrix.orgvcunatI don't have that issue.12:48:23
@vcunat:matrix.orgvcunat(I mean, resolving the name is a pretty easy step not really related to staging* cycles.)12:48:39
@eveeifyeve:matrix.orgeveeifyeve

Let me provide the devshell so I can see if you can reproduce it.

{
  description = "Super simple starting point for Polar development flake";

  inputs = {
    nixpkgs.url = "github:nixos/nixpkgs/staging"; # Change to staging,  TODO: https://nixpk.gs/pr-tracker.html?pr=453690
    flake-parts.url = "github:hercules-ci/flake-parts";
    systems.url = "github:nix-systems/default";
  };

  outputs =
    inputs:
    inputs.flake-parts.lib.mkFlake { inherit inputs; } {
      systems = import inputs.systems;
      perSystem =
        {
          pkgs,
          system,
          ...
        }:
        {
          _module.args.pkgs = import inputs.nixpkgs {
            inherit system;
            config = {
              allowUnfree = true;
            };
          };

          devShells.default = pkgs.mkShell {
            nativeBuildInputs = with pkgs; [
              nodejs_22
              pnpm

              (python3.withPackages (p: [
                p.psycopg2-binary
                p.psycopg2
              ]))
              uv

              stripe-cli
              ngrok
            ];
          };
        };
    };
}
12:49:08
@dramforever:matrix.orgdramforeveryeah running on staging is usually a bad idea12:49:23
@dramforever:matrix.orgdramforeverunless you feel like building all of those stuff12:49:34
@eveeifyeve:matrix.orgeveeifyeveFor now I am doing this as I need it as a dependency for working on polar.sh.12:50:00
@vcunat:matrix.orgvcunatUsually you can just pick your relevant changes atop some point that does have binaries. (master, staging-next, depending on situation)12:50:28
21 Oct 2025
@fabianhjr:matrix.orgFabián Herediaimage.png
Download image.png
05:49:32

Show newer messages


Back to Room ListRoom Version: 6