Home | Devuan | Git | Forum | Packages | Popcon
Donate now!
Download

Devuan logs - #738, boring messages

Message sent to [email protected]:


X-Loop: [email protected]
Subject: bug#738: Fwd: libvirtd
Reply-To: Andreas Messer <[email protected]>, [email protected]
Resent-From: Andreas Messer <[email protected]>
Resent-To: [email protected]
X-Loop: [email protected]
Resent-Date: Wed, 25 Jan 2023 18:46:02 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: report 738
X-Devuan-PR-Package: libvirt-daemon-driver-lxc
X-Devuan-PR-Keywords: 
Received: via spool by [email protected] id=B.167467232332550
          (code B); Wed, 25 Jan 2023 18:46:02 +0000
Received: (at submit) by bugs.devuan.org; 25 Jan 2023 18:45:23 +0000
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 18:45:23 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id xyDEIXd40WM3YAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 18:44:07 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 77BD1597; Wed, 25 Jan 2023 18:44:07 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=ham
	autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a03:4000:24:9b0::1; helo=nyx.bastelmap.de; [email protected]; receiver=<UNKNOWN> 
Received: from nyx.bastelmap.de (nyx.bastelmap.de [IPv6:2a03:4000:24:9b0::1])
	by email.devuan.org (Postfix) with ESMTPS id 0B417396
	for <[email protected]>; Wed, 25 Jan 2023 18:44:01 +0000 (UTC)
Received: from zeus (p200300fb97029c001dfcf8a5c3f6af25.dip0.t-ipconnect.de [IPv6:2003:fb:9702:9c00:1dfc:f8a5:c3f6:af25])
	by nyx.bastelmap.de (Postfix) with ESMTPSA id 297671EAD2A
	for <[email protected]>; Wed, 25 Jan 2023 19:44:01 +0100 (CET)
Date: Wed, 25 Jan 2023 19:43:55 +0100
From: Andreas Messer <[email protected]>
To: [email protected]
Message-Id: <[email protected]>
X-Mailer: geary/3.38.1
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Package: libvirt-daemon-driver-lxc
Version: 8.10.0-3devuan1


Here is a report from a user with symbol resolve issue. According our=20
build log
8.10.0-3devuan1 was build with libfuse3-dev 3.13.0-2. However, in=20
daedalus repos
we have libfuse3 3.12.0-1. Here is the original report:

---------- Weitergeleitete Nachricht ----------
Von: Ferenc G=E1l <[email protected]>
Betreff: libvirtd
Datum: 2023-01-24T21:31:49+0100
An: [email protected]

Hi,

i have noticed an issue with the libvirt daemon or lxc package on=20
Devuan testing:

root@HomePC:~# libvirtd
2023-01-24 20:12:17.468+0000: 12717: info : libvirt version: 8.10.0,=20
package: 3devuan1 (Andreas Messer <[email protected]> Wed, 18 Jan 2023=20
19:20:27 +0100)
2023-01-24 20:12:17.468+0000: 12717: info : hostname: HomePC
2023-01-24 20:12:17.468+0000: 12717: error : virModuleLoadFile:53 :=20
internal error: Failed to load module=20
'/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_lxc.so'=
:=20
/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_lxc.so:=20
undefined symbol: fuse_new_31, version FUSE_3.1

Installed FUSE:
root@HomePC:~# apt search fuse3
Sorting... Done
Full Text Search... Done
fuse3/testing,now 3.12.0-1 amd64 [installed,automatic]
  Filesystem in Userspace (3.x version)

libfuse3-3/testing,now 3.12.0-1 amd64 [installed,automatic]
  Filesystem in Userspace (library) (3.x version)

libfuse3-dev/testing 3.12.0-1 amd64
  Filesystem in Userspace (development) (3.x version)

python3-pyfuse3/testing 3.2.1-2+b1 amd64
  Python 3 bindings for libfuse 3 with asynchronous API

uname -a
Linux HomePC 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1=20
(2023-01-07) x86_64 GNU/Linux

Thanks,
Ferenc

Message sent:


Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
Content-Type: text/plain; charset=utf-8
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Andreas Messer <[email protected]>
Subject: bug#738: Acknowledgement (Fwd: libvirtd)
Message-ID: <[email protected]>
References: <[email protected]>
X-Devuan-PR-Message: ack 738
X-Devuan-PR-Package: libvirt-daemon-driver-lxc
Reply-To: [email protected]
Date: Wed, 25 Jan 2023 18:46:09 +0000

Thank you for filing a new bug report with Devuan.

You can follow progress on this bug here: 738: https://bugs.devuan.org/cgi/=
bugreport.cgi?bug=3D738.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

If you wish to submit further information on this problem, please
send it to [email protected].

Please do not send mail to [email protected] unless you wish
to report a problem with the Bug-tracking system.

--=20
738: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D738
Devuan Bug Tracking System
Contact [email protected] with problems

Message received at [email protected]:


