On Wed, Sep 5, 2018 at 11:21 AM Adrian Bunk <b...@debian.org> wrote: > We have (sometimes quite popular) packages that are unmaintained > upstream for over 20 years - this is not a problem, actually far > less of a problem than active upstreams breaking various stuff. > > And the package is not unmaintained in Debian, it is maintained by the > Debian QA Group. This is pretty well maintained by Debian standards, > it doesn't happen here that a trivial one-line FTBFS fix does not get > applied for over half a year.
Hmm, so I guess we'll wait 9 months or so and then remove regexxer from Debian? If so, we could still reopen this bug and just mark it buster-ignore or something. Anyway, there are https://salsa.debian.org/gnome-team/gconf https://salsa.debian.org/gnome-team/gconf-editor Let me know where you want those repos to be moved to. Because of issues with the svn-to-gconf conversion, tagged releases might not exactly match what was actually uploaded for that version number. I don't think it really makes sense to keep gconf-editor in Debian. Until you pushed stuff back into Testing, there was only one package in Testing that used gconf (eclipse). Even now, there's really not enough in Testing to justify needing to use gconf-editor to change settings. Thanks, Jeremy Bicha
