Sean Whitton writes ("Bug#1105815: git-debpush: suggest --force parameter on
errors"):
> On Thu 15 May 2025 at 11:32am +02, Simon Josefsson wrote:
> > Here is another small UX improvement idea. On errors it looks like
> > this:
> >
> > jas@kaka:~/dpkg/gsasl$ git debpush -t
> > git-debpush: check failed: last upload targeted unstable, now targeting
> > experimental; might be a mistake? ('changed-suite' check)
> > git-debpush: some check(s) failed; you can pass --force to ignore them
> > jas@kaka:~/dpkg/gsasl$
> >
> > This is very close to a perfect error message but could be improved by
> > 1) adding keyword 'error:' so the user understands that this is what
> > actually triggers the failure (rather than some unrelated warning), and
> > 2) suggest the --force=changed-suite explicitly to make it more
> > actionable. So how about:
I think what Sean's reply is saying is: the messages, taken together,
*are* actionable - they say "please pass --force".
So maybe "error:" should be added to that line, rather than the check
failed line.
While thinking about this it occurred to me that we could make
git-debpush prompt for confirmation. Sean, IDK if you like that idea.
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.
