git-debpush: error: check failed: last upload targeted unstable but now targeting experimental; use '--force=changed-suite' to override
The last error line above then becomes a bit redundant and could be
removed.
Simon Josefsson writes ("Bug#1105815: git-debpush: suggest --force
parameter on errors"):
git-debpush: error: check failed: last upload targeted unstable but
now
targeting experimental; use '--force=changed-suite' to override
The last error line above then becomes a bit redundant and could be removed.
I like this idea. I might suggest formatting it this way instead to
try to minimise the clutter:
 git-debpush: error: check failed: last upload targeted unstable but
now
 targeting experimental (--force=changed-suite to override)
Package: git-debpush
Version: 12.12
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:
git-debpush: error: check failed: last upload targeted unstable but now targeting experimental; use '--force=changed-suite' to override
The last error line above then becomes a bit redundant and could be
removed.
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:
While thinking about this it occurred to me that we could make
git-debpush prompt for confirmation. Sean, IDK if you like that idea.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 482 |
Nodes: | 16 (2 / 14) |
Uptime: | 59:45:03 |
Calls: | 9,567 |
Calls today: | 1 |
Files: | 13,663 |
Messages: | 6,143,308 |