Bug#1003583: e2fsprogs and libext2fs2 in bullseye-backports missing dependency

[Chris Slycord]

Package: e2fsprogs
Version: 1.46.2-2
Severity: normal

Dear Maintainer,

   * e2fsprogs and libext2fs2 version 1.46.5-2~bpo11+1 are in the bullseye-backports repository
   * both depend on libc6 (>= 2.33) for amd64
   * libc6 versions 2.33 and higher do not exist in bullseye or bullseye-backports repositories
   * Result:
        cannot upgrade to the version of either that are in the backports repo
   * What outcome did you expect instead?
        have neither package placed in backports repo
        or
        have all dependencies of both added to backports


-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-19041-Microsoft
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages e2fsprogs depends on:
ii  libblkid1    2.36.1-8
ii  libc6        2.31-13+deb11u2
ii  libcom-err2  1.46.5-2~bpo11+1
ii  libext2fs2   1.46.2-2
ii  libss2       1.46.5-2~bpo11+1
ii  libuuid1     2.36.1-8
ii  logsave      1.46.5-2~bpo11+1

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  <none>

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  <none>
pn  fuse2fs        <none>
pn  gpart          <none>
pn  parted         <none>

-- no debconf information

[Theodore Ts'o]

found 1003583 e2fsprogs/1.46.5-2~bpo11+1
notfound 1003583 e2fsprogs/1.46.2-2
thanks

> Dear Maintainer,
>
> * e2fsprogs and libext2fs2 version 1.46.5-2~bpo11+1 are in the
> bullseye-backports repository
> * both depend on libc6 (>= 2.33) for amd64
> * libc6 versions 2.33 and higher do not exist in bullseye or
> bullseye-backports repositories
> * Result:
> cannot upgrade to the version of either that are in the backports

Thanks for the bug report. Apparently dgit let me down, in that "dgit
gbp-build" failed to use the proper build chroot, while "gbp
buildpackage" *does* use the correct build chroot.

I had tested first using "gbp buildpackage", and then got taken
surprised when "dgit --quilt=nofix gbp-build" did *not* use the proper
schroot. At a guess, dgit is somehow invoking gbp buildpackage in a
way that causes the debian/gbp.conf is ignored.

In any case, no matter how it happened, the version of e2fsprogs that
dgit uploaded to bullseye-backport was built without a chroot, using
my Debian testing environment. I've tested this and it's quite
reproducible. <Grumble>

I've rebuilt using "gbp buildpackage" directly, which does DTRT, so
I'll reupload without uding dgit, and that should fix the problem.
When have a free day or two, I'll try figure out why dgit surprised
the heck out of me, but until then I'll stop using dgit as an
unreliable/incrutable tool. :-(

- Ted