Processed: severity of 563947 is important

To: Ben Hutchings <ben@decadent.org.uk>
Cc: Debian Kernel Team <debian-kernel@lists.debian.org> (linux-image-2.6.30-2-686 for {563947})
Subject: Processed: severity of 563947 is important
From: owner@bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 06 Jan 2010 22:21:12 +0000
Message-id: <[🔎] handler.s.C.12628162201173.transcript@bugs.debian.org>
In-reply-to: <1262816215-378-bts-ben@decadent.org.uk>
References: <1262816215-378-bts-ben@decadent.org.uk>

Processing commands for control@bugs.debian.org:

> severity 563947 important
Bug #563947 [linux-image-2.6.30-2-686] linux-image-2.6.30-2-686 doesn't start software raid on boot
Severity set to 'important' from 'critical'

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Reply to:

Prev by Date: Bug#562525: linux-2.6: [s390] Etch proposed-updates kernel boot failure
Next by Date: Bug#562025: marked as done (linux-image-2.6.32-trunk-amd64: After boot, the current virtual console is not TTY1)
Previous by thread: Bug#520090: marked as done (linux-image-2.6.26-1-686: software clock runs much too fast)
Next by thread: Bug#562025: marked as done (linux-image-2.6.32-trunk-amd64: After boot, the current virtual console is not TTY1)
Index(es):
- Date
- Thread