Hi, Quick facts.
On Fri, Nov 14, 2025 at 2:47 PM Emilio Pozuelo Monfort <[email protected]> wrote: > On 14/11/2025 14:23, Chris Hofstaedtler wrote: > > * Emilio Pozuelo Monfort <[email protected]> [251114 12:12]: > >> On Tue, 13 Aug 2024 20:05:15 +0200 Chris Hofstaedtler <[email protected]> > >> wrote: > >>> fuse (2.x) and fuse3 are not coninstallable. fuse 2.x should > >>> probably go away. Reason was that src:fuse and src:fuse3 both shipped the fusermount binary for CLI interaction. That caused the package conflict and solved in Trixie with removing this binary from src:fuse. That is, now src:fuse (libraries only) and src:fuse3 (library and the binary) are co-installable. > >> Should every rdep bug block this one? Sounds right to me. The src:fuse support ended in January, 2019 almost seven years ago. Projects should step away from it. Those had time, src:fuse3 is here since december, 2016 which means nine years by now. In short, Forky has to leave src:fuse as soon as possible. > AFAICS of the 45 remaining affected packages (ignoring sid-only packages), > only > apt-cacher-ng is a key package. That sounds bad. I thought apt-cacher-ng is in development, but a quick check shows no activity over a year, even an open security issue affects it. :( Regards, Laszlo/GCS
