* Martin Schulze:
> Imho, it's more useful to upload 2.1.5-8sarge4 and only bump the
> version number to get the new version built for all architectures into
> the archive.
While you are at it, you could also include this patch:
Revision: 8001
http://svn.sourceforge.net/mailman/?rev=80
Hi *,
Martin Schulze <[EMAIL PROTECTED]> writes:
>> Stable release team, please react accordingly; you may for example do
>> a binary sourceless NMU for the architectures that have -8sarge3 the
>> security update so that they all have -8sarge3 the maintainer update.
>
> Imho, it's more useful to
Lionel Elie Mamane wrote:
> let a be an architecture in sarge. Then one of the following holds for
> mailman in sarge r3:
>
> - it is affected by a security problem.
>
> - it has a severity critical bug.
>
> Mailman in sid:
>
> - may or may not suffer of a security problem
>
> A security pr
Hi,
let a be an architecture in sarge. Then one of the following holds for
mailman in sarge r3:
- it is affected by a security problem.
- it has a severity critical bug.
Mailman in sid:
- may or may not suffer of a security problem
A security problem in Mailman in sarge patched in May has
4 matches
Mail list logo
