Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 107:16:57 |
Calls: | 290 |
Files: | 905 |
Messages: | 76,676 |
both sound good (dropping mandatory priority is nice and consistent,
fixing unknown section behaviour too), thanks!
ideally these changes would be in dpkg in trixie, but maintainers would
start dropping priority fields *after* trixie so that for backports we woudn't need to add it back en masse.
We would like [...] that `dpkg` provides defaults [...] if the fields
are omitted from `debian/control`, you get `Priority: optional` and
`Section: unknown` as default in all artifacts (`.dsc`, `.changes`,
and in the `.deb`).
On Sun, Dec 15, 2024 at 09:50:17AM +0100, Daniel Baumann wrote:
both sound good (dropping mandatory priority is nice and consistent,
fixing unknown section behaviour too), thanks!
indeed! thank you both!
ideally these changes would be in dpkg in trixie, but maintainers would start dropping priority fields *after* trixie so that for backports we woudn't need to add it back en masse.
indeed.
Historically, if you omitted `Priority` and `Section` from your
package, `dpkg` would warn and use `-` or `unknown` as placeholder
when it absolutely needed a value for these fields in the `.dsc` and
the `.changes` file. The resulting `.deb` would omit the field.
We would like to change this behavior such that `dpkg` provides
defaults for these fields. That is, if the fields are omitted from `debian/control`, you get `Priority: optional` and `Section: unknown`
as default in all artifacts (`.dsc`, `.changes`, and in the `.deb`).
# The affected tools
Here are the tools that we are aware of that is or might be affected.
* `dpkg` (such as `dpkg-source`, `dpkg-genchanges`, and
`dpkg-gencontrol`) will need to be updated to implement
the change.
* Maintainer tools such as `lintian`, `debputy [lint|lsp server]`,
etc. should stop warning about missing `Priority` field for
unstable. Most other maintainer facing tools should not care at
all, since the `Priority` field is mostly for d-i.
With `Section` being de facto mandatory, nothing major changes here
for that field.
* `dak` and other archive processing may need tweaking as `-` will
disappear (we can assume all uploads will come from a `dpkg`
version that has these features). Concretely, any special casing
of `-` for `Priority` will be redundant, and any special case
for `-` should apply equally to `unknown` for `Section`.
Though, our understanding is that `dak` likely only uses the cases
where `dpkg` used `unknown` consistently (such the `Package-List`
in the `.dsc`). Accordingly, we suspect it might not need any
changes other than a review to be sure.