Received: (at control) by bugs.devuan.org; 25 Jan 2023 18:52:55 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 18:52:55 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id HdgxDU960WNwYAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 18:51:59 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 2A788597; Wed, 25 Jan 2023 18:51:59 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=ham
	autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a03:4000:24:9b0::1; helo=nyx.bastelmap.de; [email protected]; receiver=<UNKNOWN> 
Received: from nyx.bastelmap.de (nyx.bastelmap.de [IPv6:2a03:4000:24:9b0::1])
	by email.devuan.org (Postfix) with ESMTPS id 0B2D0396
	for <[email protected]>; Wed, 25 Jan 2023 18:51:56 +0000 (UTC)
Received: from zeus.ad.home.arpa (pd95e1dac.dip0.t-ipconnect.de [217.94.29.172])
	by nyx.bastelmap.de (Postfix) with ESMTPSA id 66AA91EAD4A
	for <[email protected]>; Wed, 25 Jan 2023 19:51:56 +0100 (CET)
Date: Wed, 25 Jan 2023 19:51:55 +0100
From: Andreas Messer <[email protected]>
To: [email protected]
Subject: [Devuan-bugs] bug#738: Fwd: libvirtd
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="lO6Ef4ChkNX0JYPE"
Content-Disposition: inline


--lO6Ef4ChkNX0JYPE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

submitter 738 [email protected]
owner 738 !
thanks
--=20
gnuPG keyid: 8C2BAF51
fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51

--lO6Ef4ChkNX0JYPE
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iF0EABEIAB0WIQQo7oQ45ojZkjZhx1OQs7qqjCuvUQUCY9F6RwAKCRCQs7qqjCuv
USllAJ4hE+eb9mPiFJdnhb4Q6mkpQJJh8gCfYNnqTUCBgSOK9Qj/fdUiirQIA1o=
=DVyV
-----END PGP SIGNATURE-----

--lO6Ef4ChkNX0JYPE--

Message received at [email protected]:


Received: (at control) by bugs.devuan.org; 25 Jan 2023 18:52:55 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 18:52:55 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id HdgxDU960WNwYAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 18:51:59 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 2A788597; Wed, 25 Jan 2023 18:51:59 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=ham
	autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a03:4000:24:9b0::1; helo=nyx.bastelmap.de; [email protected]; receiver=<UNKNOWN> 
Received: from nyx.bastelmap.de (nyx.bastelmap.de [IPv6:2a03:4000:24:9b0::1])
	by email.devuan.org (Postfix) with ESMTPS id 0B2D0396
	for <[email protected]>; Wed, 25 Jan 2023 18:51:56 +0000 (UTC)
Received: from zeus.ad.home.arpa (pd95e1dac.dip0.t-ipconnect.de [217.94.29.172])
	by nyx.bastelmap.de (Postfix) with ESMTPSA id 66AA91EAD4A
	for <[email protected]>; Wed, 25 Jan 2023 19:51:56 +0100 (CET)
Date: Wed, 25 Jan 2023 19:51:55 +0100
From: Andreas Messer <[email protected]>
To: [email protected]
Subject: [Devuan-bugs] bug#738: Fwd: libvirtd
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="lO6Ef4ChkNX0JYPE"
Content-Disposition: inline


--lO6Ef4ChkNX0JYPE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

submitter 738 [email protected]
owner 738 !
thanks
--=20
gnuPG keyid: 8C2BAF51
fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51

--lO6Ef4ChkNX0JYPE
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iF0EABEIAB0WIQQo7oQ45ojZkjZhx1OQs7qqjCuvUQUCY9F6RwAKCRCQs7qqjCuv
USllAJ4hE+eb9mPiFJdnhb4Q6mkpQJJh8gCfYNnqTUCBgSOK9Qj/fdUiirQIA1o=
=DVyV
-----END PGP SIGNATURE-----

--lO6Ef4ChkNX0JYPE--

Message sent to [email protected], Andreas Messer <[email protected]>:


X-Loop: [email protected]
Subject: bug#738: actually libfuse3-3
Reply-To: Mark Hindley <[email protected]>, [email protected]
Resent-From: Mark Hindley <[email protected]>
Resent-To: [email protected]
Resent-CC: Andreas Messer <[email protected]>
X-Loop: [email protected]
Resent-Date: Wed, 25 Jan 2023 19:32:02 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: followup 738
X-Devuan-PR-Package: libvirt-daemon-driver-lxc
X-Devuan-PR-Keywords: 
References: <[email protected]> <[email protected]>
Received: via spool by [email protected] id=B738.16746750943059
          (code B ref 738); Wed, 25 Jan 2023 19:32:02 +0000
Received: (at 738) by bugs.devuan.org; 25 Jan 2023 19:31:34 +0000
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 19:31:34 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id Qu9rLIyD0WNMYQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 19:31:24 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id AAE4C597; Wed, 25 Jan 2023 19:31:24 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id AC5F7396
	for <[email protected]>; Wed, 25 Jan 2023 19:31:19 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pKlUL-0005ln-Ub; Wed, 25 Jan 2023 19:31:18 +0000
Received: (nullmailer pid 16599 invoked by uid 1000);
	Wed, 25 Jan 2023 19:31:17 -0000
