Hello,

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.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature

Reply via email to