On Wed, Aug 28, 2024 at 12:59:42PM +0200, Chris Hofstaedtler wrote: > > > > If mono should be removed > > > That's the question that needs to be answered somehow, first. > > > It got another FTBFS bug (#1075284) recently. I've just tried to check > > which packages need mono, with `reverse-depends libmono-system4.0-cil` and > > with dak and skipping libraries and mono-related stuff. > > Thanks for checking! > > > Looks like the main problem is keepass2. > > > > boogie - RFA, not in testing > > dafny - RFA, not in testing > > de4dot - dead upstream > > gbrainy - not in testing > > gnome-subtitles - not in testing > > keepass2 - looks healthy upstream and in Debian > > openmcdf - outdated in Debian but looks healthy upstream > > quickroute-gps - unmaintained, there is some upstream activity > > repetier-host - not in testing > > smuxi - orphaned > > xsddiagram - orphaned > [..] > > > Overall, this doesn't look like a lot of work, *if* we decide to do it > > (and we can file RM bugs for many broken and unmaintained leaf packages in > > any case). > > Maybe we should at least remove packages like gtk-sharp3, which was > removed from testing in September. I'm guessing the maintainers are > long gone. > > gbrainy would need to go away with gtk-sharp3. > > And then we can see about other orphaned and dead users?
Yeah, I'll file RM for at least some of this stuff. I'm also considering formally orphaning everything under pkg-mono-group and pkg-cli-libs-team, that's about 14 packages. https://qa.debian.org/developer.php?email=pkg-cli-libs-team%40lists.alioth.debian.org actually shows we already had a big cleanup of dead mono libs, this will be just the next step. -- WBR, wRAR
signature.asc
Description: PGP signature
