Guillem Jover writes ("Re: Bug#1147288: dgit: Fails its autopkgtest due to
scrapping dpkg-source --version"):
> Ah, forgot to mention, for the future if there's interest I could add a
> --robot modifier to dpkg-source, like it is supported in dpkg, to have
> machine readable output for --version, like this:
>
> $ dpkg --robot --version; echo
> 1.23.11
> $
Thanks. It might be useful to do that for *some* of the calls
to --version in dgit.git, but I don't think i want to do that for (for
example) the call that appears in tag2upload transcripts. Eg, here:
https://lists.debian.org/debian-tag2upload/2026/09/msg00485.html
oracle$ dgit --version
dgit version 16.7~bpo13+1
# builder: oracle$ ./ssh-builder
'[email protected]' ...
builder$ dgit --version
dgit version 16.7
builder$ dpkg-source --version
Debian dpkg-source version 1.23.7.
I think the t2u user wants something "obvious" here and we don't want
to add noise or weird output modes here.
And given that we have a test case checking the output in the email is
as expected, this is always going to break if src:dpkg changes the
output significantly. I don't see a good way round this other than
for me to update the test suite promptly when this situation arises.
src:dgit typically migrates quickly, so I shouldn't delay you by very
much.
FTR I will update the test suite so that it works with both forms of
output from src:dpkg - we need that for backports etc. etc.
Regards,
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.
