[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1124443: debian-policy: misleading information about Priority field in upgrading checklist



Hi Sean,

On 2026-01-01 13:02, Sean Whitton wrote:
> Hello,
> 
> Aurelien Jarno [01/Jan  1:47pm +01] wrote:
> > Package: debian-policy
> > Version: 4.7.3.0
> > Severity: normal
> >
> > Hi,
> >
> > Debian policy 4.7.3.0 stopped recommending the "Priority" field in
> > debian/control file. The upgrading check list contains the corresponding
> > entry:
> >
> > | 5.6.6
> > |    It is no longer recommended to specify the Priority field in source
> > |    package control files.  dpkg now defaults it to "optional".
> >
> > This is misleading information. dpkg indeeds defaults to "optional" if
> > absolutely no priority field is present in the debian/control file. This
> > is also correct for the source package stanza. However for the binary
> > package stanza, it defaults to the value of the source stanza.
> >
> > This misleading information leaded to a wrong check in lintian (see
> > #1124442).
> 
> I see what you mean but am not sure how to reword it.  Do you have a
> suggestion?

I don't know what is the maximum allowed length for the upgrading 
checklist. Waht about that:

  It is no longer recommended to specify the Priority field in source
  package control files.  If the field is omitted, dpkg defaults to
  "optional" for the source package priority, and binary packages
  inherit the priority from the source package.

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

Attachment: signature.asc
Description: PGP signature


Reply to: