Subject: bug#738: actually libfuse3-3

From: Mark Hindley <[email-masked]>
Date: Wed, 25 Jan 2023 19:31:17 +0000

Control: reassign -1 libfuse3-3
Control: found -1 3.12.0-1
Control: fixed -1 3.13.0-1
Control: affects -1 libvirt-daemon-driver-lxc
Control: tags -1 debian upstream

Ferenc and Andreas,

At first sight this is odd and looks as if a library transition might have been
missed in Debian. However, Debian's fuse3 changelog shows no symbol changes
between 3.12 and 3.13:

fuse3 (3.13.0-2) unstable; urgency=medium

  * Can't run self-testing on big-endian machines.

 -- Laszlo Boszormenyi (GCS) <[email-masked]>  Sun, 22 Jan 2023 08:17:08 +0100

fuse3 (3.13.0-1) unstable; urgency=medium

  * New upstream release.

 -- Laszlo Boszormenyi (GCS) <[email-masked]>  Tue, 17 Jan 2023 19:11:25 +0100

fuse3 (3.12.0-1) unstable; urgency=medium

  * New upstream release.
  * Update library symbols for this release.
  * Update watch file.
  * Update Lintian overrides.
  * Update Standards-Version to 4.6.1 .

 -- Laszlo Boszormenyi (GCS) <[email-masked]>  Sat, 22 Oct 2022 21:28:52 +0200

So, looking at fuse3 upstream, it appears that fuse_new_31 was not defined when
HAVE_LIBC_VERSIONED_SYMBOLS was not set and recently fixed upstream[1].

That upstream fix is included in 3.13.

So I suspect this is a Debian bug in 3.12 where the symbol is not defined. I am
surprised that nobody else has bumped into it and reported it.

Alternatively, fuse3 3.13 should migrate to testing in 2 days[2], which
should fix it.

HTH

Mark

[1]  https://github.com/libfuse/libfuse/commit/d372d3f80b5437e652ea501d8a4a917f7001b9d7

[2]  https://qa.debian.org/excuses.php?package=fuse3