I'm not sure what changed, but this issue seems to have gone away, at least from preventing nghttp2 from migrating:
$ rmad nghttp2 nghttp2 | 1.43.0-1build3 | jammy nghttp2 | 1.47.0-1 | kinetic
nghttp2 | 1.43.0-1 | stable nghttp2 | 1.47.0-1 | testing nghttp2 | 1.47.0-1 | unstable nghttp2 | 1.47.0-1 | unstable-debug
I'm not sure what changed, but this issue seems to have gone away, at least from preventing nghttp2 from migrating:
$ rmad nghttp2
nghttp2 | 1.43.0-1build3 | jammy
nghttp2 | 1.47.0-1 | kinetic
nghttp2 | 1.43.0-1 | stable
nghttp2 | 1.47.0-1 | testing
nghttp2 | 1.47.0-1 | unstable
nghttp2 | 1.47.0-1 | unstable-debug