Bug#1125967: libconfig-model-dpkg-perl: cme can add "Priority: optional"

[gregor herrmann]

On Mon, 19 Jan 2026 19:22:34 +0100, Dominique Dumont wrote:

>On Monday, 19 January 2026 19:01:37 Central European Standard Time you wrote:
>> 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 :)
>The idea I had was more:
>- update format and semantically equivalent changes so you get the same behavior from your application. The change can include:
>  - dropping redundant field/value like Priority/optional
>  - dripping obsolete fields
>  - adding default values
>  - migrating fields (i.e. when a field is deprecated and replaced by another one)
>- a warning requires a user decision to accept or not the change (for instance, one should apply blindly a Standard-Version upgrade)
>I may have to change the wording of cme doc ...

For "modify" or for "fix"? Or, put differently, what's the difference 
between them in your idea?

>> 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`?
>I'll have to think about it.

No hurry, I understand this is complicated, and it's just a minor 
thing.

> That would be quite difficult as cme is designed this way:
>- config tree load data as required (the read routines are called by the tree)
>- config tree performs update, re-ordering and other "minor" changes
>- then data is written back by the tree when needed

Right, that was my assumption.


For my workflow / for dpt-fixup, I thought about:
- replacing `cme modify dpkg-control -save` for formatting with
   either `wrap-and-sort -ast` or
   `debputy reformat --style black --no-linter-exit-code`
   They both seem to have agreed on a common format, just I'm not
   happy with parts of it:
   + putting ${subst:Vars} at the bpttom of Depends
   + putting some build dependencies (like debhelper) before all
     others.
- for the time being, bumping the S-V (with sed etc.) before the call
   to `cme modify dpkg-control -save`, then the latter shouldn't add a 
   removed Priority:optional back.


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
    `-   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-perl-maintainers/attachments/20260121/26211d98/attachment.sig>