Pulp creates Release files in the outer folder (stretch/updates)
The latest pulp_deb that supports nested release folders (for example, debian security http://security-cdn.debian.org/debian-security/dists/stretch/updates) puts the Release and Release.gpg into the outer folder (/dists/stretch/Release), however, the files should be placed into the inner folder (/dists/stretch/updates/Release).
This leads to the following warning on debian:
apt-get update ... Fetched 791 kB in 0s (2,069 kB/s) Reading package lists... Done W: The repository 'https://<pulp_host>/<path> stretch/updates Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details.
If both the Release files and Release.gpg are moved to the inner folder, the warning disappears:
apt-get update ... Fetched 1,672 B in 0s (5,455 B/s) Reading package lists... Done
The commands that have been used to create the repo:
pulp-admin deb repo create --repo-id <repo_id> --relative-url <relative_url> --feed http://security.debian.org/debian-security --basicauth-user <basic_user> --basicauth-pass <basic_pass> --serve-https true --serve-http false --releases stretch/updates --components main,contrib,non-free --architectures amd64 pulp-admin deb repo publish run --repo-id <repo_id> pulp-admin deb repo sync run --repo-id <repo_id>
Add the distribution field to the DB models
Within a standard Debian repository structure, the term "distribution"
refers to the unique string given by the path segment between the
"dists/" folder, and some "Release" file (without the trailing slash).
Since each "Release" file in the directory structure is associated with
exactly one unique distribution string, the terms "distribution" and
"release" can be (and often are) used interchangably.
The distribution string is most commonly (but not always) given by
either the "codename" or the "suite". The pulp_deb implementation prior
to this commit, has assumed that the distribution string is always equal
to codename, and has therefore imposed a uniqueness constraint on the
codename for all releases/distributions within a single repository.
Since upstream repository sources make no such assumption and are not
necessarily structured using the codename, this has lead to a plathora
of unpredictable and buggy behaviour when synchronizing upstream
repositories with 'codename != distribution'.
This change fixes these problems by introducing and using a
"distribution" field for both the units_deb_release and
Please register to edit this issue