Issue #5379: pool locations should be handled automatically and dirhashed - Debian Support - Pulp

Actions

Send by e-mail Copy link

Issue #5379

closed

pool locations should be handled automatically and dirhashed

Added by jaymzh about 5 years ago. Updated over 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Sprint/Milestone:

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version - Debian:

Platform Release:

Target Release - Debian:

OS:

Triaged:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Quarter:

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.

Actions

Copy link

Updated by mdellweg about 5 years 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.