Bug#964518: nanoblogger: replace transitional bsdmainutils dependency
Package: nanoblogger Version: 3.4.2-8 Severity: important Dear Maintainer, your package currently Depends on bsdmainutils, which has become a transitional package. Please change the dependency to one of the replacement packages: * bsdutils * bsdextrautils * calendar * ncal * vacation Thanks, Chris
Bug#964519: svtools: replace transitional bsdmainutils dependency
Package: svtools Version: 0.6-4 Severity: important Dear Maintainer, your package currently Depends on bsdmainutils, which has become a transitional package. Please change the dependency to one of the replacement packages: * bsdutils * bsdextrautils * calendar * ncal * vacation Thanks, Chris
Bug#1084475: fosfat: move from fuse to fuse3
Package: fosfat Version: 0.4.0-13-ged091bb-5 Severity: normal Dear Maintainer, your package currently (Build-)Depends on fuse - that is fuse 2.x, it being obsolete. A newer version of fuse, fuse3, is available since at least buster. Please migrate your package to the fuse3 library, which is actively maintained. It would be great if we could remove fuse 2.x in the forky development cycle. If you cannot migrate yet, please at least update your Depends: line. If you currently have: > Depends: fuse please update that to: > Depends: fuse3 (>= 3.10.1-3) | fuse (<< 3) This allows mount.fuse and fusermount to be provided by fuse3, which is what the majority of new installs already have [1]. You should still migrate from libfuse 2.x to libfuse 3.x later. fuse upstream noted important differences in [2]. [1] compare https://qa.debian.org/popcon.php?package=fuse and https://qa.debian.org/popcon.php?package=fuse3 [2] https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0
Bug#1084485: zfs-fuse: move from fuse to fuse3
Package: zfs-fuse Version: 0.7.0-29 Severity: normal Dear Maintainer, your package currently (Build-)Depends on fuse - that is fuse 2.x, it being obsolete. A newer version of fuse, fuse3, is available since at least buster. Please migrate your package to the fuse3 library, which is actively maintained. It would be great if we could remove fuse 2.x in the forky development cycle. If you cannot migrate yet, please at least update your Depends: line. If you currently have: > Depends: fuse please update that to: > Depends: fuse3 (>= 3.10.1-3) | fuse (<< 3) This allows mount.fuse and fusermount to be provided by fuse3, which is what the majority of new installs already have [1]. You should still migrate from libfuse 2.x to libfuse 3.x later. fuse upstream noted important differences in [2]. [1] compare https://qa.debian.org/popcon.php?package=fuse and https://qa.debian.org/popcon.php?package=fuse3 [2] https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0
Bug#1084421: plptools: move from fuse to fuse3
Package: plptools Version: 1.0.13-3 Severity: normal Dear Maintainer, your package currently (Build-)Depends on fuse - that is fuse 2.x, it being obsolete. A newer version of fuse, fuse3, is available since at least buster. Please migrate your package to the fuse3 library, which is actively maintained. It would be great if we could remove fuse 2.x in the forky development cycle. If you cannot migrate yet, please at least update your Depends: line. If you currently have: > Depends: fuse please update that to: > Depends: fuse3 (>= 3.10.1-3) | fuse (<< 3) This allows mount.fuse and fusermount to be provided by fuse3, which is what the majority of new installs already have [1]. You should still migrate from libfuse 2.x to libfuse 3.x later. fuse upstream noted important differences in [2]. [1] compare https://qa.debian.org/popcon.php?package=fuse and https://qa.debian.org/popcon.php?package=fuse3 [2] https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0
Bug#1084407: tup: move from fuse to fuse3
Package: tup Version: 0.7.11-5 Severity: normal Dear Maintainer, your package currently (Build-)Depends on fuse - that is fuse 2.x, it being obsolete. A newer version of fuse, fuse3, is available since at least buster. Please migrate your package to the fuse3 library, which is actively maintained. It would be great if we could remove fuse 2.x in the forky development cycle. If you cannot migrate yet, please at least update your Depends: line. If you currently have: > Depends: fuse please update that to: > Depends: fuse3 (>= 3.10.1-3) | fuse (<< 3) This allows mount.fuse and fusermount to be provided by fuse3, which is what the majority of new installs already have [1]. You should still migrate from libfuse 2.x to libfuse 3.x later. fuse upstream noted important differences in [2]. [1] compare https://qa.debian.org/popcon.php?package=fuse and https://qa.debian.org/popcon.php?package=fuse3 [2] https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0
Bug#1084415: rdiff-backup-fs: move from fuse to fuse3
Package: rdiff-backup-fs Version: 1.0.0-8 Severity: normal Dear Maintainer, your package currently (Build-)Depends on fuse - that is fuse 2.x, it being obsolete. A newer version of fuse, fuse3, is available since at least buster. Please migrate your package to the fuse3 library, which is actively maintained. It would be great if we could remove fuse 2.x in the forky development cycle. If you cannot migrate yet, please at least update your Depends: line. If you currently have: > Depends: fuse please update that to: > Depends: fuse3 (>= 3.10.1-3) | fuse (<< 3) This allows mount.fuse and fusermount to be provided by fuse3, which is what the majority of new installs already have [1]. You should still migrate from libfuse 2.x to libfuse 3.x later. fuse upstream noted important differences in [2]. [1] compare https://qa.debian.org/popcon.php?package=fuse and https://qa.debian.org/popcon.php?package=fuse3 [2] https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0
Bug#1084419: obexftp: move from fuse to fuse3
Package: obexftp Version: 0.24-10 Severity: normal Dear Maintainer, your package currently (Build-)Depends on fuse - that is fuse 2.x, it being obsolete. A newer version of fuse, fuse3, is available since at least buster. Please migrate your package to the fuse3 library, which is actively maintained. It would be great if we could remove fuse 2.x in the forky development cycle. If you cannot migrate yet, please at least update your Depends: line. If you currently have: > Depends: fuse please update that to: > Depends: fuse3 (>= 3.10.1-3) | fuse (<< 3) This allows mount.fuse and fusermount to be provided by fuse3, which is what the majority of new installs already have [1]. You should still migrate from libfuse 2.x to libfuse 3.x later. fuse upstream noted important differences in [2]. [1] compare https://qa.debian.org/popcon.php?package=fuse and https://qa.debian.org/popcon.php?package=fuse3 [2] https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0
Bug#1084425: obexfs: move from fuse to fuse3
Package: obexfs Version: 0.11-3 Severity: normal Dear Maintainer, your package currently (Build-)Depends on fuse - that is fuse 2.x, it being obsolete. A newer version of fuse, fuse3, is available since at least buster. Please migrate your package to the fuse3 library, which is actively maintained. It would be great if we could remove fuse 2.x in the forky development cycle. If you cannot migrate yet, please at least update your Depends: line. If you currently have: > Depends: fuse please update that to: > Depends: fuse3 (>= 3.10.1-3) | fuse (<< 3) This allows mount.fuse and fusermount to be provided by fuse3, which is what the majority of new installs already have [1]. You should still migrate from libfuse 2.x to libfuse 3.x later. fuse upstream noted important differences in [2]. [1] compare https://qa.debian.org/popcon.php?package=fuse and https://qa.debian.org/popcon.php?package=fuse3 [2] https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0
Bug#1084443: gnunet-fuse: move from fuse to fuse3
Package: gnunet-fuse Version: 0.20.0-3 Severity: normal Dear Maintainer, your package currently (Build-)Depends on fuse - that is fuse 2.x, it being obsolete. A newer version of fuse, fuse3, is available since at least buster. Please migrate your package to the fuse3 library, which is actively maintained. It would be great if we could remove fuse 2.x in the forky development cycle. If you cannot migrate yet, please at least update your Depends: line. If you currently have: > Depends: fuse please update that to: > Depends: fuse3 (>= 3.10.1-3) | fuse (<< 3) This allows mount.fuse and fusermount to be provided by fuse3, which is what the majority of new installs already have [1]. You should still migrate from libfuse 2.x to libfuse 3.x later. fuse upstream noted important differences in [2]. [1] compare https://qa.debian.org/popcon.php?package=fuse and https://qa.debian.org/popcon.php?package=fuse3 [2] https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0
