Control: tags -1 - bullseye + bookworm Control: retitle -1 fuse3: provide upgrade path fuse -> fuse3 for bookworm
On 2021-04-06 21:30:37, Sebastian Ramacher wrote: > Control: severity -1 serious > Control: retitle -1 fuse3: provide upgrade path fuse -> fuse3 for bullseye > > The fuse/fuse3 situation turns out to be an issue for buster -> bullseye > upgrades. Take a minimal buster chroot with ntfs-3g and sshfs installed: > > $ apt-get -y install ntfs-3g sshfs > $ sed 's/buster/bullseye/' -i /etc/apt/sources.list > $ apt-get update > $ apt-get -y dist-upgrade > > After the upgrade, sshfs is still at the version from buster: > > $ apt-cache policy sshfs > sshfs: > Installed: 2.10+repack-2 > Candidate: 3.7.1+repack-1 > Version table: > 3.7.1+repack-1 500 > 500 http://localhost:3142/debian bullseye/main amd64 Packages > *** 2.10+repack-2 100 > 100 /var/lib/dpkg/status > > > Explicitely upgrading sshfs with apt-get install will cause fuse3 to be > installed and fuse to be removed. Thanks to Helmut Grohne for the > reproducer. > > With my release team hat on, I'm raising this issue to serious. We want > to provide working upgrade paths. One possible solution to the problem > would be for src:fuse3 to take over the fuse binary package as > transitional package depending on bin:fuse3. As far as I understand the > situation, all reverse dependencies of fuse should also work with fuse3. This is now being documented in the release notes at https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/92 and should not occur in normal upgrades. Since fixing this issue also involves udeps, let's postponse this for bookworm. Cheers -- Sebastian Ramacher
