Your message dated Sat, 20 Dec 2025 02:05:26 +0100
with message-id <[email protected]>
and subject line Re: Bug#1123661: Please reconsider undeprecating --auto-commit
with native formats
has caused the Debian Bug report #1123661,
regarding Please reconsider undeprecating --auto-commit with native formats
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.)
--
1123661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123661
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.23.0
Severity: minor
I saw this in a CI log [1]:
225s dpkg-source: warning: --auto-commit is not a valid option for
Dpkg::Source::Package::V3::Native
I think it would be more sensible to treat --auto-commit as "auto
commit *if necessary*" (which is already what it does for "3.0 (quilt)")
and therefore say that for formats that don't need "committing",
it is a no-op.
So I don't think it makes sense to print a warning about it - passing
this option when it's not needed is normal. A tool might reasonably
always pass --auto-commit without even caring what the source format
is. We surely don't expect the authors of a script that calls
dpkg-source to inspect the source format to try to decide whether to
pass --auto-commit or not.
Thanks,
Ian.
[1] https://ci.debian.net/packages/l/lintian/testing/amd64/67253141/#L4872
--
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 ---
--- Begin Message ---
Hi!
On Fri, 2025-12-19 at 16:12:41 +0000, Ian Jackson wrote:
> Package: dpkg
> Version: 1.23.0
> Severity: minor
> I saw this in a CI log [1]:
>
> 225s dpkg-source: warning: --auto-commit is not a valid option for
> Dpkg::Source::Package::V3::Native
>
> I think it would be more sensible to treat --auto-commit as "auto
> commit *if necessary*" (which is already what it does for "3.0 (quilt)")
> and therefore say that for formats that don't need "committing",
> it is a no-op.
>
> So I don't think it makes sense to print a warning about it - passing
> this option when it's not needed is normal. A tool might reasonably
> always pass --auto-commit without even caring what the source format
> is. We surely don't expect the authors of a script that calls
> dpkg-source to inspect the source format to try to decide whether to
> pass --auto-commit or not.
There's no deprecation here at all. Many of the dpkg-source options
are source format specific, and passing them for source formats that
do not know about them has emitted a warning since 2008.
It's the equivalent of passing say --git-ref to a non «3.0 (git)»
format. If there was no warning, then it would be pretty hard to know
when someone passes a non-existing option or a typoed one, etc.
And in the end this is just a warning. So I'm in principle not planning
on changing this general behavior, and will be closing this report with
this email.
Thanks,
Guillem
--- End Message ---
