So, regarding jammy, and considering we are __not__ introducing a regression in jammy with this MRE because the service already crashes if the ssl_engine configuration option is present, I am wondering if we should still parse the config file and comment the ssl_engine option if that is present to enhance the experience for focal users or if I should just drop that from my MP in https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/squid/+git/squid/+merge/442033 before we proceed.
ATM, I am inclined to drop the postinst and d/NEWS (documenting the ssl_engine option deprecation) changes for jammy.
So, regarding jammy, and considering we are __not__ introducing a regression in jammy with this MRE because the service already crashes if the ssl_engine configuration option is present, I am wondering if we should still parse the config file and comment the ssl_engine option if that is present to enhance the experience for focal users or if I should just drop that from my MP in https:/ /code.launchpad .net/~athos- ribeiro/ ubuntu/ +source/ squid/+ git/squid/ +merge/ 442033 before we proceed.
ATM, I am inclined to drop the postinst and d/NEWS (documenting the ssl_engine option deprecation) changes for jammy.
Thoughts?