Source: fuse3 Version: 3.4.1-1 Severity: important (Original message follows, apparently something went wrong and no bug was created)
---------- Forwarded message --------- From: Mo Zhou <lu...@debian.org> Date: mer 9 gen 2019 alle ore 16:17 Subject: Re: Bug#871019: sshfs: Please update to 3.x To: <sub...@bugs.debian.org> Cc: <871...@bugs.debian.org>, Bartosz Fenski <fe...@debian.org>, Fabio Pedretti <fabio.pedre...@unibs.it> Package: fuse3 Version: 3.4.1-1 Severity: important Dear maintainer, I still cannot co-install fuse3/3.4.1-1 and fuse/2.9.9-1 . gnome-core (depends on ?gvfs? (depends on fuse)) got removed when I'm trying to install fuse3. I packaged sshfs 3.5.1 for myself and used it for a while. The performance improvement compared to 2.X is significant. I hope the co-install problem could be solved so that we'll still have a chance to get sshfs 3.X into Buster. @Bartosz: Do you have plan to upload sshfs 3.X to Buster? If you need help, I volunteer to do it. On Wed, Jan 09, 2019 at 02:32:59PM +0100, Fabio Pedretti wrote: > Il giorno lun 7 gen 2019 alle ore 14:26 Mo Zhou <lu...@debian.org> ha scritto: > > On Mon, Jan 07, 2019 at 12:48:32PM +0100, Fabio Pedretti wrote: > > ~ ❯❯❯ sudo apt install fuse > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > The following packages were automatically installed and are no > longer > > required: > > [...] > > Use 'sudo apt autoremove' to remove them. > > The following packages will be REMOVED: > > fuse3 sshfs sshfs-dbgsym > > The following NEW packages will be installed: > > fuse > > 0 upgraded, 1 newly installed, 3 to remove and 2 not upgraded. > > Need to get 0 B/72.0 kB of archives. > > After this operation, 243 kB disk space will be freed. > > Do you want to continue? [Y/n] > > > > How are they "co-installable"??? > > > > Thanks for the feedback. Since recently released fuse3 3.4.1-1 this > issue > > should be fixed, this bug has more info: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912528 > > > > Are you using 3.4.1-1? If so maybe this issue was not entirely > addressed. > > Yes. The sshfs package as shown above is built by myself[1] > > > I think this is unexpected, given 912528 was supposed to fix this. > > Maybe you could add these info on 912528, or opening a new bug against fuse3, > so that the maintainer has a chance to fix it. > > Thanks. > > > ~ ❯❯❯ apt list libfuse\* --installed > Listing... Done > libfuse2/unstable,unstable,unstable,now 2.9.8-2 amd64 > [installed,automatic] > libfuse3-3/unstable,unstable,unstable,now 3.4.1-1 amd64 > [installed,automatic] > libfuse3-dev/unstable,unstable,unstable,now 3.4.1-1 amd64 [installed] > ~ ❯❯❯ apt list fuse\* --installed > Listing... Done > fuse3/unstable,unstable,unstable,now 3.4.1-1 amd64 [installed,automatic] > ~ ❯❯❯ apt list sshfs\* --installed > Listing... Done > sshfs-dbgsym/now 3.5.1-1 amd64 [installed,local] > sshfs/now 3.5.1-1 amd64 [installed,local] > > [1] https://salsa.debian.org/lumin/sshfs-fuse -- Informativa sulla Privacy: http://www.unibs.it/node/8155 <http://www.unibs.it/node/8155>