Date: Wed, 25 Jan 2023 19:31:17 +0000
From: Mark Hindley <[email protected]>
To: [email protected], [email protected]
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

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 protected]>  Sun, 22 Jan 2023 08:17:08 +0100

fuse3 (3.13.0-1) unstable; urgency=medium

  * New upstream release.

 -- Laszlo Boszormenyi (GCS) <[email protected]>  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 protected]>  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

Message sent:


Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
Content-Type: text/plain; charset=utf-8
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Mark Hindley <[email protected]>
Subject: bug#738: Info received (bug#738: actually libfuse3-3)
Message-ID: <[email protected]>
References: <[email protected]>
X-Devuan-PR-Message: ack-info 738
X-Devuan-PR-Package: libvirt-daemon-driver-lxc
Reply-To: [email protected]
Date: Wed, 25 Jan 2023 19:32:03 +0000

Thank you for the additional information you have supplied regarding
this bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Andreas Messer <[email protected]>

If you wish to submit further information on this problem, please
send it to [email protected].

Please do not send mail to [email protected] unless you wish
to report a problem with the Bug-tracking system.

--=20
738: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D738
Devuan Bug Tracking System
Contact [email protected] with problems

Message received at [email protected]:


Received: (at 738) by bugs.devuan.org; 25 Jan 2023 19:31:34 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 19:31:34 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id Qu9rLIyD0WNMYQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 19:31:24 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id AAE4C597; Wed, 25 Jan 2023 19:31:24 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id AC5F7396
	for <[email protected]>; Wed, 25 Jan 2023 19:31:19 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pKlUL-0005ln-Ub; Wed, 25 Jan 2023 19:31:18 +0000
Received: (nullmailer pid 16599 invoked by uid 1000);
	Wed, 25 Jan 2023 19:31:17 -0000
Date: Wed, 25 Jan 2023 19:31:17 +0000
From: Mark Hindley <[email protected]>
To: [email protected], [email protected]
Subject: Re: bug#738: actually libfuse3-3
Message-ID: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

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 protected]>  Sun, 22 Jan 2023 08:17:08 +0100

fuse3 (3.13.0-1) unstable; urgency=medium

  * New upstream release.

 -- Laszlo Boszormenyi (GCS) <[email protected]>  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 protected]>  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

Message received at [email protected]:


Received: (at 738) by bugs.devuan.org; 25 Jan 2023 19:31:34 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 19:31:34 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id Qu9rLIyD0WNMYQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 19:31:24 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id AAE4C597; Wed, 25 Jan 2023 19:31:24 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id AC5F7396
	for <[email protected]>; Wed, 25 Jan 2023 19:31:19 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pKlUL-0005ln-Ub; Wed, 25 Jan 2023 19:31:18 +0000
Received: (nullmailer pid 16599 invoked by uid 1000);
	Wed, 25 Jan 2023 19:31:17 -0000
Date: Wed, 25 Jan 2023 19:31:17 +0000
From: Mark Hindley <[email protected]>
To: [email protected], [email protected]
Subject: Re: bug#738: actually libfuse3-3
Message-ID: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

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 protected]>  Sun, 22 Jan 2023 08:17:08 +0100

fuse3 (3.13.0-1) unstable; urgency=medium

  * New upstream release.

 -- Laszlo Boszormenyi (GCS) <[email protected]>  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 protected]>  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

Message received at [email protected]:


Received: (at 738) by bugs.devuan.org; 25 Jan 2023 19:31:34 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 19:31:34 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id Qu9rLIyD0WNMYQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 19:31:24 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id AAE4C597; Wed, 25 Jan 2023 19:31:24 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id AC5F7396
	for <[email protected]>; Wed, 25 Jan 2023 19:31:19 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pKlUL-0005ln-Ub; Wed, 25 Jan 2023 19:31:18 +0000
Received: (nullmailer pid 16599 invoked by uid 1000);
	Wed, 25 Jan 2023 19:31:17 -0000
Date: Wed, 25 Jan 2023 19:31:17 +0000
From: Mark Hindley <[email protected]>
To: [email protected], [email protected]
Subject: Re: bug#738: actually libfuse3-3
Message-ID: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

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 protected]>  Sun, 22 Jan 2023 08:17:08 +0100

fuse3 (3.13.0-1) unstable; urgency=medium

  * New upstream release.

 -- Laszlo Boszormenyi (GCS) <[email protected]>  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 protected]>  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

Message received at [email protected]:


Received: (at 738) by bugs.devuan.org; 25 Jan 2023 19:31:34 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 19:31:34 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id Qu9rLIyD0WNMYQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 19:31:24 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id AAE4C597; Wed, 25 Jan 2023 19:31:24 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id AC5F7396
	for <[email protected]>; Wed, 25 Jan 2023 19:31:19 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pKlUL-0005ln-Ub; Wed, 25 Jan 2023 19:31:18 +0000
Received: (nullmailer pid 16599 invoked by uid 1000);
	Wed, 25 Jan 2023 19:31:17 -0000
Date: Wed, 25 Jan 2023 19:31:17 +0000
From: Mark Hindley <[email protected]>
To: [email protected], [email protected]
Subject: Re: bug#738: actually libfuse3-3
Message-ID: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

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 protected]>  Sun, 22 Jan 2023 08:17:08 +0100

fuse3 (3.13.0-1) unstable; urgency=medium

  * New upstream release.

 -- Laszlo Boszormenyi (GCS) <[email protected]>  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 protected]>  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

Message received at [email protected]:


Received: (at 738) by bugs.devuan.org; 25 Jan 2023 19:31:34 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 19:31:34 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id Qu9rLIyD0WNMYQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 19:31:24 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id AAE4C597; Wed, 25 Jan 2023 19:31:24 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id AC5F7396
	for <[email protected]>; Wed, 25 Jan 2023 19:31:19 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pKlUL-0005ln-Ub; Wed, 25 Jan 2023 19:31:18 +0000
Received: (nullmailer pid 16599 invoked by uid 1000);
	Wed, 25 Jan 2023 19:31:17 -0000
Date: Wed, 25 Jan 2023 19:31:17 +0000
From: Mark Hindley <[email protected]>
To: [email protected], [email protected]
Subject: Re: bug#738: actually libfuse3-3
Message-ID: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

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 protected]>  Sun, 22 Jan 2023 08:17:08 +0100

fuse3 (3.13.0-1) unstable; urgency=medium

  * New upstream release.

 -- Laszlo Boszormenyi (GCS) <[email protected]>  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 protected]>  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

Message received at [email protected]:


Received: (at 738) by bugs.devuan.org; 25 Jan 2023 19:31:34 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 19:31:34 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id Qu9rLIyD0WNMYQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 19:31:24 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id AAE4C597; Wed, 25 Jan 2023 19:31:24 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id AC5F7396
	for <[email protected]>; Wed, 25 Jan 2023 19:31:19 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pKlUL-0005ln-Ub; Wed, 25 Jan 2023 19:31:18 +0000
Received: (nullmailer pid 16599 invoked by uid 1000);
	Wed, 25 Jan 2023 19:31:17 -0000
Date: Wed, 25 Jan 2023 19:31:17 +0000
From: Mark Hindley <[email protected]>
To: [email protected], [email protected]
Subject: Re: bug#738: actually libfuse3-3
Message-ID: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

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 protected]>  Sun, 22 Jan 2023 08:17:08 +0100

fuse3 (3.13.0-1) unstable; urgency=medium

  * New upstream release.

 -- Laszlo Boszormenyi (GCS) <[email protected]>  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 protected]>  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

Message received at [email protected]:


Received: (at control) by bugs.devuan.org; 25 Jan 2023 19:36:05 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 19:36:05 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id qHoZEGmE0WNuYQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 19:35:05 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 37C2B597; Wed, 25 Jan 2023 19:35:05 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 5980D396
	for <[email protected]>; Wed, 25 Jan 2023 19:35:04 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pKlXz-0005ol-31
	for [email protected]; Wed, 25 Jan 2023 19:35:03 +0000
Received: (nullmailer pid 17538 invoked by uid 1000);
	Wed, 25 Jan 2023 19:35:03 -0000
From: Mark Hindley <[email protected]>
To: [email protected]
Subject: retitle 738 to Missing symbol fuse_new_31
Date: Wed, 25 Jan 2023 19:35:02 +0000
User-Agent: devscripts bts/2.22.2
Message-ID: <[email protected]>

retitle 738 Missing symbol fuse_new_31
thanks

Message sent to [email protected], [email protected], Andreas Messer <[email protected]>:


X-Loop: [email protected]
Subject: bug#738: actually libfuse3-3
Reply-To: Mark Hindley <[email protected]>, [email protected]
Resent-From: Mark Hindley <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected], Andreas Messer <[email protected]>
X-Loop: [email protected]
Resent-Date: Fri, 27 Jan 2023 14:18:01 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: followup 738
X-Devuan-PR-Package: libfuse3-3
X-Devuan-PR-Keywords: debian upstream
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]>
Received: via spool by [email protected] id=B738.167482899314890
          (code B ref 738); Fri, 27 Jan 2023 14:18:01 +0000
Received: (at 738) by bugs.devuan.org; 27 Jan 2023 14:16:33 +0000
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Fri, 27 Jan 2023 14:16:33 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id dY4LB4Hc02PrRwAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Fri, 27 Jan 2023 14:15:29 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 121B3597; Fri, 27 Jan 2023 14:15:28 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 0C3F592
	for <[email protected]>; Fri, 27 Jan 2023 14:15:23 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pLPVh-0004vC-GI; Fri, 27 Jan 2023 14:15:21 +0000
Received: (nullmailer pid 5591 invoked by uid 1000);
	Fri, 27 Jan 2023 14:15:21 -0000
Date: Fri, 27 Jan 2023 14:15:21 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Cc: [email protected]
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

Ferenc,

On Wed, Jan 25, 2023 at 07:31:17PM +0000, Mark Hindley wrote:
> Alternatively, fuse3 3.13 should migrate to testing in 2 days[2], which
> should fix it.

Debian migrated fuse3 3.13.0-2 to testing[1] this morning. Does upgrading to
that version of libfuse3-3 resolve this bug for you?

Thanks

Mark

[1]  https://tracker.debian.org/news/1413829/fuse3-3130-2-migrated-to-testing/

Message sent to [email protected], [email protected], Andreas Messer <[email protected]>:


X-Loop: [email protected]
Subject: bug#738: actually libfuse3-3
Reply-To: Ferenc =?UTF-8?Q?G=C3=A1l?= <[email protected]>, [email protected]
Resent-From: Ferenc =?UTF-8?Q?G=C3=A1l?= <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected], Andreas Messer <[email protected]>
X-Loop: [email protected]
Resent-Date: Sun, 29 Jan 2023 13:20:01 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: followup 738
X-Devuan-PR-Package: libfuse3-3
X-Devuan-PR-Keywords: debian upstream
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>
Received: via spool by [email protected] id=B738.167499837732148
          (code B ref 738); Sun, 29 Jan 2023 13:20:01 +0000
Received: (at 738) by bugs.devuan.org; 29 Jan 2023 13:19:37 +0000
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Sun, 29 Jan 2023 13:19:37 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id qelqOShy1mNrVwAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Sun, 29 Jan 2023 13:18:32 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id E1D6AA05; Sun, 29 Jan 2023 13:18:32 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS
	autolearn=ham autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::1132; helo=mail-yw1-x1132.google.com; [email protected]; receiver=<UNKNOWN> 
Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132])
	by email.devuan.org (Postfix) with ESMTPS id 03AB9597
	for <[email protected]>; Sun, 29 Jan 2023 13:18:26 +0000 (UTC)
Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-506609635cbso127185907b3.4
        for <[email protected]>; Sun, 29 Jan 2023 05:18:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20210112;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:from:to:cc:subject:date:message-id:reply-to;
        bh=OLGrUq2QavohOzYvOQEz4h0bqUx+XS+Ibmg9KkMRnNg=;
        b=Ozjqbx4w+vSDCRsSfQAONUzeEul5XHlJSjxpG3jJFEh44takyqz53LyFfEiaeQVuic
         SdFswJ8jMaGyySkwACk8+XQ03Q99m4B0ZCx4KAbFm7a9i3Ghl1ANN7y2+niknBJTtAXH
         Ao0NHDzmvX6qEcZEHVOvG4b/q2IJ62gj0pkxsJFWmij7+WW6jEb2drURGekKTm11hAUN
         8tqqbd4+PlWgnl3xc0UxqqLTahxR0w2MR27FelIFwadIkNhf2D6xd9uCrQLYMzSJABxE
         VLuAaUratOoQ+nFj+P9FlHyq3XkkmwtN0H5+qL9WWnBb8UcgODnM867rmC2deWJFT5au
         o+Xw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
         :reply-to;
        bh=OLGrUq2QavohOzYvOQEz4h0bqUx+XS+Ibmg9KkMRnNg=;
        b=t+s+wqFc9w4YsgpsbOa5V/VlJa7K7wZRpMYFJB1XN0YETX6QZ+oM5Icr85y5Zxvqj0
         fgM7QFn2C7irwmBy9kSwTWf7e7Y8HRhstRhtjWsRjoLj3udhG/dVoPZAH4zkV/eBXfDg
         Nraj0/tKpoZ/c5Ey0vVS8WaV1XuZJnyA8eIMT8WKo/Uk6lD/qTBwoTn3YqB2Skr2QPI0
         uz0YdtR0tAL4V4omg5rDzQ3rtq/BwCWiPmqHhjRy2/9yOir5DfEmXWYlqMcdbTNBPBT1
         RhXkFShd+Z+9gubJbDgVvyyZix1IcV8J/BmXmFDS65sKWMAZDfEur2r8MZL34noyfx33
         T0ng==
X-Gm-Message-State: AO0yUKXyjeG0gC12PnIMTnpc0qSBG2UM2/63Wf37olHQVAHovgX0D4Sq
	cmV91MFU0EKvfm5Ht8PnByoXtznLnV+7HtrdaCI=
X-Google-Smtp-Source: AK7set94GqiHT4f/P/6Ndjf2cL0rDqTbaf1KrNnOgoCXbBEIYFeQRxPd3yft5FHpHeiCIV37zh3b50UJO2kZ/dsvxp4=
X-Received: by 2002:a0d:cac3:0:b0:506:3d62:209c with SMTP id
 m186-20020a0dcac3000000b005063d62209cmr3044265ywd.33.1674998305153; Sun, 29
 Jan 2023 05:18:25 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <[email protected]>
From: Ferenc =?UTF-8?Q?G=C3=A1l?= <[email protected]>
Date: Sun, 29 Jan 2023 14:17:33 +0100
Message-ID: <CAFUqQPDzh9ri=Xv8-8t6VE4mHxYmGudd0JwA_Lafne3W=iVVUg@mail.gmail.com>
To: Mark Hindley <[email protected]>
Cc: [email protected]
Content-Type: multipart/alternative; boundary="000000000000fa698f05f366ee76"

--000000000000fa698f05f366ee76
Content-Type: text/plain; charset="UTF-8"

Hi Mark,

yes the issue is solved and the exception message is gone after the upgrade.

Thanks.

Regards,
Ferenc

On Fri, Jan 27, 2023 at 3:15 PM Mark Hindley <[email protected]> wrote:

> Ferenc,
>
> On Wed, Jan 25, 2023 at 07:31:17PM +0000, Mark Hindley wrote:
> > Alternatively, fuse3 3.13 should migrate to testing in 2 days[2], which
> > should fix it.
>
> Debian migrated fuse3 3.13.0-2 to testing[1] this morning. Does upgrading
> to
> that version of libfuse3-3 resolve this bug for you?
>
> Thanks
>
> Mark
>
> [1]
> https://tracker.debian.org/news/1413829/fuse3-3130-2-migrated-to-testing/
>
>

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

<div dir=3D"ltr">Hi Mark,<div><br></div><div>yes the issue is solved and th=
e exception message is gone after the upgrade.</div><div><br></div><div>Tha=
nks.</div><div><br></div><div>Regards,</div><div>Ferenc</div></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 27=
, 2023 at 3:15 PM Mark Hindley &lt;<a href=3D"mailto:[email protected]">m=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">Ferenc,<br>
<br>
On Wed, Jan 25, 2023 at 07:31:17PM +0000, Mark Hindley wrote:<br>
&gt; Alternatively, fuse3 3.13 should migrate to testing in 2 days[2], whic=
h<br>
&gt; should fix it.<br>
<br>
Debian migrated fuse3 3.13.0-2 to testing[1] this morning. Does upgrading t=
o<br>
that version of libfuse3-3 resolve this bug for you?<br>
<br>
Thanks<br>
<br>
Mark<br>
<br>
[1]=C2=A0 <a href=3D"https://tracker.debian.org/news/1413829/fuse3-3130-2-m=
igrated-to-testing/" rel=3D"noreferrer" target=3D"_blank">https://tracker.d=
ebian.org/news/1413829/fuse3-3130-2-migrated-to-testing/</a><br>
<br>
</blockquote></div>

--000000000000fa698f05f366ee76--

Message sent:


Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
Content-Type: text/plain; charset=utf-8
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Ferenc =?UTF-8?Q?G=C3=A1l?= <[email protected]>
Subject: bug#738: Info received (bug#738: actually libfuse3-3)
Message-ID: <[email protected]>
References: <CAFUqQPDzh9ri=Xv8-8t6VE4mHxYmGudd0JwA_Lafne3W=iVVUg@mail.gmail.com>
X-Devuan-PR-Message: ack-info 738
X-Devuan-PR-Package: libfuse3-3
X-Devuan-PR-Keywords: debian upstream
Reply-To: [email protected]
Date: Sun, 29 Jan 2023 13:20:05 +0000

Thank you for the additional information you have supplied regarding
this bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 [email protected]
 Andreas Messer <[email protected]>

If you wish to submit further information on this problem, please
send it to [email protected].

Please do not send mail to [email protected] unless you wish
to report a problem with the Bug-tracking system.

--=20
738: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D738
Devuan Bug Tracking System
Contact [email protected] with problems

Message sent:


MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Mark Hindley <[email protected]>
Subject: bug#738: marked as done (Missing symbol fuse_new_31)
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
X-Devuan-PR-Message: closed 738
X-Devuan-PR-Package: libfuse3-3
X-Devuan-PR-Keywords: debian upstream
Reply-To: [email protected]
Date: Sun, 29 Jan 2023 13:38:01 +0000
Content-Type: multipart/mixed; boundary="----------=_1674999481-32460-0"

This is a multi-part message in MIME format...

------------=_1674999481-32460-0
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Your message dated Sun, 29 Jan 2023 13:37:18 +0000
with message-id <[email protected]>
and subject line Re: bug#738: actually libfuse3-3
has caused the Devuan bug report #738,
regarding Missing symbol fuse_new_31
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


--=20
738: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D738
Devuan Bug Tracking System
Contact [email protected] with problems

------------=_1674999481-32460-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at submit) by bugs.devuan.org; 25 Jan 2023 18:45:23 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 18:45:23 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id xyDEIXd40WM3YAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 18:44:07 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 77BD1597; Wed, 25 Jan 2023 18:44:07 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=ham
	autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a03:4000:24:9b0::1; helo=nyx.bastelmap.de; [email protected]; receiver=<UNKNOWN> 
Received: from nyx.bastelmap.de (nyx.bastelmap.de [IPv6:2a03:4000:24:9b0::1])
	by email.devuan.org (Postfix) with ESMTPS id 0B417396
	for <[email protected]>; Wed, 25 Jan 2023 18:44:01 +0000 (UTC)
Received: from zeus (p200300fb97029c001dfcf8a5c3f6af25.dip0.t-ipconnect.de [IPv6:2003:fb:9702:9c00:1dfc:f8a5:c3f6:af25])
	by nyx.bastelmap.de (Postfix) with ESMTPSA id 297671EAD2A
	for <[email protected]>; Wed, 25 Jan 2023 19:44:01 +0100 (CET)
