Actions
Issue #6907
closed
Rework release file fields
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:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Right now we are publishing bare bones release files containing the fields:
- Codename
- Architectures
- Components
- the various hash fields
To this we could consider adding:
- Origin (Pulp 3)
- Label (the repository name?)
- Suite (the upstream Suite if available)
- Version (the repository version?)
- Description (user setting?)
Note: For the Date field we already have a separate issue: https://pulp.plan.io/issues/6869
As part of this ticket, we could also consider changing the order of the fields to match upstream Debian. While this is not functionally required, it makes for more human readable release files. (Especially moving the hash fields to the bottom...)
Related issues
Updated by quba42 over 4 years ago
I forgot to mention: At a minimum we should add any fields, we already had for Pulp 2!
Updated by quba42 over 4 years ago
- Related to Issue #6869: Pulp 3 - pulp-deb : Add "Date" metadata in Release file added
Updated by quba42 over 4 years ago
- Related to Issue #6876: Pulp 3 - pulp-deb : Wrong paths in Release file added
Updated by pulpbot over 4 years ago
- Status changed from NEW to POST
Added by msinghal over 4 years ago
Updated by msinghal over 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset 1f2826ce8df59f5f760225a3f9e1735061a124c0.
Updated by quba42 over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Add Release file fields
fixes #6907 https://pulp.plan.io/issues/6907