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

[Pkg-security-team] Maintenance of aircrack-ng

On Fri, Sep 09, 2016 at 04:08:38PM +0000, Gianfranco Costamagna wrote:
> Hi Mia Team,

[ please teach your MUA to wrap lines at a decent width, unless you have
to reason to do so, the formatting of huge lines is annoying to see ]

> >Considering that the last upload to aircrack-ng made by you was 2 years ago, i'm sending this email to see if you're still interested in maintaining aircrack-ng, >the package is very outdated and it lacks various changes on its packaging.
> >I'm willing to take on the maintenance of the package if you're not interested anymore, i would maintain it under the pkg-security team, probably with help from >another uploader, providing it with all the changes and updates needed.
> >I already did some changes on the packaging and uploaded them to mentors, i had to contact upstream to fix some things and understand others, if you confirm that i >can take over the packaging or doesn't respond on a reasonable time, i'm planning to fix everything missing (the one present on mentors is not complete yet) and >upload it.
> >Thanks for you consideration and effort on the previous uploads of aircrack-ng.
> >Please add pkg-security as a cc when answering this email.
> considering the importance of aircrack-ng for the security group, I would like to know if the maintainer is MIA or not.

udd=> select source, version, date, nmu from upload_history where changed_by_email='clopez at igalia.com' or fingerprint='B5D2B50BC48EC7F1EE90D9AB965089CE6B95F882';
    source    |      version       |          date          | nmu 
 aircrack-ng  | 1:1.1-2            | 2012-06-27 17:02:09+00 | f
 aircrack-ng  | 1:1.1-3            | 2012-06-27 17:02:26+00 | f
 aircrack-ng  | 1:1.1-4            | 2012-07-27 22:47:11+00 | f
 aircrack-ng  | 1:1.1-5            | 2012-07-28 18:32:10+00 | f
 aircrack-ng  | 1:1.1-6            | 2013-06-11 01:03:05+00 | f
 util-vserver | 0.30.216-pre3038-1 | 2014-01-19 16:05:28+00 | f
 util-vserver | 0.30.216-pre3054-1 | 2014-03-18 15:21:19+00 | f
 aircrack-ng  | 1:1.2-0~beta3-1    | 2014-06-08 01:03:46+00 | f
 aircrack-ng  | 1:1.2-0~beta3-2    | 2014-11-12 03:34:28+00 | f
 aircrack-ng  | 1:1.2-0~beta3-3    | 2014-11-12 17:48:42+00 | f
 aircrack-ng  | 1:1.2-0~beta3-4    | 2014-11-28 10:48:59+00 | f
 util-vserver | 0.30.216-pre3120-1 | 2015-09-02 18:05:15+00 | f
 zfs-linux    |          | 2016-08-17 05:48:50+00 | f
(13 rows)

So no, Carlos can't be considered MIA, the last upload from him is from
not even a month ago, and mails from him in the BTS can be find for this

> a package takeover might sound hostile and not happening in the near future but the package really needs care :)
> (and the freeze is approaching)

I don't see any RC bug against aircrack-ng, but I trust you if you say
that the package needs care.
I suppose that that non-MIAness of the maintainer doesn't really block
you from following the usual NMU procedure to fix whatever bug the
current package has, as long as the usual proceder delined in devref is

if you have lost interest in the package in question *please*, *please*
orphan it!
Having package with the maintainer set to somebody that can't (due to
time issues) or don't want to maintain it is only a source of annoiance
for 1) your user because they receive a package of a lower quality of
what they deserve 2) your fellow developers because they have to go
through huge hops to get fixes in.

Mattia (for the MIA team)

                        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  `-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-security-team/attachments/20160909/9c299218/attachment.sig>

Reply to: