Project

Profile

Help

Issue #4705

closed

Pulp creates Release files in the outer folder (stretch/updates)

Added by pulpuser19 about 5 years ago. Updated almost 5 years ago.

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

Description

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>

Related issues

Is duplicate of Debian Support - Issue #4138: Handling publish paths correctlyCLOSED - CURRENTRELEASEquba42Actions

Also available in: Atom PDF