Comment 12 for bug 1957320

Thank you for the excellent investigation and analysis!

Staging the fix would definitely not make it worse for any user, right? However, staging it would mean that new production users won't get the fix and would break on next upgrade.

nginx has already had three updates in Jammy so it seems likely that it will have many more. So not fixing this would be worse.

As you've considered, it would be better if we could have it not break an affected user even the first time, but I agree that does not seem practical.

I wondered about trying to flag the situation via debconf in the preinst, or even blocking the upgrade in case of non-attended installation, but that also seems worse. For example a security update might never land via unattended-upgrades in this case.

Unless someone comes up with something better, I think releasing the SRU as normal while acknowledging the breakage for affected users here is the least worst option.