Control: severity -1 important
On Fri, Jun 28, 2019 at 05:24:29PM +0200, Jonas Smedegaard wrote: > Justification: renders package unusable This is clearly wrong. > Upstream homepage http://www.policyd-weight.org/ contains a single sentence: > > Project discontinued > > According to > https://web.archive.org/web/20180810082500/http://policyd-weight.org/ and > https://web.archive.org/web/20180317115359/http://www.policyd-weight.org:80/ > this changed a year ago, somewhere between 2018-03-17 and 2018-08-10, and > last upstream release was 2011-09-18. We have many packages in the archive that are dead upstream. Debian is keping quite a number of packages on life-support. The question really is how well it is maintained. I see two bugs: * #891789 (missing systemd .service file) * #891790 (install example config) Outdated standards version. 3 lintian warnings. The package uses debhelper, but not dh. To me this looks like it's not the top of packages, but certainly in releaseable quality. I also happen to know that it just works for me. > Setting severity to grave to keep it out of Buster _unless_ the package > maintainer actively considers this package sane to release with Buster > without upstream support to back it. Given the above, I don't see a good reason not to ship it with buster. Would you also file a grave bug against autoconf2.64, which was released in 2009 and last uploaded 2.5 years ago? Helmut
