Charles Plessy:
Le Sun, Dec 15, 2024 at 09:27:06AM +0100, Niels Thykier a écrit :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`).Hi Niels and Guillem, that sounds good, thank you for proposing it. Can I ask you to expand a bit on how you envision how it plays with the archive overrides system (https://wiki.debian.org/FtpMaster/Override) and why it is better that a default for missing values is provided by dpkg rather by the archive? Have a nice day, Charles
Hi Charles,The default from `dpkg` is **not** intended as a replacement for the FTP Master overrides system, so we envision this will continue unaffected.
Also, this change is about `dpkg` being consistent about *how* the defaults are implemented. However, `dpkg` has *always* provided a default for `.dsc` and `.changes`, which is (as I understand it) what `dak` uses. What changes is that:
1) The default for the `.dsc` and `.changes` no longer will use `-` in
some cases and a "proper" value in other. As an example, in the
`Files` field of the `.changes` Priority and Section would default
to `-` but for the `Package-List` field in the `.dsc` it would use
`unknown`. With this change, both cases will use the same value.
For `Priority`, the new default will be `optional` with is a valid
value for that field and also exceedingly common. For `Section`,
it will be `unknown` (rather than a mix of `-` and `unknown`).
2) The default will also be visible in the control file of the `.deb`.
Since the fields have been de-facto mandatory for the past 15+
years in packaging practice, there will not be a visible effect
right now. Only if you were to start omitting fields would you see
a difference between "old dpkg" and "new dpkg".
Best regards,
Niels
OpenPGP_signature.asc
Description: OpenPGP digital signature
