python-3.13/3.13.11 package update #74858
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
octo-sts
bot
added
automated pr
python-3.13
request-version-update
octo-sts
bot
added
request-version-update
Contributor
Author
🔄 Build Failed: Git Checkout Error
Build Details
Root Cause Analysis 🔍The git cherry-pick operation failed because the specified commit hash 333d4a6f4967d3ace91492a39ededbcf3faa76a6 from branch 3.13 could not be found in the repository. This is a CVE-2025-8291 security patch that appears to be missing from the fetched branch or may have been rebased/modified since the build configuration was created. Was this comment helpful? Please use 👍 or 👎 reactions on this comment. |
Member
|
This is failing because of chainguard-dev/melange#1473. |
sergiodj
added a commit
to sergiodj/melange
that referenced
this pull request
Dec 5, 2025
Melange currently barfs on specific cherry-pick situations like the one at wolfi-dev/os#74858 . I spent some time investigating this and found that this happens because the initial `git clone` to fetch a tag is done in shallow mode, and then subsequent `git fetch` commands will be constrained by the "shallowness" that was created. I was surprised to find @smoser's chainguard-dev#1473 which pretty much reached the same conclusion. My suggestion is that we should bite the bullet here and just invoke the `git fetch` that's run during `cherry-pick` using the `--unshallow` option. The downside is that this will pull in the entire repository history, which can be a lot in some cases. Signed-off-by: Sergio Durigan Junior <sergiodj@chainguard.dev>
This is a workaround for chainguard-dev/melange#1473 Signed-off-by: Sergio Durigan Junior <sergiodj@chainguard.dev>
Member
|
I've pushed a workaround for now (setting |
octo-sts
bot
added
bincapz/pass
xnox
approved these changes
Dec 6, 2025
Member
xnox
left a comment
xnox
left a comment
There was a problem hiding this comment.
Cve mentioned in scan is fixed by this point release.
Also I wonder if cherry picks should have been dropped with new point release. Can figure this out later.
sergiodj
added a commit
to sergiodj/melange
that referenced
this pull request
Dec 8, 2025
Melange currently barfs on specific cherry-pick situations like the one at wolfi-dev/os#74858 . I spent some time investigating this and found that this happens because the initial `git clone` to fetch a tag is done in shallow mode, and then subsequent `git fetch` commands will be constrained by the "shallowness" that was created. I was surprised to find @smoser's chainguard-dev#1473 which pretty much reached the same conclusion. My suggestion is that we should bite the bullet here and just invoke the `git fetch` that's run during `cherry-pick` using the `--unshallow` option. The downside is that this will pull in the entire repository history, which can be a lot in some cases. Signed-off-by: Sergio Durigan Junior <sergiodj@chainguard.dev>
sergiodj
added a commit
to chainguard-dev/melange
that referenced
this pull request
Dec 8, 2025
Melange currently barfs on specific cherry-pick situations like the one at wolfi-dev/os#74858 . I spent some time investigating this and found that this happens because the initial `git clone` to fetch a tag is done in shallow mode, and then subsequent `git fetch` commands will be constrained by the "shallowness" that was created. I was surprised to find @smoser's #1473 which pretty much reached the same conclusion. My suggestion is that we should bite the bullet here and just invoke the `git fetch` that's run during `cherry-pick` using the `--unshallow` option. The downside is that this will pull in the entire repository history, which can be a lot in some cases. Signed-off-by: Sergio Durigan Junior <sergiodj@chainguard.dev>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Commit: 627894459a84be3488a1789919679c997056a03c