Sean Whitton writes ("Bug#1107552: git-debpush's changed suite check"):
> On Mon 09 Jun 2025 at 11:18am +01, Ian Jackson wrote:
> > git-debpush pickiness:
> >
> > git-debpush can easily do this check because it's digging into history
> > anyway to try to find out which quilt mode to use. dgit would maybe
> > have to do something similar if we wanted it to check this.
> >
> > But git-debpush is trying to be less picky than dgit. I think this
> > includes not just trying to avoid conversion failures at the t2u
> > service, but also being picky about things that can be detected
> > synchronously.
> >
> > It seems odd that we have put a check in git-debpush which mitigates a
> > risk that existing upload tooling also fails to mitigate, and for
> > which there are other mitigations, at least some of which can be
> > adopted immediately.
> >
> > [...]
> >
> > Tenative conclusion:
> >
> > This check should be simply removed from git-debpush.
>
> How about we just reduce the scope of the check to particular changes?
>
> For example unstable->experimental would be waved through but not the
> converse.
I don't like this idea for two reasons.
One is that it would involve embed much specific knowledge of Debian
suites (or put them in config or something).
And the other is that I find my arguments above compel the conclusion
that this check just shouldn't be here.
Another way is to look at userbases:
* Existing users of other upload tooling don't expect this check.
* Existing users who don't use UNRELEASED trip over it pointlessly.
* Existing dgit users moving to t2u don't expect this check.
* Uploading to sid after uploading to experimental is a normal change.
I think git-debpush is the wrong place to try to sort this out given
how easy the non-UNRELEASED workflows are (and how easily we could
probably make them work more nicely in forky).
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.