Debian Bug report logs - #846069
RM: squirrelmail -- RoQA; RC-buggy; little upstream activity

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Ondřej Surý <ondrej@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: RM: squirrelmail -- RoQA; RC-buggy; little upstream activity

Date: Mon, 28 Nov 2016 10:37:55 +0100

Package: ftp.debian.org
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear ftp-masters,

please remove squirrelmail from unstable, it doesn't have PHP 7.0
support and henceforth it's RC-buggy.  I have checked upstream
activity and while there's a little activity in upstream SVN, the
latest stable release was in 2013.

(A fun fact in my RM storm: The squirrelmail logo was designed by my
colleague back in 199x when we deployed squirrelmail for the hosting
company I worked for then :).

Thanks,
Ondrej

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQJ8BAEBCgBmBQJYO/rzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHpksP/2Yp7cMRMOx8bnyhJ15iZQWZ
LSSncfAzew88ND8f/VRdqTZcq2wxVB9qF/1MXGkvF+0M3FRvUgEslT19DfjuGCFa
p7ZUnbEjqqQUATC2rwzGzWiH+ScpNH/RDh5oBbr+dyGq9xLXUHf0Yagd+MIBFqUh
rGOoizfO/xQ7OTaSbjsMh6/9moGOWlDjlcqTdEM25by2Cl08hjKr5fJroEowSwCL
EI6GPCWbT/bky/Ez/XRF/BlLT3gxRKslyHKr6hX4/KpKIoThop5xMgmLKXvvq6v3
hGvJBpq2PKbDbgU5kIrVKaV/R37hmuiy3ZiktupFJQtdVVe8MR+4RL+kmBauOecO
TBJjm0Hc8POxzVgYHIeZpQi7V/5mq90/9UB2GLY3KRN1x/75hbIlK2Z5vS3TvmGp
nEIADjTTwXUWwlncKv2xsDwp9wePQChjVU0IE8dNqZu5gGe1fBz9YACcNvtzW9wc
WTM43hNXP4SbEUC+UKGYzcr+58za0RKXwqfT3fSXIm1boN2u6liTLGjb9zVw2sn0
rymqNgAar/eH5VaP1TGbHH2bGz7H+/2YL7wzWg80G0zJZvdH4KNNonvTUsXniKCp
f0MnsU38gBo16Aq7rouvGxeDF6UQHvOZGcieHmw7EN806cCqu98zRs6hPY3u0mVL
H0uogmLoyw3ipQlM+AeY
=ZIEv
-----END PGP SIGNATURE-----

Message #10 received at 846069@bugs.debian.org (full text, mbox, reply):

From: Scott Kitterman <debian@kitterman.com>

To: 846069@bugs.debian.org, Ondřej Surý <ondrej@debian.org>

Subject: Re: RM: squirrelmail -- RoQA; RC-buggy; little upstream activity

Date: Mon, 28 Nov 2016 07:57:58 -0500

On Mon, 28 Nov 2016 10:37:55 +0100 =?utf-8?b?T25kxZllaiBTdXLDvQ==?= 
<ondrej@debian.org> wrote:
> Package: ftp.debian.org
> Severity: normal
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Dear ftp-masters,
> 
> please remove squirrelmail from unstable, it doesn't have PHP 7.0
> support and henceforth it's RC-buggy.  I have checked upstream
> activity and while there's a little activity in upstream SVN, the
> latest stable release was in 2013.
> 
> (A fun fact in my RM storm: The squirrelmail logo was designed by my
> colleague back in 199x when we deployed squirrelmail for the hosting
> company I worked for then :).

See #844240.  Adding moreinfo pending the maintainer's reply.

Scott K

Message #17 received at 846069@bugs.debian.org (full text, mbox, reply):

From: Ondřej Surý <ondrej@debian.org>

To: Scott Kitterman <debian@kitterman.com>, Thijs Kinkhorst <thijs@debian.org>, 846069@bugs.debian.org

Subject: Re: RM: squirrelmail -- RoQA; RC-buggy; little upstream activity

Date: Mon, 28 Nov 2016 14:45:29 +0100

Hi Thijs, Scott,

according to the upstream, the SVN snapshot is supposed to support PHP
7.0, but it seems to be untested even by upstream (well, that's what I
am reading on the mailing list). One way or another, I agree with Thijs
that random SVN snapshot isn't really suited to be supported for next
stable cycle.

