Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Known fetchpatch and fetchpatch2 issues #266556

Open
4 tasks
pbsds opened this issue Nov 10, 2023 · 2 comments
Open
4 tasks

Known fetchpatch and fetchpatch2 issues #266556

pbsds opened this issue Nov 10, 2023 · 2 comments
Labels
0.kind: bug 5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems

Comments

@pbsds
Copy link
Contributor

pbsds commented Nov 10, 2023

Creating this tracking issue in case a fetchpatch3 ever gets made. These are notable issues in the fetchpatch{,2} normalization:

fixes found in the wild:

@pbsds pbsds mentioned this issue Nov 10, 2023
12 tasks
@pbsds pbsds mentioned this issue Dec 4, 2023
13 tasks
@pbsds
Copy link
Contributor Author

pbsds commented Dec 4, 2023

For those looking for a workaround, use fetchurl with a https://github.com/.../somehash.diff?full_index=1 url to ensure the hash is stable.

?full_index is discussed here: https://github.com/orgs/community/discussions/46034#discussioncomment-4846112

This will not support features like revert = true;

@lheckemann
Copy link
Member

It also seems to mangle concatenated patches that introduce a new file and later patch it, like https://github.com/Alexays/Waybar/compare/Alexays:e7c7ef6...picnoir:f99f08b.patch.

@samueldr samueldr added the 5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug 5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems
Projects
None yet
Development

No branches or pull requests

3 participants