Your message dated Sun, 18 Mar 2007 22:01:21 +0100 with message-id <20070318210121.GA27761@javifsp.no-ip.org> and subject line This is already covered in the latest version of the Release Notes 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)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Upgrade path for udev needs documenting
- From: Frans Pop <aragorn@tiscali.nl>
- Date: Mon, 29 Aug 2005 14:42:22 +0200
- Message-id: <200508291442.22885.aragorn@tiscali.nl>
Package: release-notes Severity: important As it looks now, the Sarge to Etch upgrade for udev will not be trivial and will need documenting in the release notes. Etch's udev does not support 2.6.8 kernels and Sarge's udev will not work properly with 2.6.12 kernels. The current upgrade path looks to be that a kernel upgrade has to be done before udev can be upgraded.Attachment: pgp_uRO_IOpD4.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: 383982-done@bugs.debian.org
- Subject: This is already covered in the latest version of the Release Notes
- From: Javier Fernández-Sanguino Peña <jfs@computer.org>
- Date: Sun, 18 Mar 2007 22:01:21 +0100
- Message-id: <20070318210121.GA27761@javifsp.no-ip.org>
- Mail-followup-to: 383982-done@bugs.debian.org
The Release Notes already covers the name change for Linux kernel packages, please see http://www.debian.org/releases/etch/i386/release-notes/ch-upgrading.en.html#s-newkernel (this information used to be in the Debian Kernel's release notes for etch and was merge some time ago) If you consider something is still missing there please reopen the bug and provide more information. Thanks JavierAttachment: signature.asc
Description: Digital signature
--- End Message ---