Bug#1127383: dpkg-source: --commit stopped working (no upstream tarball found ...)

On 2026-02-07 Guillem Jover <[email protected]> wrote:
> Control: found -1 1.17.27
> Control: retitle -1 dpkg-source: --commit does not support pathnames to the current source tree directory

> On Sat, 2026-02-07 at 18:30:23 +0100, Andreas Metzler wrote:
> > Package: dpkg-dev
> > Version: 1.23.5
> > Severity: normal

> > dpkg-source --commit stopped working:
> > ametzler@argenau:/tmp/LUMINANCE-HDR$ apt source findutils
> > [...]
> > Fetched 2.277 kB in 1s (2.972 kB/s)
> > dpkg-source: info: extracting findutils in findutils-4.10.0
> > dpkg-source: info: unpacking findutils_4.10.0.orig.tar.xz
> > dpkg-source: info: unpacking findutils_4.10.0-3.debian.tar.xz
> > ametzler@argenau:/tmp/LUMINANCE-HDR$ cd findutils-4.10.0/
> > ametzler@argenau:/tmp/LUMINANCE-HDR/findutils-4.10.0$ echo blah >> NEWS
> > ametzler@argenau:/tmp/LUMINANCE-HDR/findutils-4.10.0$ dpkg-source --commit `pwd`
> > dpkg-source: error: no upstream tarball found at ../findutils_4.10.0.orig.tar.{bz2,gz,lzma,xz}
[...]
> What has worked since the --commit command was introduced was either
> not specifying a directory or specifying it as «.».
[...]

Hello Guillem,

I am quite sure that this used to work *for* *me*. - I had been using
this exact invocation basically since --commit was introduced.

However it also fails for me in fresh trixie and bullseye chroots (on
barriere.d.o.)

I am stumped.

cu Andreas