On Sun, 2023-02-19 at 00:12 +0200, Adrian Bunk wrote: > 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.
The soft freeze date snuck up on us. :( Given the minimal impact to packages, is this a transition? If you look at the release and EOL dates on https://bestpractical.com/release-policy/ you'll see that Best Practical typically end of life releases 3-4 years after the next release. 5.0 was released in 2020, therefore it is worth considering that 4.4 will most likely be EOL in 2023 or 2024. For practical support reasons, we're concerned about releasing Bookworm with 4.4. > 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 This will need to updated after all the below packages are updated. > No package remame required, has to upgrade to the upstream version > that supports request-tracker5: > - librt-extension-commandbymail-perl We've had updated packaging ready to go for a while, but it looks like we'd forgotten to upload it. Current proposed package does introduce new packages, but we could drop that and re-use the existing package name. > 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 Some of these will need to be updated, but that is relatively straightforward. > Update to latest upstream version and package rename required: > - rt-extension-repeatticket Again, we have updated packaging ready, again includes new package names. But the splitting into new packages can be dropped. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
