Bug#1031802: fuse3: inaccurate information in symbols file (was: Re: libvirt-daemon-driver-lxc: Incorrect dependencies)

2024-03-17 Thread Andrea Bolognani
On Wed, Mar 13, 2024 at 11:06:03AM +, Simon McVittie wrote: > On Sat, 18 Mar 2023 at 14:46:47 +0100, Andrea Bolognani wrote: > > In other words, upstream developers have retroactively added symbols > > (fuse_new_31) to existing symbol groups (FUSE_3.1). > ... > > really this looks like an upstr

Bug#1031802: fuse3: inaccurate information in symbols file (was: Re: libvirt-daemon-driver-lxc: Incorrect dependencies)

2024-03-13 Thread Simon McVittie
On Sat, 18 Mar 2023 at 14:46:47 +0100, Andrea Bolognani wrote: > In other words, upstream developers have retroactively added symbols > (fuse_new_31) to existing symbol groups (FUSE_3.1). ... > really this looks like an upstream > bug in my opinion: even if the function was present in the source >

Bug#1031802: fuse3: inaccurate information in symbols file (was: Re: libvirt-daemon-driver-lxc: Incorrect dependencies)

2023-03-18 Thread Andrea Bolognani
On Thu, Feb 23, 2023 at 01:03:50AM +0100, Vincent Danjean wrote: > After doing a partial upgrade of my system (i.e. only libvirt-daemon > with its required dependencies), libvirtd refused to start. > In systemd journal, I can see: > > févr. 23 00:53:32 eyak libvirtd[3010536]: internal error: Faile