Comment 2 for bug 2013423

In the diff for this upload, I see:

--- squid-5.6/debian/NEWS 2023-01-30 23:12:50.000000000 +0000
+++ squid-5.7/debian/NEWS 2023-03-30 10:27:09.000000000 +0000
@@ -1,3 +1,13 @@
+squid (5.7-0ubuntu0.22.10.1) kinetic; urgency=medium
+
+ The ssl_engine directive has been dropped, meaning squid will fail to start
+ for installations using that configuration directive. There is no current
+ workaround for this issue since squid does not provide support for OpenSSL
+ >= 3 Providers yet. You can find more context on that particular change at
+ https://github.com/squid-cache/squid/pull/694.
+
+ -- Athos Ribeiro <email address hidden> Thu, 06 Apr 2023 18:27:15 -0300
+

This indicates that you are breaking compatibility with certain configs that would work today with the 5.6 package, which is not acceptable in SRU.

I would accept either a package which uses a maintainer script to comment out the unsupported ssl_engine option, or a package which patches the code to make references to ssl_engine non-fatal. But we can't regress working user configs in an SRU.