On Fri, May 22, 2020 at 02:27:48PM +0100, Robie Basak wrote:
> We implemented a least-worst solution there, involving IIRC a
> critical debconf prompt. I don't remember the details, but that might be
Looks like we made the maintainer scripts exit with a success code, but
we always present a debconf critical note first if we haven't been able
to complete. IIRC, we thought that this would be better than breaking a
release upgrade. I think this is limited to dealing with things already
being broken though - for every other type of problem we do exit
non-zero as normal.
It might still be a reasonable pattern to follow if we can't come up
with anything better.