On Mon, 19 Jan 2026 18:30:42 +0100, Dominique Dumont wrote:
With 3.017: - a bug fix to not write a value that is identical to upstream_default value - a conditional setup where upstream_default is optional for Std-version >= 4.7.3 and default is optional for Std-version < 4.7.3 The second change is what writes back Priority/optional field with Std-version = 4.7.2.
Ack, thanks.
However, cme cannot decide if user wants to reformat without changing anything (dpt-fixup) or want to drop unnecessary fields (Andreas' bug). So you may have case where Priority/optional is dropped when running «cme modify dpkg-control -save».What do you prefer ?
I thought that `cme modify dpkg-control -save` doesn't change anything (no modifications requested), and that `cme fix dpkg-control` (as used by Andreas, and also by dpt-fixup later) is supposed to change/fix things. Looking at cme(1p) still makes me believe that this is not a completely stupid assumption :)
Taking a step back: The idea of running `cme modify dpkg-control -save` early is to have the (pure) reformatting in a separate git commit before making any specific changes (also as atomic as possible), and I don't know what's the best way to achieve this. `cme fix` should of course drop "Priority: optional" as requested by Andreas; if `cme modify` without any arguments can be made to act no-changing that would be great, otherwise a `cme reformat` might be an idea? Or `cme run reformat`?
PS: you can use «cme run update-standards-version» instead of these lines:
Oh, nice, thank you! Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe`-
signature.asc
Description: Digital Signature