Also I would like you to know that I am trying to properly investigate
all the options before filling RM bugs. So far the most common case is:
"last release in ~2011-2014 - added support for PHP 5.4/5.5" :(.

Cheers,
-- 
Ondřej Surý <ondrej@sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver

On Mon, Nov 28, 2016, at 13:57, Scott Kitterman wrote:
> On Mon, 28 Nov 2016 10:37:55 +0100 =?utf-8?b?T25kxZllaiBTdXLDvQ==?= 
> <ondrej@debian.org> wrote:
> > Package: ftp.debian.org
> > Severity: normal
> > 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> > 
> > Dear ftp-masters,
> > 
> > please remove squirrelmail from unstable, it doesn't have PHP 7.0
> > support and henceforth it's RC-buggy.  I have checked upstream
> > activity and while there's a little activity in upstream SVN, the
> > latest stable release was in 2013.
> > 
> > (A fun fact in my RM storm: The squirrelmail logo was designed by my
> > colleague back in 199x when we deployed squirrelmail for the hosting
> > company I worked for then :).
> 
> See #844240.  Adding moreinfo pending the maintainer's reply.
> 
> Scott K

Message #22 received at 846069@bugs.debian.org (full text, mbox, reply):

From: Scott Kitterman <debian@kitterman.com>

To: Ondřej Surý <ondrej@debian.org>, 846069@bugs.debian.org, Thijs Kinkhorst <thijs@debian.org>

Subject: Re: Bug#846069: RM: squirrelmail -- RoQA; RC-buggy; little upstream activity

Date: Mon, 28 Nov 2016 09:19:08 -0500

On Monday, November 28, 2016 02:45:29 PM Ondřej Surý wrote:
> Hi Thijs, Scott,
> 
> according to the upstream, the SVN snapshot is supposed to support PHP
> 7.0, but it seems to be untested even by upstream (well, that's what I
> am reading on the mailing list). One way or another, I agree with Thijs
> that random SVN snapshot isn't really suited to be supported for next
> stable cycle.
> 
> Also I would like you to know that I am trying to properly investigate
> all the options before filling RM bugs. So far the most common case is:
> "last release in ~2011-2014 - added support for PHP 5.4/5.5" :(.

Certainly.  I'm not at all meaning to call in to question your efforts.  In 
this particular case it was pointed out to me that the maintainer had recently 
expressed a preference for keeping squirrelmail in unstable.  While I don't 
think that's very sustainable, I'd prefer to get agreement where a php5 
rdepend maintainer has expressed a preference.

Scott K

Message #27 received at 846069@bugs.debian.org (full text, mbox, reply):

From: "Thijs Kinkhorst" <thijs@debian.org>

To: "Scott Kitterman" <debian@kitterman.com>

Cc: ondrej@debian.org, 846069@bugs.debian.org

Subject: Re: Bug#846069: RM: squirrelmail -- RoQA; RC-buggy; little upstream activity

Date: Wed, 30 Nov 2016 14:20:37 +0100

On Mon, November 28, 2016 15:19, Scott Kitterman wrote:
> On Monday, November 28, 2016 02:45:29 PM Ondřej Surý wrote:
>> according to the upstream, the SVN snapshot is supposed to support PHP
>> 7.0, but it seems to be untested even by upstream (well, that's what I
>> am reading on the mailing list). One way or another, I agree with Thijs
>> that random SVN snapshot isn't really suited to be supported for next
>> stable cycle.
>>
>> Also I would like you to know that I am trying to properly investigate
>> all the options before filling RM bugs. So far the most common case is:
>> "last release in ~2011-2014 - added support for PHP 5.4/5.5" :(.
>
> Certainly.  I'm not at all meaning to call in to question your efforts.
> In this particular case it was pointed out to me that the maintainer had
> recently expressed a preference for keeping squirrelmail in unstable.
> While I don't think that's very sustainable, I'd prefer to get agreement
> where a php5 rdepend maintainer has expressed a preference.

As the maintainer you have my OK to remove squirrelmail from unstable.


Cheers,
Thijs

Message #34 received at 846069@bugs.debian.org (full text, mbox, reply):

From: Scott Kitterman <debian@kitterman.com>

To: 846069@bugs.debian.org

Subject: Re: RM: squirrelmail -- RoQA; RC-buggy; little upstream activity

Date: Fri, 02 Dec 2016 08:15:30 -0500

On Mon, 28 Nov 2016 10:37:55 +0100 =?utf-8?b?T25kxZllaiBTdXLDvQ==?= 
<ondrej@debian.org> wrote:
> Package: ftp.debian.org
> Severity: normal
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Dear ftp-masters,
> 
> please remove squirrelmail from unstable, it doesn't have PHP 7.0
> support and henceforth it's RC-buggy.  I have checked upstream
> activity and while there's a little activity in upstream SVN, the
> latest stable release was in 2013.
> 
> (A fun fact in my RM storm: The squirrelmail logo was designed by my
> colleague back in 199x when we deployed squirrelmail for the hosting
> company I worked for then :).

There are rdepends that need to be removed first:

Checking reverse dependencies...
# Broken Depends:
avelsieve: avelsieve
squirrelmail-compatibility: squirrelmail-compatibility
squirrelmail-decode: squirrelmail-decode
squirrelmail-locales: squirrelmail-locales
squirrelmail-lockout: squirrelmail-lockout
squirrelmail-logger: squirrelmail-logger
squirrelmail-secure-login: squirrelmail-secure-login
squirrelmail-sent-confirmation: squirrelmail-sent-confirmation
squirrelmail-spam-buttons: squirrelmail-spam-buttons
squirrelmail-viewashtml: squirrelmail-viewashtml

Please remove the moreinfo tag once those are done.

Scott K

Message #43 received at 846069-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 846069-close@bugs.debian.org

Cc: squirrelmail@packages.debian.org, squirrelmail@packages.qa.debian.org

Subject: Bug#846069: Removed package(s) from unstable

Date: Mon, 02 Jan 2017 12:59:51 +0000

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

squirrelmail | 2:1.4.23~svn20120406-2 | source, all

------------------- Reason -------------------
RoQA; RC-buggy; little upstream activity
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 846069@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/846069

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Message #48 received at 846069@bugs.debian.org (full text, mbox, reply):

From: Jan Hauke Rahm <jhr@jhr-online.de>

To: 846069@bugs.debian.org

Subject: Re: Bug#846069: RM: squirrelmail -- RoQA; RC-buggy; little upstream activity

Date: Mon, 2 Jan 2017 16:50:28 +0100

Hi everyone,

On Fri, Dec 02, 2016 at 08:15:30AM -0500, Scott Kitterman wrote:
> On Mon, 28 Nov 2016 10:37:55 +0100 =?utf-8?b?T25kxZllaiBTdXLDvQ==?= 
> <ondrej@debian.org> wrote:
> > Package: ftp.debian.org
> > Severity: normal
> > 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> > 
> > Dear ftp-masters,
> > 
> > please remove squirrelmail from unstable, it doesn't have PHP 7.0
> > support and henceforth it's RC-buggy.  I have checked upstream
> > activity and while there's a little activity in upstream SVN, the
> > latest stable release was in 2013.
> > 
> > (A fun fact in my RM storm: The squirrelmail logo was designed by my
> > colleague back in 199x when we deployed squirrelmail for the hosting
> > company I worked for then :).
> 
> There are rdepends that need to be removed first:
> 
> Checking reverse dependencies...
> # Broken Depends:
> avelsieve: avelsieve
> squirrelmail-compatibility: squirrelmail-compatibility
> squirrelmail-decode: squirrelmail-decode
> squirrelmail-locales: squirrelmail-locales
> squirrelmail-lockout: squirrelmail-lockout
> squirrelmail-logger: squirrelmail-logger
> squirrelmail-secure-login: squirrelmail-secure-login
> squirrelmail-sent-confirmation: squirrelmail-sent-confirmation
> squirrelmail-spam-buttons: squirrelmail-spam-buttons
> squirrelmail-viewashtml: squirrelmail-viewashtml

As I am the maintainer of most those packages, namely
* avelsieve,
* squirrelmail-compatibility,
* squirrelmail-lockout,
* squirrelmail-logger,
* squirrelmail-secure-login,
* squirrelmail-sent-confirmation,
* squirrelmail-spam-buttons,
* squirrelmail-viewashtml,
I would just like to point out that I do also support the removal of
said packages. No effort has to made to reach out, and if any assistance
is needed, please get in touch.

As always, thank you all for your hard work!

Hauke

Send a report that this bug log contains spam.