Skip to content

Conversation

@nixpkgs-ci
Copy link
Contributor

@nixpkgs-ci nixpkgs-ci bot commented Jul 31, 2025

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

  • 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.

Essentially reverts ebbcb00 since
6814b2f fixes it.

(cherry picked from commit 9093a19)
@D3vil0p3r
Copy link
Member

D3vil0p3r commented Jul 31, 2025

Is it possible to backport the current rustc version (1.88) to 25.05? I think it is needed to create different backport requests since the current one involve only one nix file.

@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux. 6.topic: rust General-purpose programming language emphasizing performance, type safety, and concurrency. 4.workflow: backport This targets a stable branch labels Jul 31, 2025
@alyssais
Copy link
Member

#407444 (comment)

@alyssais
Copy link
Member

Closing this as we learned that rustc was in fact still broken for LLVM stdenv.

@alyssais alyssais closed this Jul 31, 2025
@alyssais alyssais deleted the backport-429009-to-release-25.05 branch July 31, 2025 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4.workflow: backport This targets a stable branch 6.topic: rust General-purpose programming language emphasizing performance, type safety, and concurrency. 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants