[request-tracker-maintainers] Bug#1031587: Handling of the request-tracker4 -> request-tracker5 transition in bookworm

[Adrian Bunk]

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: Dominic Hargreaves <dom at earth.li>, Debian Request Tracker Group <pkg-request-tracker-maintainers at lists.alioth.debian.org>
Control: block 1030749 by -1

https://release.debian.org/testing/freeze_policy.html#soft

...
Dropping or adding binary packages to a source package, moving binaries between source packages or renaming source or binary packages is no longer allowed. Packages with these changes will not be allowed to migrate to testing. These changes are also no longer appropriate in unstable.
...


The problem is that opening of #1030749 is de facto
a request-tracker4 -> request-tracker5 transition that
happened 4 weeks after the deadline for transitions.


There are two options for resolving this:
1. Treat #1030749 as a forbidden transition and ship both versions
   of request-tracker in bookworm, or
2. grant reverse dependencies an exception from the soft freeze
   rules for the request-tracker4 -> request-tracker5 transition.


For option 2 I looked at the 9 reverse dependencies of request-tracker4
in the autoremoval list:

RT extension installer that has to stop depending on
both versions:
- libmodule-install-rtx-perl

No package remame required, has to upgrade to the upstream version
that supports request-tracker5:
- librt-extension-commandbymail-perl

Ships packages for both versions and has to drop the
request-tracker4 package:
- rt-extension-assets-import-csv

request-tracker4 -> request-tracker5 transition prepared
in experimental:
- rt-extension-customfieldsonupdate
- rt-extension-calendar
- rt-extension-jsgantt
- rt-extension-nagios
- rt-extension-smsnotify

Update to latest upstream version and package rename required:
- rt-extension-repeatticket