There’s a new package in the process of being uploaded. The version I produced a few days ago accidentally used an old lint profile, but I’ll fix that imminently.
/K > On 29 May 2016, at 00:27, Mattia Rizzolo <mat...@debian.org> wrote: > > Source: swift-im > Version: 2.0+dev6-1 > Severity: serious > > Dear maintainer, > > swift-im: > > * has few users https://qa.debian.org/popcon.php?package=swift-im > * has 2 unanswered RC bugs since 9 months #797279 #822131 > * FTBFS > * several other bugs with no action taken (and waiting for the next big > upstream is no reason for that, uploads fixing stuff can be done > nevertheless; also, cherry-pick is a thing and stuff fixed in the next > release could be backported; and if this is too much of a delta, then > you should probably release it more often) > * no uploads since 2013 > * hinders openssl decruft > > This package looks all in all in a bad shape, and I wonder whether it > would be better to be without it instead. > > > > > RM: swift-im -- RoQA; FTBFS; RC-buggy; FTBFS; unmaintained; low popcon > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > more about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
