Project

Profile

Help

Issue #5379

pool locations should be handled automatically and dirhashed

Added by jaymzh 7 months ago. Updated 6 months ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Severity:
2. Medium
Version - Debian:
Platform Release:
Blocks Release:
Target Release - Debian:
OS:
Backwards Incompatible:
No
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

Currently when adding content you must tell the pulp_deb plugin what the relative path is. While the ability to specify this is useful, by default, it should create hashed pool directories ala the debian/ubuntu official repos:

http://archive.ubuntu.com/ubuntu/pool/

I would expect to add content called `foo_1.0-1_amd64.deb` and at the very least have the default path be:

pool/f/foo_1.0-1_amd64.deb

In a typical apt repo, it would be something like:

apt/pool/$distribution/f/foo_1.0-1_amd64.deb

But I think Pulp would prefer packages to be able to be associated with multiple repos, thus having the distribution not be part of the content path makes sense.

History

#1 Updated by mdellweg 7 months ago

OK, this one is a little bit odd: There are two publication mechanisms in pulp_deb.
1 Verbatim publication: All files (from all content) are published in the path specified as relative_path; metadata is not generated, but forwarded. That way, you can mirror an upsteam repo (including the original signatures).
2. Simple publication: All packages are published in a single repo component. This time, the publication paths for the packages are generated in the way you described. Metadata is generated (and hopefully in the future signed).

A more complex method for publishing is planned, but it is yet to be determined how to save the necessary data.

#2 Updated by mdellweg 6 months ago

  • Status changed from NEW to MODIFIED

Please register to edit this issue

Also available in: Atom PDF