[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#726262: Accepted m2crypto 0.21.1-4 (source amd64) into unstable



Le Sat, Sep 12, 2015 at 10:20:25AM +0000, Emanuele Rocca a écrit :
> Urgency: low
> Maintainer: Debian QA Group <packages@qa.debian.org>
> Changed-By: Emanuele Rocca <ema@debian.org>
> Description:
>  python-m2crypto - Crypto and SSL toolkit for Python
> Changes:
>  m2crypto (0.21.1-4) unstable; urgency=low
>  .
>    * QA upload.
>    * Maintainer field set to QA Group.
>    * Bump Standards-Version to 3.9.6.
>    * Remove Uploaders field.
>    * Fix debian/watch by using pypi.debian.net.
>    * Do not start synopsis with an article.

Hi Emanuele,

thank you for formally relieving me from the maintenance of m2crypto.
In #726262, where I ophaned it, a few people offered their help, but did not
follow up.  Have you considered re-contacting them or the Debian Python
Applications or Modules Teams, that maintain some packages depending on
m2crypto ? 

The reason I ask is that, as the name indicates, m2crypto might be involved in
security issues anytime, and it would obviously better if we found a person or
a team knowledgeable in at least python or cryptography, to increase Debian's
chances of reacting quickly.  One painful alternative is to remove m2crypto,
and therefore its dependency chain, given the concerns of not being able to
deal with potential problems in the future.

Anyway, thanks for your intervention, and have a nice day,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


Reply to: