Comment 16 for bug 244670

Revision history for this message
Kry (cafedetal) wrote : Re: [hardy] Request of update of aMule to 2.2.1 final release

This is the thing: the hint I gave Festor about the upstream release is unrelated to regression testing or similar. It is actually a new security problem that needs to be patched - upstream is waiting for a concurrent eMule release (or their beta) before releasing a new version. Releasing 2.2.1, or keeping the current one would keep the same vulnerability that would have to be patched.

It can be easily applied as a patch over this release instead if that's what you prefer - it's been out for a month with no important reports, and I can probably package a couple of important patches (well tested ones) from this last month. But I think this duplicated effort can easily be avoided by waiting till our actual release.

You tell me what you prefer, really.