Date: Wed, 25 Jan 2023 19:43:55 +0100
From: Andreas Messer <[email protected]>
Subject: Fwd: libvirtd
To: [email protected]
Message-Id: <[email protected]>
References:
	<CAFUqQPDvY=wN5Q044chkhEBPBgJn6g7jNvMkgXyGd8edQW0m=A@mail.gmail.com>
X-Mailer: geary/3.38.1
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Package: libvirt-daemon-driver-lxc
Version: 8.10.0-3devuan1


Here is a report from a user with symbol resolve issue. According our=20
build log
8.10.0-3devuan1 was build with libfuse3-dev 3.13.0-2. However, in=20
daedalus repos
we have libfuse3 3.12.0-1. Here is the original report:

---------- Weitergeleitete Nachricht ----------
Von: Ferenc G=E1l <[email protected]>
Betreff: libvirtd
Datum: 2023-01-24T21:31:49+0100
An: [email protected]

Hi,

i have noticed an issue with the libvirt daemon or lxc package on=20
Devuan testing:

root@HomePC:~# libvirtd
2023-01-24 20:12:17.468+0000: 12717: info : libvirt version: 8.10.0,=20
package: 3devuan1 (Andreas Messer <[email protected]> Wed, 18 Jan 2023=20
19:20:27 +0100)
2023-01-24 20:12:17.468+0000: 12717: info : hostname: HomePC
2023-01-24 20:12:17.468+0000: 12717: error : virModuleLoadFile:53 :=20
internal error: Failed to load module=20
'/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_lxc.so'=
:=20
/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_lxc.so:=20
undefined symbol: fuse_new_31, version FUSE_3.1

Installed FUSE:
root@HomePC:~# apt search fuse3
Sorting... Done
Full Text Search... Done
fuse3/testing,now 3.12.0-1 amd64 [installed,automatic]
  Filesystem in Userspace (3.x version)

libfuse3-3/testing,now 3.12.0-1 amd64 [installed,automatic]
  Filesystem in Userspace (library) (3.x version)

libfuse3-dev/testing 3.12.0-1 amd64
  Filesystem in Userspace (development) (3.x version)

python3-pyfuse3/testing 3.2.1-2+b1 amd64
  Python 3 bindings for libfuse 3 with asynchronous API

uname -a
Linux HomePC 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1=20
(2023-01-07) x86_64 GNU/Linux

Thanks,
Ferenc

------------=_1674999481-32460-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at 738-done) by bugs.devuan.org; 29 Jan 2023 13:37:38 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Sun, 29 Jan 2023 13:37:38 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id miWBIZZ21mOKWQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Sun, 29 Jan 2023 13:37:26 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 67EA1A05; Sun, 29 Jan 2023 13:37:26 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id A6FE9597
	for <[email protected]>; Sun, 29 Jan 2023 13:37:20 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pM7ry-0003DI-A4; Sun, 29 Jan 2023 13:37:18 +0000
Received: (nullmailer pid 12126 invoked by uid 1000);
	Sun, 29 Jan 2023 13:37:18 -0000
Date: Sun, 29 Jan 2023 13:37:18 +0000
From: Mark Hindley <[email protected]>
To: Ferenc =?iso-8859-1?B?R+Fs?= <[email protected]>
Cc: [email protected]
Subject: Re: bug#738: actually libfuse3-3
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
 <[email protected]>
 <[email protected]>
 <CAFUqQPDzh9ri=Xv8-8t6VE4mHxYmGudd0JwA_Lafne3W=iVVUg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAFUqQPDzh9ri=Xv8-8t6VE4mHxYmGudd0JwA_Lafne3W=iVVUg@mail.gmail.com>

Version: 3.13.0-1

On Sun, Jan 29, 2023 at 02:17:33PM +0100, Ferenc G�l wrote:
>    Hi Mark,
>    yes the issue is solved and the exception message is gone after the
>    upgrade.

Great. Thanks. Closing

Mark
------------=_1674999481-32460-0--

Message sent:


MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: [email protected]
Subject: bug#738 closed by Mark Hindley <[email protected]> (Re:
 bug#738: actually libfuse3-3)
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
X-Devuan-PR-Message: they-closed 738
X-Devuan-PR-Package: libfuse3-3
X-Devuan-PR-Keywords: debian upstream
Reply-To: [email protected]
Date: Sun, 29 Jan 2023 13:38:04 +0000
Content-Type: multipart/mixed; boundary="----------=_1674999484-32460-1"

This is a multi-part message in MIME format...

------------=_1674999484-32460-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

This is an automatic notification regarding your bug report
which was filed against the libfuse3-3 package:

#738: Missing symbol fuse_new_31

It has been closed by Mark Hindley <[email protected]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mark Hindley <mark@hin=
dley.org.uk> by
replying to this email.


--=20
738: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D738
Devuan Bug Tracking System
Contact [email protected] with problems

