[25.11] cosmic-greeter: apply upstream patch for security hardening#505350
Conversation
(cherry picked from commit 64db9dd)
There was a problem hiding this comment.
This report is automatically generated by the PR / Check / cherry-pick CI workflow.
Some of the commits in this PR require the author's and reviewer's attention.
Sometimes it is not possible to cherry-pick exactly the same patch.
This most frequently happens when resolving merge conflicts.
The range-diff will help to review the resolution of conflicts.
If you need to merge this PR despite the warnings, please dismiss this review shortly before merging.
Warning
Difference between 838c3f9 and original 64db9dd may warrant inspection.
Show diff
@@ Metadata
## Commit message ##
cosmic-greeter: apply upstream patch for security hardening
+ (cherry picked from commit 64db9dd59be49b07d88409084dd94c1cf34b5097)
+
## pkgs/by-name/co/cosmic-greeter/package.nix ##
@@
nix-update-script,
@@ pkgs/by-name/co/cosmic-greeter/package.nix
rustPlatform.buildRustPackage (finalAttrs: {
@@ pkgs/by-name/co/cosmic-greeter/package.nix: rustPlatform.buildRustPackage (finalAttrs: {
- hash = "sha256-U0JrxvMWzISSA0tP8moasN7iN7TfZreEwbvWZGHRn8E=";
+ hash = "sha256-HP2Dl/vEX4K3XaXtjOpN1EW6uE4RuLm2+RMLB3QvOXQ=";
};
-- cargoHash = "sha256-sNJTXBInr/h8w5dhOOP9ceBYWBcJW3qGjDuaG6UTV90=";
-+ cargoHash = "sha256-J5ycaeKZsEBPcI9JH8bHsOAcXXwcx/D21GlVhJZbGwM=";
+- cargoHash = "sha256-4yRBgFrH4RBpuvChTED+ynx+PyFumoT2Z+R1gXxF4Xc=";
++ cargoHash = "sha256-KLIUE3+iAZbNB6YPSl75I6jHwa1RBN+go5A7RFi5LxE=";
+
+ cargoPatches = [
+ (fetchpatch2 {
@@ pkgs/by-name/co/cosmic-greeter/package.nix: rustPlatform.buildRustPackage (final
+ })
+ ];
- env.VERGEN_GIT_SHA = finalAttrs.src.tag;
-
+ env = {
+ VERGEN_GIT_COMMIT_DATE = "2025-12-05";
Hint: The full diffs are also available in the runner logs with slightly better highlighting.
|
I was alerted a bit when viewing the patch from GitHub's UI shows "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository." but its not a problem because I recall pulling the commit from the PR but GitHub didn't fast-forward it, hence the change in has for the commit SHA in the PR vs in-tree. Commenting for documentation purposes. |
|
|
|
@NixOS/nixpkgs-merge-bot |
|
@NixOS/nixpkgs-merge-bot merge |
|
@thefossguy wants to merge this PR. Requirements to merge this PR with
❌ Pull Request could not be merged (#305350) |
|
My bad, I thought Kenji was a committer. I don't have commit access either. |
Reviewed cherry-pick range-diff. Differences are expected for release-25.11
fd28b91
(cherry picked from commit 64db9dd)
Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.