Your message dated Mon, 24 Jan 2005 21:36:46 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bugs not fixed from 2.6.8
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; 23 Jan 2005 16:33:35 +0000
>From [EMAIL PROTECTED] Sun Jan 23 08:33:35 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 80-218-227-31.dclient.hispeed.ch (hal9000) [80.218.227.31]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Cskg7-0002Jz-00; Sun, 23 Jan 2005 08:33:31 -0800
Received: from [192.168.42.12] (aragon [192.168.42.12])
by hal9000 (Postfix) with ESMTP id 4830436C0D0
for <[EMAIL PROTECTED]>; Sun, 23 Jan 2005 17:33:21 +0100 (CET)
From: Peter Walser <[EMAIL PROTECTED]>
Date: Sun, 23 Jan 2005 17:33:24 +0100
User-Agent: KMail/1.7.2
MIME-Version: 1.0
Content-Disposition: inline
To: [EMAIL PROTECTED]
Subject: Bugs not fixed from 2.6.8
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
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=-4.3 required=4.0 tests=BAYES_00,FORGED_YAHOO_RCVD,
HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: kernel-image-2.6.8-2-686
Version: 2.6.8-12
Severity: grave
hi
Has someone looked at the bugs in kernel-image-2.6.8-1-386 and
kernel-image-2.6.8-1-686?
<http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=kernel-image-2.6.8-1-386>
Grave functionality bugs - outstanding (1 bug)
Important bugs - outstanding (5 bugs)
Normal bugs - outstanding (9 bugs)
Wishlist items - outstanding (1 bug)
Grave functionality bugs - resolved (2 bugs)
<http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=kernel-image-2.6.8-1-686>
Critical bugs - outstanding (1 bug)
Important bugs - outstanding (8 bugs)
Normal bugs - outstanding (21 bugs)
Minor bugs - outstanding (2 bugs)
Wishlist items - outstanding (1 bug)
Normal bugs - resolved (1 bug)
At least not all bugs are tested, if they are still present and the
people are not informed to test with the newer version
kernel-image-2.6.8-2-686.
My bug #282800 is still not fixed and you shouldn't go out with this
2.6.8. In Kernel 2.6.10 this bug is fixed.
Peter
---------------------------------------
Received: (at 291846-done) by bugs.debian.org; 25 Jan 2005 05:36:49 +0000
>From [EMAIL PROTECTED] Mon Jan 24 21:36:49 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain)
[66.93.39.86]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CtJNg-0006AC-00; Mon, 24 Jan 2005 21:36:49 -0800
Received: by localhost.localdomain (Postfix, from userid 1000)
id 994E311AF3C; Mon, 24 Jan 2005 21:36:46 -0800 (PST)
Date: Mon, 24 Jan 2005 21:36:46 -0800
From: Steve Langasek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bugs not fixed from 2.6.8
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="/NkBOFFp2J2Af1nK"
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
--/NkBOFFp2J2Af1nK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Peter,
These bugs have not been lost; there's really no reason to open new release
critical bugs just to point at release critical bugs that are already open.
If anything, the bugs open against the -1 kernel images probably need to be
reassigned to the -2 kernel images, but it should be confirmed that these
bugs are still present in the new images before doing so.
The release-critical bugs you've pointed to will be addressed before the
sarge release.
--=20
Steve Langasek
postmodern programmer
--/NkBOFFp2J2Af1nK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFB9drsKN6ufymYLloRApYmAKDBNpL+ZZLuHjt5MDg7fECV06todgCgj64C
iqXTWkGVrzE4fqarTVusiNo=
=869X
-----END PGP SIGNATURE-----
--/NkBOFFp2J2Af1nK--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
