proposed-migration for nginx 1.24.0-2ubuntu6

[Steve Langasek]

nginx 1.24.0-2ubuntu6 changes ABI on armhf after a no-change rebuild. As a result existing binary modules fail to load.
Since nginx 1.24.0 shipped in mantic, this should be handled as a transition, bumping the ABI in the Provides: field.

[Steve Langasek (vorlon)]

unblocking current nginx for migration via removal of existing armhf extensions, but that still means breakage on upgrade if old packages are not removed.

Removing packages from noble:
 libnginx-mod-http-auth-pam 1:1.5.5-2 in noble armhf
 libnginx-mod-http-brotli-filter 1.0.0~rc-5 in noble armhf
 libnginx-mod-http-brotli-static 1.0.0~rc-5 in noble armhf
 libnginx-mod-http-cache-purge 1:2.3-6 in noble armhf
 libnginx-mod-http-dav-ext 1:3.0.0-5 in noble armhf
 libnginx-mod-http-echo 1:0.63-6 in noble armhf
 libnginx-mod-http-fancyindex 1:0.5.2-5 in noble armhf
 libnginx-mod-http-geoip2 1:3.4-5build1 in noble armhf
 libnginx-mod-http-headers-more-filter 1:0.37-2 in noble armhf
 libnginx-mod-http-lua 1:0.10.26-2 in noble armhf
 libnginx-mod-http-memc 0.20-1 in noble armhf
 libnginx-mod-http-ndk 1:0.3.3-1 in noble armhf
 libnginx-mod-http-set-misc 0.33-5 in noble armhf
 libnginx-mod-http-srcache-filter 0.33-3 in noble armhf
 libnginx-mod-http-subs-filter 1:0.6.4-6 in noble armhf
 libnginx-mod-http-uploadprogress 1:0.9.2-5 in noble armhf
 libnginx-mod-http-upstream-fair 1:0.0~git20120408.a18b409-5 in noble armhf
 libnginx-mod-http-js 0.7.12-2 in noble armhf
 libnginx-mod-stream-js 0.7.12-2 in noble armhf
 libnginx-mod-nchan 1:1.3.6+dfsg-4 in noble armhf
 libnginx-mod-rtmp 1:1.2.2+dfsg-5 in noble armhf
Comment: armhf removals
21 packages successfully removed.

[Olivier Gayot (ogayot)]

I just uploaded nginx 1.24.0-2ubuntu7~ppa2 in ogayot/noble-proposed.

Upgraded from 1.24.0-2ubuntu6 to 1.24.0-2ubuntu7~ppa2 forces removal of libnginx-mod-* packages so that seems to work as expected.

https://launchpad.net/~ogayot/+archive/ubuntu/noble-proposed/+build/27962400

Not adding the debdiff yet since we might want to bump the ABI version of nginx modules in debian/libnginx-mod.abisubstvars

[Steve Langasek (vorlon)]

On Tue, Mar 26, 2024 at 06:14:29PM -0000, Olivier Gayot wrote:
> I just uploaded nginx 1.24.0-2ubuntu7~ppa2 in ogayot/noble-proposed.

> Upgraded from 1.24.0-2ubuntu6 to 1.24.0-2ubuntu7~ppa2 forces removal of
> libnginx-mod-* packages so that seems to work as expected.

> https://launchpad.net/~ogayot/+archive/ubuntu/noble-
> proposed/+build/27962400

> Not adding the debdiff yet since we might want to bump the ABI version
> of nginx modules in debian/libnginx-mod.abisubstvars

-nginx:abi=nginx-abi-1.24.0-1
+nginx:abi=nginx-abi-1.24.0-2

What does the '-1' suffix actually mean? Is this somehow defined by
upstream (like an soname) and therefore we should avoid incrementing it
locally in Debian?

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
<email address hidden> <email address hidden>

[Olivier Gayot (ogayot)]

> -nginx:abi=nginx-abi-1.24.0-1
> +nginx:abi=nginx-abi-1.24.0-2
>
> What does the '-1' suffix actually mean? Is this somehow defined by
> upstream (like an soname) and therefore we should avoid incrementing it
> locally in Debian?
>

I will double check. When the nginx:abi variable was first introduced [1]
it was set 1.22.1-7 (same as the debian source package version)
[1]
https://salsa.debian.org/nginx-team/nginx/-/commit/309c257646a7bb8f772d890738742ca27166371f