Bug#1061450: dpkg-dev: Please add bash completion for dpkg-buildpackage

--0000000000007796510656f8d993
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Guillem,

Apologies for the slow reply =E2=80=94 work has been keeping me busy these =
past
few weeks.

I see the transfer has landed in the meantime: bash-completion deprecated
its dpkg completions, and the import plus the dpkg-source rework are now
on dpkg main. Nice!

Since scripts/completion/bash/ only has dpkg-source so far, I'd like to
take dpkg-buildpackage as discussed =E2=80=94 bash only, following the styl=
e and
layout of the dpkg-source file on main. If you've already started on it
locally, sorry for the delay, just tell me and I'll pick another program
instead.

Would you prefer a merge request on Salsa, or a patch to this bug?

Best regards,
Cheng Li

Guillem Jover <[email protected]> =E4=BA=8E2026=E5=B9=B46=E6=9C=882=E6=97=
=A5=E5=91=A8=E4=BA=8C 11:32=E5=86=99=E9=81=93=EF=BC=9A

> Hi!
>
> On Tue, 2026-05-19 at 18:21:32 +0800, Cheng Li wrote:
> > I'm new to Debian contribution and came across this bug via the
> > `newcomer` tag. Before I write anything, two quick questions so I
> > don't duplicate or conflict with the upstream bash-completion
> > integration you mentioned (pu/merge-bash-completions /
> > scop/bash-completion#694):
>
> I've now submitted an MR to bash-completion upstream to be able to
> unblock this and take over the completions in dpkg, which I'd be
> planning on doing for 1.23.8, where I'm refreshing the
> pu/merge-bash-completions branch, which I'll try to update tomorrow
> or so.
>
> > 1. Is dpkg-buildpackage completion still open for an outside
> >    contribution,
>
> Sure thing! For bash sure, for zsh I see that this is already
> provided by zsh upstream (but I'm not sure how up-to-date it is).
>
> >    or has it been absorbed into your upstream work
> >    since then?
>
> I've not added anything new relative to bash-completion upstream,
> but would consider starting to work on bash-completion improvements
> and additions once the transfer has been coordinate. Let me know if
> you'd like to start on any program and I'll hold off on those. I'm
> unlikely to work on zsh as I don't use it, but I'm happy to merge
> zsh completions.
>
> > 2. If still open, would you prefer the initial patch to add a zsh
> >    completion only (matching the existing `_dpkg-parsechangelog`
> >    style under `scripts/completion/zsh/`), or bash + zsh together?
>
> Given what I mention above that zsh already ships completions for it,
> I think bash-only would be easiest, as I'm not sure what's zsh stance
> on where they prefer to maintain these. But if you or someone else
> would like to check how an ownership transfer could be done from zsh
> to dpkg, although that might imply rewriting the zsh completion from
> scratch (clean room etc) to avoid having to use the Zsh license in
> dpkg, then I'd be happy to merge such new completions.
>
> So from my PoV, both would be ideal, but feel free to work on the ones
> you are most interested in. In case you work on bash completions,
> please make use of the new bash-completion 2.12 APIs (but not later).
>
> Thanks,
> Guillem
>


--=20
Best regards
Cheng Li

--0000000000007796510656f8d993
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Guillem,<br><br>Apologies for the slow reply =E2=80=94 =
work has been keeping me busy these past<br>few weeks.<br><br>I see the tra=
nsfer has landed in the meantime: bash-completion deprecated<br>its dpkg co=
mpletions, and the import plus the dpkg-source rework are now<br>on dpkg ma=
in. Nice!<br><br>Since scripts/completion/bash/ only has dpkg-source so far=
, I&#39;d like to<br>take dpkg-buildpackage as discussed =E2=80=94 bash onl=
y, following the style and<br>layout of the dpkg-source file on main. If yo=
u&#39;ve already started on it<br>locally, sorry for the delay, just tell m=
e and I&#39;ll pick another program<br>instead.<br><br>Would you prefer a m=
erge request on Salsa, or a patch to this bug?<br><br>Best regards,<br>Chen=
g Li</div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"=
ltr" class=3D"gmail_attr">Guillem Jover &lt;<a href=3D"mailto:guillem@debia=
n.org">[email protected]</a>&gt; =E4=BA=8E2026=E5=B9=B46=E6=9C=882=E6=97=
=A5=E5=91=A8=E4=BA=8C 11:32=E5=86=99=E9=81=93=EF=BC=9A<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">Hi!<br>
<br>
On Tue, 2026-05-19 at 18:21:32 +0800, Cheng Li wrote:<br>
&gt; I&#39;m new to Debian contribution and came across this bug via the<br=
>
&gt; `newcomer` tag. Before I write anything, two quick questions so I<br>
&gt; don&#39;t duplicate or conflict with the upstream bash-completion<br>
&gt; integration you mentioned (pu/merge-bash-completions /<br>
&gt; scop/bash-completion#694):<br>
<br>
I&#39;ve now submitted an MR to bash-completion upstream to be able to<br>
unblock this and take over the completions in dpkg, which I&#39;d be<br>
planning on doing for 1.23.8, where I&#39;m refreshing the<br>
pu/merge-bash-completions branch, which I&#39;ll try to update tomorrow<br>
or so.<br>
<br>
&gt; 1. Is dpkg-buildpackage completion still open for an outside<br>
&gt;=C2=A0 =C2=A0 contribution,<br>
<br>
Sure thing! For bash sure, for zsh I see that this is already<br>
provided by zsh upstream (but I&#39;m not sure how up-to-date it is).<br>
<br>
&gt;=C2=A0 =C2=A0 or has it been absorbed into your upstream work<br>
&gt;=C2=A0 =C2=A0 since then?<br>
<br>
I&#39;ve not added anything new relative to bash-completion upstream,<br>
but would consider starting to work on bash-completion improvements<br>
and additions once the transfer has been coordinate. Let me know if<br>
you&#39;d like to start on any program and I&#39;ll hold off on those. I&#3=
9;m<br>
unlikely to work on zsh as I don&#39;t use it, but I&#39;m happy to merge<b=
r>
zsh completions.<br>
<br>
&gt; 2. If still open, would you prefer the initial patch to add a zsh<br>
&gt;=C2=A0 =C2=A0 completion only (matching the existing `_dpkg-parsechange=
log`<br>
&gt;=C2=A0 =C2=A0 style under `scripts/completion/zsh/`), or bash + zsh tog=
ether?<br>
<br>
Given what I mention above that zsh already ships completions for it,<br>
I think bash-only would be easiest, as I&#39;m not sure what&#39;s zsh stan=
ce<br>
on where they prefer to maintain these. But if you or someone else<br>
would like to check how an ownership transfer could be done from zsh<br>
to dpkg, although that might imply rewriting the zsh completion from<br>
scratch (clean room etc) to avoid having to use the Zsh license in<br>
dpkg, then I&#39;d be happy to merge such new completions.<br>
<br>
So from my PoV, both would be ideal, but feel free to work on the ones<br>
you are most interested in. In case you work on bash completions,<br>
please make use of the new bash-completion 2.12 APIs (but not later).<br>
<br>
Thanks,<br>
Guillem<br>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_s=
ignature"><div dir=3D"ltr">Best regards<div>Cheng Li</div></div></div>

--0000000000007796510656f8d993--