Dear Paul, On 28.04.2023 17:34, Paul Gevers wrote:
I'm not looking at details now, but quoting our policy [1]: """We very strongly prefer changes that can be done via unstable instead of testing-proposed-updates. If there are unrelated changes in unstable, we ask you to revert these changes instead of making an upload to testing-proposed-updates."""
At the same time this guide [1] mentions a newer version in unstable might be a reason for a t-p-u.
You should not upload to testing-proposed-updates when you can update your packages through unstable. If you can't (for example because you have a newer development version in unstable), you may use this facility.
Of course, the policy beats this guide, but I think it might be an indication that this can be a case-by-case decision. Anyway, I have no strong opinions and I trust the decisions of more experienced debian contributors and especially release team, so whatever you think is best will be ok for me. I just want to avoid gummi being removed from bookworm.
Best regards, Martin[1] https://www.debian.org/doc/manuals/developers-reference/pkgs.html#t-p-u
signature.asc
Description: PGP signature
