Project

Profile

Help

Issue #7819

closed

Servers supporting Acquire-By-Hash may break verbatim publications

Added by quba42 about 4 years ago. Updated almost 3 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Debian:
Platform Release:
Target Release - Debian:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulp_deb/397":https://github.com/pulp/pulp_deb/issues/397


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

Actions #1

Updated by quba42 about 4 years ago

Ideally this will just require adding additional "by hash" artifacts to our package index file units.

I suppose there is no concept of "symlinks" in a pulp repository? It is simply a matter of publishing the same artifact under an extra path?

Actions #2

Updated by quba42 over 3 years ago

  • Sprint/Milestone set to Wishlist
Actions #3

Updated by knzivid over 3 years ago

May I vote for this?

Actions #4

Updated by pulpbot almost 3 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF