On Thu, Sep 07, 2006 at 08:02:06PM +0200, Florian Weimer wrote:
* 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:
On Thu, Sep 07, 2006 at 02:44:21AM -0700, Steve Langasek wrote:
On Thu, Sep 07, 2006 at 11:21:35AM +0200, Lionel Elie Mamane wrote:
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
On Fri, Sep 08, 2006 at 05:03:06PM +0200, Lionel Elie Mamane wrote:
On Thu, Sep 07, 2006 at 08:02:06PM +0200, Florian Weimer wrote:
* 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
On Fri, Sep 08, 2006 at 05:05:48PM +0200, Lionel Elie Mamane wrote:
On Thu, Sep 07, 2006 at 02:44:21AM -0700, Steve Langasek wrote:
On Thu, Sep 07, 2006 at 11:21:35AM +0200, Lionel Elie Mamane wrote:
Stable release team, please react accordingly; you may for example
do a binary sourceless NMU
On Wed, Sep 06, 2006 at 12:03:34PM +0200, Lionel Elie Mamane wrote:
There seems to have been a screw-up in handling of mailman security
and stable updates: There are two different mailman packages in Debian
with version number 2.1.5-8sarge3.
-8sarge3 maintainer update (that got frozen
On Thu, Sep 07, 2006 at 11:21:35AM +0200, Lionel Elie Mamane wrote:
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.
I have now
* 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
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
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 problem in
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 upload
10 matches
Mail list logo
