Skip to content

[Backport staging-25.05] python3Packages.msgspec: fix src hash#442010

Merged
vcunat merged 1 commit intostaging-25.05from
backport-416464-to-staging-25.05
Sep 11, 2025
Merged

[Backport staging-25.05] python3Packages.msgspec: fix src hash#442010
vcunat merged 1 commit intostaging-25.05from
backport-416464-to-staging-25.05

Conversation

@nixpkgs-ci
Copy link
Contributor

@nixpkgs-ci nixpkgs-ci bot commented Sep 11, 2025 •
edited by vcunat
Loading

Bot-based backport to staging-25.05, triggered by a label in #416464.

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

@YorikSar @github-actions
python3Packages.msgspec: fix src hash
fc4ca4c 
The source hash changes because they use `$Format:%d$` in their code,
and GitHub can substitute this with different things in different times,
see #84312.

In this case, the diff looks like this:

```
diff -ur /nix/store/v2yfg05q83i154bdi2s96g21zi079rgi-source/msgspec/_version.py /nix/store/94zddrfms1ikx61i0plxnqdd3gavfdzr-source/msgspec/_version.py
--- /nix/store/v2yfg05q83i154bdi2s96g21zi079rgi-source/msgspec/_version.py      1970-01-01 00:00:01.000000000 +0000
+++ /nix/store/94zddrfms1ikx61i0plxnqdd3gavfdzr-source/msgspec/_version.py      1970-01-01 00:00:01.000000000 +0000
@@ -24,7 +24,7 @@
     # setup.py/versioneer.py will grep for the variable names, so they must
     # each be defined on a line of their own. _version.py will just call
     # get_keywords().
-    git_refnames = " (HEAD -> main, tag: 0.19.0)"
+    git_refnames = " (tag: 0.19.0)"
     git_full = "dd965dce22e5278d4935bea923441ecde31b5325"
     git_date = "2024-12-27 11:06:58 -0600"
     keywords = {"refnames": git_refnames, "full": git_full, "date": git_date}
```

Fix the hash and add a comment explaining the situation.

(cherry picked from commit e72eda8)
@nixpkgs-ci nixpkgs-ci bot mentioned this pull request Sep 11, 2025
Merged
8 tasks
@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-linux: 2501-5000 This PR causes many rebuilds on Linux and should target the staging branches. 10.rebuild-darwin: 1001-2500 This PR causes many rebuilds on Darwin and should most likely target the staging branches. 6.topic: python Python is a high-level, general-purpose programming language. 4.workflow: backport This targets a stable branch labels Sep 11, 2025
@nix-owners nix-owners bot requested a review from fabaff September 11, 2025 10:32
@vcunat vcunat merged commit fc4ca4c into staging-25.05 Sep 11, 2025
36 of 38 checks passed
@vcunat vcunat deleted the backport-416464-to-staging-25.05 branch September 11, 2025 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@fabaff fabaff Awaiting requested review from fabaff

Assignees

No one assigned

Labels

4.workflow: backport This targets a stable branch 6.topic: python Python is a high-level, general-purpose programming language. 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-darwin: 1001-2500 This PR causes many rebuilds on Darwin and should most likely target the staging branches. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux: 2501-5000 This PR causes many rebuilds on Linux and should target the staging branches.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@vcunat @YorikSar