Hi mentors,
I have been targeting package sponsorship requests at experimental
because of "no changes in unstable that are not targeted for trixie" [1]
and I note that "the migration of packages from experimental to unstable
is entirely at discretion of the packagers" [2]. However, I haven't been
able to read up on what workflows are available for this migration and
am curious to find out the answer ahead of needing it when the freeze
ends.
It seems a given that a new upload with a new changelog entry and a
later version number will work but are there also options either for a
sponsor to re-upload the same identical package with unchanged changelog
to unstable or is there a semi-automated mechanism featuring something
like britney that can do the same?
And in any of these cases is there an automated removal mechanism for
the redundant package left behind in experimental?
Thanks!
[1]
https://release.debian.org/trixie/freeze_policy.html
[2]
https://wiki.debian.org/DebianExperimental
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)