Hi! On Thu, 2024-07-18 at 01:30:48 +0200, Guillem Jover wrote: > > A workaround is to detect the dpkg version in use, and if it's >= 1.20.1, > > add --force-remove-protected to the dpkg command-line. > > The expected way to detect whether you might need to pass that option > is to use «dpkg --assert-protected-field» and checking the exit code, > which is the way apt is doing that too.
Ah, sorry, it looks like apt never used that option, because it either waited for the dpkg in the same release to have the support, or assumed that packages would only add the field after a dpkg in stable had the support. So it does not really need to care as much. Thanks, Guillem
