Bug#309307: marked as done (kernel-image-2.4.27-sparc in sarge lacks security fixes from kernel-source-2.4.27 2.4.27-9)
Your message dated Thu, 19 May 2005 11:46:44 +0900
with message-id <20050519024642.GK12589@verge.net.au>
and subject line Bug#309307: kernel-image-2.4.27-sparc in sarge lacks security fixes from kernel-source-2.4.27 2.4.27-9
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 16 May 2005 09:26:27 +0000
>From bunk@stusta.de Mon May 16 02:26:27 2005
Return-path: <bunk@stusta.de>
Received: from mailout.stusta.mhn.de [141.84.69.5]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1DXbrn-0002mH-00; Mon, 16 May 2005 02:26:27 -0700
Received: (qmail 19049 invoked from network); 16 May 2005 09:25:55 -0000
Received: from r063144.stusta.swh.mhn.de (10.150.63.144)
by mailout.stusta.mhn.de with SMTP; 16 May 2005 09:25:55 -0000
Received: by r063144.stusta.swh.mhn.de (Postfix, from userid 1000)
id 3FC00BBE3B; Mon, 16 May 2005 11:25:55 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Adrian Bunk <bunk@stusta.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: kernel-image-2.4.27-sparc in sarge lacks security fixes from
kernel-source-2.4.27 2.4.27-9
X-Mailer: reportbug 3.9
Date: Mon, 16 May 2005 11:25:54 +0200
Message-Id: <[🔎] 20050516092555.3FC00BBE3B@r063144.stusta.swh.mhn.de>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: kernel-image-2.4.27-sparc
Version: 2.4.27-2
Severity: critical
Tags: security, sarge
The package in sarge lacks the security fixes from
kernel-source-2.4.27 2.4.27-9 .
---------------------------------------
Received: (at 309307-done) by bugs.debian.org; 19 May 2005 03:12:01 +0000
>From horms@koto.vergenet.net Wed May 18 20:12:01 2005
Return-path: <horms@koto.vergenet.net>
Received: from koto.vergenet.net [210.128.90.7]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DYbS4-0002nf-00; Wed, 18 May 2005 20:12:01 -0700
Received: by koto.vergenet.net (Postfix, from userid 7100)
id 23CBE34038; Thu, 19 May 2005 11:45:03 +0900 (JST)
Date: Thu, 19 May 2005 11:46:44 +0900
From: Horms <horms@debian.org>
To: Adrian Bunk <bunk@stusta.de>, 309307-done@bugs.debian.org
Subject: Re: Bug#309307: kernel-image-2.4.27-sparc in sarge lacks security fixes from kernel-source-2.4.27 2.4.27-9
Message-ID: <20050519024642.GK12589@verge.net.au>
References: <[🔎] 20050516092555.3FC00BBE3B@r063144.stusta.swh.mhn.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 20050516092555.3FC00BBE3B@r063144.stusta.swh.mhn.de>
X-Cluestick: seven
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: 309307-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
On Mon, May 16, 2005 at 11:25:54AM +0200, Adrian Bunk wrote:
> Package: kernel-image-2.4.27-sparc
> Version: 2.4.27-2
> Severity: critical
> Tags: security, sarge
>
>
> The package in sarge lacks the security fixes from
> kernel-source-2.4.27 2.4.27-9 .
Almost all of the kernels in sarge are built against 2.4.27-8.
Actually, I think all of them. This is a known problem. All of the
security bugs are being tracked in the BTS and they have all been marked
as pending, which they are. I don't think there is any need
for this meta-bug, I am closing it accordingly.
--
Horms
Reply to: