Bug#1020267: Essential packages only provide functionality after being configured

[Russ Allbery]

Guillem Jover  writes:
> On Sun, 2022-09-18 at 20:27:46 -0700, Russ Allbery wrote:
>> Helmut Grohne  writes:
>>> […] It can be made explicit in section 3.8 quite easily:

>>>  Since dpkg will not prevent upgrading of other packages while an
>>>  ``essential`` package is in an unconfigured state, all ``essential``
>>>  packages must supply all of their core functionality even when
>>> -unconfigured. If the package cannot satisfy this requirement it must not
>>> +unconfigured after being configured at least once.
>>> +If the package cannot satisfy this requirement it must not
>>>  be tagged as essential, and any packages depending on this package must
>>>  instead have explicit dependency fields as appropriate.

> Seconded.

Thanks, this has been applied for the next release.

-- 
Russ Allbery (r...@debian.org)  

Bug#1020267: Essential packages only provide functionality after being configured

[Guillem Jover]

Hi!

On Sun, 2022-09-18 at 20:27:46 -0700, Russ Allbery wrote:
> Helmut Grohne  writes:
> > […] It can be made explicit in section 3.8 quite easily:
> 
> >  Since dpkg will not prevent upgrading of other packages while an
> >  ``essential`` package is in an unconfigured state, all ``essential``
> >  packages must supply all of their core functionality even when
> > -unconfigured. If the package cannot satisfy this requirement it must not
> > +unconfigured after being configured at least once.
> > +If the package cannot satisfy this requirement it must not
> >  be tagged as essential, and any packages depending on this package must
> >  instead have explicit dependency fields as appropriate.

Seconded.

Thanks,
Guillem


signature.asc
Description: PGP signature