Your message dated Fri, 21 Oct 2016 09:35:08 +1300
with message-id <20161020203508.le7hnwx33wy7k...@survex.com>
and subject line Re: Bug#825704: swift-im: should it be removed from Debian?
has caused the Debian Bug report #825704,
regarding swift-im: should it be removed from Debian?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
825704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 `-
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Sat, May 28, 2016 at 11:27:28PM +0000, Mattia Rizzolo wrote:
> 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
The recent upload of 3.0.4-1 addresses most of the above (including #797279
which wasn't listed in the changelog entry, but was fixed and has now been
closed):
Format: 1.8
Date: Fri, 03 Jun 2016 15:56:20 +0100
Source: swift-im
Binary: libswiften3 libswiften-dev swift-im
Architecture: source amd64
Version: 3.0.4-1
Distribution: unstable
Urgency: low
Maintainer: Swift Package Maintainer <packa...@swift.im>
Changed-By: Kevin Smith <ke...@kismith.co.uk>
Description:
libswiften-dev - XMPP library (development files)
libswiften3 - XMPP library
swift-im - easy to use Jabber/XMPP chat client
Closes: 745807 757554 784532 810839 822131
Changes:
swift-im (3.0.4-1) unstable; urgency=low
.
* New upstream release
* Allow compiling with newer boosts. Closes: 810839, 822131
* Switch to Qt5 instead of Qt4. Closes: 784532, 745807
* Fix some platform detection in build system. Closes: 757554
* Rewrite rules file with dh sequencer.
* Drop -dbg package.
Hence closing this bug.
Cheers,
Olly
--- End Message ---