------------=_1674999484-32460-1
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at 738-done) by bugs.devuan.org; 29 Jan 2023 13:37:38 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Sun, 29 Jan 2023 13:37:38 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id miWBIZZ21mOKWQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Sun, 29 Jan 2023 13:37:26 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 67EA1A05; Sun, 29 Jan 2023 13:37:26 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id A6FE9597
	for <[email protected]>; Sun, 29 Jan 2023 13:37:20 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pM7ry-0003DI-A4; Sun, 29 Jan 2023 13:37:18 +0000
Received: (nullmailer pid 12126 invoked by uid 1000);
	Sun, 29 Jan 2023 13:37:18 -0000
Date: Sun, 29 Jan 2023 13:37:18 +0000
From: Mark Hindley <[email protected]>
To: Ferenc =?iso-8859-1?B?R+Fs?= <[email protected]>
Cc: [email protected]
Subject: Re: bug#738: actually libfuse3-3
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
 <[email protected]>
 <[email protected]>
 <CAFUqQPDzh9ri=Xv8-8t6VE4mHxYmGudd0JwA_Lafne3W=iVVUg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAFUqQPDzh9ri=Xv8-8t6VE4mHxYmGudd0JwA_Lafne3W=iVVUg@mail.gmail.com>

Version: 3.13.0-1

On Sun, Jan 29, 2023 at 02:17:33PM +0100, Ferenc G�l wrote:
>    Hi Mark,
>    yes the issue is solved and the exception message is gone after the
>    upgrade.

Great. Thanks. Closing

Mark
------------=_1674999484-32460-1
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at submit) by bugs.devuan.org; 25 Jan 2023 18:45:23 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 18:45:23 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id xyDEIXd40WM3YAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 18:44:07 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 77BD1597; Wed, 25 Jan 2023 18:44:07 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=ham
	autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a03:4000:24:9b0::1; helo=nyx.bastelmap.de; [email protected]; receiver=<UNKNOWN> 
Received: from nyx.bastelmap.de (nyx.bastelmap.de [IPv6:2a03:4000:24:9b0::1])
	by email.devuan.org (Postfix) with ESMTPS id 0B417396
	for <[email protected]>; Wed, 25 Jan 2023 18:44:01 +0000 (UTC)
Received: from zeus (p200300fb97029c001dfcf8a5c3f6af25.dip0.t-ipconnect.de [IPv6:2003:fb:9702:9c00:1dfc:f8a5:c3f6:af25])
	by nyx.bastelmap.de (Postfix) with ESMTPSA id 297671EAD2A
	for <[email protected]>; Wed, 25 Jan 2023 19:44:01 +0100 (CET)
Date: Wed, 25 Jan 2023 19:43:55 +0100
From: Andreas Messer <[email protected]>
Subject: Fwd: libvirtd
To: [email protected]
Message-Id: <[email protected]>
References:
	<CAFUqQPDvY=wN5Q044chkhEBPBgJn6g7jNvMkgXyGd8edQW0m=A@mail.gmail.com>
X-Mailer: geary/3.38.1
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Package: libvirt-daemon-driver-lxc
Version: 8.10.0-3devuan1


Here is a report from a user with symbol resolve issue. According our=20
build log
8.10.0-3devuan1 was build with libfuse3-dev 3.13.0-2. However, in=20
daedalus repos
we have libfuse3 3.12.0-1. Here is the original report:

---------- Weitergeleitete Nachricht ----------
Von: Ferenc G=E1l <[email protected]>
Betreff: libvirtd
Datum: 2023-01-24T21:31:49+0100
An: [email protected]

Hi,

i have noticed an issue with the libvirt daemon or lxc package on=20
Devuan testing:

root@HomePC:~# libvirtd
2023-01-24 20:12:17.468+0000: 12717: info : libvirt version: 8.10.0,=20
package: 3devuan1 (Andreas Messer <[email protected]> Wed, 18 Jan 2023=20
19:20:27 +0100)
2023-01-24 20:12:17.468+0000: 12717: info : hostname: HomePC
2023-01-24 20:12:17.468+0000: 12717: error : virModuleLoadFile:53 :=20
internal error: Failed to load module=20
'/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_lxc.so'=
:=20
/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_lxc.so:=20
undefined symbol: fuse_new_31, version FUSE_3.1

Installed FUSE:
root@HomePC:~# apt search fuse3
Sorting... Done
Full Text Search... Done
fuse3/testing,now 3.12.0-1 amd64 [installed,automatic]
  Filesystem in Userspace (3.x version)

libfuse3-3/testing,now 3.12.0-1 amd64 [installed,automatic]
  Filesystem in Userspace (library) (3.x version)

libfuse3-dev/testing 3.12.0-1 amd64
  Filesystem in Userspace (development) (3.x version)

python3-pyfuse3/testing 3.2.1-2+b1 amd64
  Python 3 bindings for libfuse 3 with asynchronous API

uname -a
Linux HomePC 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1=20
(2023-01-07) x86_64 GNU/Linux

Thanks,
Ferenc

------------=_1674999484-32460-1--

Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.

Devuan Bugs Owner <[email protected]>.
Last modified: Thu, 28 Nov 2024 08:39:01 UTC