The 3.9.x releases are maintenance releases (see [1]), and as they appear to be bugfix only we could still fix this bug in Kinetic by packaging 3.9.15 (ahead of Debian).
I don't think the package has enough tests to do an "new upstream microrelease" upload: the autopkgtest is just a smoke tests, and the upstream tests are disabled in d/rules, so fixing the bug in Jammy will probably require cherry-picking the right commit.
I didn't setup a reproducer for this one, but the situation looks pretty clear. Currently affected are:
rabbitmq-server | 3.9.13-1 | jammy
rabbitmq-server | 3.9.13-1 | kinetic
The 3.9.x releases are maintenance releases (see [1]), and as they appear to be bugfix only we could still fix this bug in Kinetic by packaging 3.9.15 (ahead of Debian).
I don't think the package has enough tests to do an "new upstream microrelease" upload: the autopkgtest is just a smoke tests, and the upstream tests are disabled in d/rules, so fixing the bug in Jammy will probably require cherry-picking the right commit.
[1] https:/ /rabbitmq. com/github. html