Skip to content

[Backport release-25.05] teleport_17: 17.5.3 -> 17.5.4; teleport_16: 16.5.11 -> 16.5.13#423289

Merged
wolfgangwalther merged 2 commits intorelease-25.05from
backport-422238-to-release-25.05
Jul 15, 2025
Merged

[Backport release-25.05] teleport_17: 17.5.3 -> 17.5.4; teleport_16: 16.5.11 -> 16.5.13#423289
wolfgangwalther merged 2 commits intorelease-25.05from
backport-422238-to-release-25.05

Conversation

@nixpkgs-ci
Copy link
Copy Markdown
Contributor

@nixpkgs-ci nixpkgs-ci Bot commented Jul 7, 2025

Bot-based backport to release-25.05, triggered by a label in #422238.

  • Before merging, ensure that this backport is acceptable for the release.
    • Even as a non-committer, if you find that it is not acceptable, leave a comment.

@nixpkgs-ci nixpkgs-ci Bot added the 1.severity: security Issues which raise a security issue, or PRs that fix one label Jul 7, 2025
@nixpkgs-ci nixpkgs-ci Bot added 4.workflow: backport This targets a stable branch 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. labels Jul 7, 2025
@JuliusFreudenberger
Copy link
Copy Markdown
Contributor

nixpkgs-review result

Generated using nixpkgs-review-gha

Command: nixpkgs-review pr 423289

Logs: https://github.com/JuliusFreudenberger/nixpkgs-review-gha/actions/runs/16126229708


x86_64-linux

✅ 4 packages built:
  • teleport (teleport_17)
  • teleport.client (teleport_17.client)
  • teleport_16
  • teleport_16.client

aarch64-linux

✅ 4 packages built:
  • teleport (teleport_17)
  • teleport.client (teleport_17.client)
  • teleport_16
  • teleport_16.client

x86_64-darwin (sandbox = true)

❌ 2 packages failed to build:
  • teleport_16
  • teleport_16.client
✅ 2 packages built:
  • teleport (teleport_17)
  • teleport.client (teleport_17.client)

aarch64-darwin (sandbox = true)

❌ 2 packages failed to build:
  • teleport_16
  • teleport_16.client
✅ 2 packages built:
  • teleport (teleport_17)
  • teleport.client (teleport_17.client)

version = "16.5.13";
hash = "sha256-X9Ujgvp+2dFCoku0tjGW4W05X8QrnExFE+H1kMhf91A=";
vendorHash = "sha256-0+7xbIONnZs7dPpfpHPmep+k4XxQE8TS/eKz4F5a3V0=";
pnpmHash = "sha256-waBzmNs20wbuoBDObVFnJjEYs3NJ/bzQksVz7ltMD7M=";
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
pnpmHash = "sha256-waBzmNs20wbuoBDObVFnJjEYs3NJ/bzQksVz7ltMD7M=";
pnpmHash = "sha256-IISTLreZSBrF1VDmXSDK6EFpn0o9sOxQDgDmwFNocRA=";

(per https://github.com/JuliusFreudenberger/nixpkgs-review-gha/actions/runs/16126229708/job/45503671368#step:6:1871)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Was gone without laptop, so didn't have the capabilities to check.

But: Why?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@techknowlogick, you own a aarch64-darwin machine. Could you please double-check?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest, this is similar to #407982 (comment) (and following links).
So a review on real hardware (not GHA runner) is really appreciated.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See my nixpkgs-review run. Does that mean pnpm.fetchDeps is not reproducible?

Copy link
Copy Markdown
Contributor

@wolfgangwalther wolfgangwalther Jul 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ping @gepird and @Scrumplex who fixed some pnpm.fetchDeps reproducibility issue earlier this year.

Edit: Ah, found #422975 now, which could hopefully fix it?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#422975 fixes the permission mismatch when using pnpm.fetchDeps on different environments. If this is the cause, you'll be able to fix it by opting into a newer version:

# file: pkgs/by-name/te/teleport/package.nix
    pnpmDeps = pnpm_10.fetchDeps {
      inherit src pname version;
      hash = pnpmHash;
      fetcherVersion = 2;
    };

I'm getting the sha256-waBzmNs20wbuoBDObVFnJjEYs3NJ/bzQksVz7ltMD7M= hash, it would be helpful if you could share your pnpm deps with the sha256-IISTLreZSBrF1VDmXSDK6EFpn0o9sOxQDgDmwFNocRA= hash :)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems the only time the other hash appeared is in the GHA run in #423289 (comment) - so I think nobody has access to the actual result with the other hash.

Although I wonder whether the fact that this seems to be the only case where the sandbox was fully enabled (sandbox = true) plays a role? I assume all other tests were with a relaxed sandbox.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible for either of you to run it with fully enabled sandbox? I sadly don't have access to a Mac, so I cannot help here.

@wolfgangwalther
Copy link
Copy Markdown
Contributor

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 423289
Commit: cfe8744d79862cf40b77ca315bee2644f61a834a


x86_64-linux

✅ 4 packages built:
  • teleport (teleport_17)
  • teleport.client (teleport_17.client)
  • teleport_16
  • teleport_16.client

aarch64-linux

✅ 4 packages built:
  • teleport (teleport_17)
  • teleport.client (teleport_17.client)
  • teleport_16
  • teleport_16.client

x86_64-darwin

✅ 4 packages built:
  • teleport (teleport_17)
  • teleport.client (teleport_17.client)
  • teleport_16
  • teleport_16.client

aarch64-darwin

✅ 4 packages built:
  • teleport (teleport_17)
  • teleport.client (teleport_17.client)
  • teleport_16
  • teleport_16.client

@techknowlogick
Copy link
Copy Markdown
Member

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 423289


aarch64-darwin

✅ 4 packages built:
  • teleport (teleport_17)
  • teleport.client (teleport_17.client)
  • teleport_16
  • teleport_16.client

@nixpkgs-ci nixpkgs-ci Bot added 12.approvals: 1 This PR was reviewed and approved by one person. 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in any of the changed packages. labels Jul 9, 2025
@wolfgangwalther
Copy link
Copy Markdown
Contributor

Since there is no reason to assume that this hash is consistent on the release branch right now and the inconsistencies only introduced here, I think we should merge this with the current hash. That's no worse than what we already have, I think.

The "other" hash was only observed in a GHA run, so far. Everybody else had the hash that is currently in the code. Once this hits hydra (and assuming that hydra will be able to build it), this hash will then substitute the same FOD for everyone.

Thus, we should not block this PR on the instability of the fetcher. Any objection to merging, anyone?

Copy link
Copy Markdown
Contributor

@JuliusFreudenberger JuliusFreudenberger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's do the merge.

@nixpkgs-ci nixpkgs-ci Bot added 12.approvals: 2 This PR was reviewed and approved by two persons. and removed 12.approvals: 1 This PR was reviewed and approved by one person. labels Jul 15, 2025
@wolfgangwalther wolfgangwalther dismissed mdaniels5757’s stale review July 15, 2025 19:44

needs to be solved elsewhere

@wolfgangwalther wolfgangwalther merged commit 2ef493b into release-25.05 Jul 15, 2025
33 of 34 checks passed
@wolfgangwalther wolfgangwalther deleted the backport-422238-to-release-25.05 branch July 15, 2025 19:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1.severity: security Issues which raise a security issue, or PRs that fix one 4.workflow: backport This targets a stable branch 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 12.approvals: 2 This PR was reviewed and approved by two persons. 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in any of the changed packages.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants