Your message dated Mon, 26 Dec 2022 13:36:49 +0000
with message-id <[email protected]>
and subject line Re: dgit-maint-native(7) examples should use push-source
(rather than push)
has caused the Debian Bug report #1017725,
regarding dgit-maint-native(7) examples should use push-source (rather than
push)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1017725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017725
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dgit
Version: 9.16
Severity: minor
It strikes me that examples that currently show the `push` sub-command:
dgit -wgf --overwrite push
and
dgit -wgf push
should show the use of the `push-source` sub-command instead, since doing binary
uploads to Debian now prevents migration to testing, so chances are that's not
what most people want to do.
One could perhaps also add a `--with-binary` option for `push` and gently
transition to defaulting to doing source-only uploads unless one specified that
option via config or options.
--- End Message ---
--- Begin Message ---
Version: 10.0
These renamings and docs updates have been done now. dgit push is now
a configurable alias, which we plan to change next release cycle.
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.
--- End Message ---
