Servers supporting Acquire-By-Hash may break verbatim publications
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 40/100
Research direction
Start with the verbatim publisher and the sync handling for Debian Acquire-By-Hash files, then read the Debian Repository Format references linked in the issue. Check how the same files are represented under their hashed paths and how relative_path affects them; done means a verbatim publication includes the required package-index by-hash locations without breaking existing paths.
Written by the indexing model from the issue text.
Description
Author: @quba42 (quba42)
Redmine Issue: 7819, https://pulp.plan.io/issues/7819
If a server supports Acquire-By-Hash (in a Release file), the verbatim publisher will still claim to do so (since it will republish the Release file verbatim). However, the verbatim publisher will not publish the Acquire-By-Hash locations for package indecies, since we do not sync them.
This should be easy to fix, if we add the Acquire-By-Hash to our sync. Note that this will be the same files under a different path which probably relates to the whole relative_path corner case problem? (I have forgotten what exactly the latest state of that problem/discussion was).
See
- Dominant language
- Python
- Stars
- 72
- Forks
- 91
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pulp/pulp_deb
-
Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Sync fails for a flat repo whose Release lists only SHA512 checksums (PackageIndex requires sha256)Open
Difficulty 3/5 1-2 days Newbie friendliness 78/100
pulp/pulp_deb#1528 · 1 comment ·
Maintainers usually reply within 1 day
-
Triage-Needed
Difficulty 5/5 Over a week Newbie friendliness 35/100
pulp/pulp_deb#1515 · 2 comments ·
Maintainers usually reply within 1 day
-
.bugfix
Difficulty 3/5 1-2 days Newbie friendliness 55/100
pulp/pulp_deb#1507 · 9 comments ·
Maintainers usually reply within 1 day
-
Remote not signedOpenTriage-Needed
Difficulty 3/5 1-2 days Newbie friendliness 58/100
pulp/pulp_deb#1498 · 6 comments ·
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
awslabs/visual-asset-management-system#414 ·
Maintainers usually reply within 1 day
-
bug v1 v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/python-sdk#3670 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aicell-lab/bioengine#232 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
modelscope/evalscope#1836 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100