There is an argument for removing it though: we don't know if it's still working. But what's worse: a non-working package, or a removed package one? I'm not sure they're very different in this situation.
The main reason for removing packages was that they hold back other changes due to autopkgtest regressions. With fewer packages involved due to updates and britney hints, that's far less problematic now and I don't see a hurry to remove this package. It's worth mentioning that now that I look at this with a fresh mind, I notice that I got a bit confused by how the certbot plugins are organized. The dns-google plugin lives in the certbot git repository but is then uploaded to pypi which serves as the upstream for the python- certbot source package in Debian. Version numbers between certbot and the plugins match but they don't absolutely have to. As a consequence, it might be possible to cherry-pick https://github.com/certbot/certbot/commit/b0d0a832772bc7747f65c2c2c90d0f790fa40f8a . The python-certbot version is a bit older than that patch but mismatches don't look very likely. The patch should apply with no major modification to the current python-certbot-dns-google package (restrict to the effective directory, remove tests (gah!), fix some offsets and fix a conflict in setup.py). My main concern at the moment is that I can't fully test the changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076930 Title: Removal request: python-certbot-dns-google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-dns-google/+bug/2076930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
