Servers supporting Acquire-By-Hash may break verbatim publications
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 71
- Forks
- 91
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 22
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
Contributor 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.
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.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100