package lvm2 reopen 358373 thanks On Wed, Mar 22, 2006 at 06:24:44PM +0100, Mario 'BitKoenig' Holbe wrote: > On Wed, Mar 22, 2006 at 09:18:13AM -0800, Debian Bug Tracking System wrote: > > From: Bastian Blank <[EMAIL PROTECTED]> > > On Wed, Mar 22, 2006 at 02:37:22PM +0100, Mario 'BitKoenig' Holbe wrote: > > > I'm not sure whether this is intentional or not. > > It is. > Could you then please at least comment a little about my migration > scenario?
Allright, if you don't see a need to comment, I'll just comment myself and reopen the bug. No problem. Refusing to install the package on a system that's not currently running a kernel > 2.6.12 makes it impossible to migrate from lvm1 to lvm2 at all for users running their /usr and /var on lvm1 already: Current 2.6 kernels don't support lvm1, so these users are not able to mount their /usr and /var to be able to install Debian packages at all. Thus, these users are not able to install lvm2 once they've booted a recent 2.6 kernel. Thus, they are not able to install the package *after* booting into 2.6. Since you make it impossible to install the package *before* booting into 2.6, these users have no chance to install the package at all. Thus, they have no chance to migrate at all. That's why simply refusing to install on systems running too old kernels is just not acceptable. If you *need* to refuse to install on systems running kernels <2.6.12 because you would otherwise break things that did work before, you need to provide a different migration path. You could, for example, let this package carry an earlier lvm2 version that supports kernels <2.6.12 and you could provide another (third) package carrying a recent lvm2 version to close the migration gap. best regards Mario -- Programmieren in C++ haelt die grauen Zellen am Leben. Es schaerft alle fuenf Sinne: den Schwachsinn, den Bloedsinn, den Wahnsinn, den Unsinn und den Stumpfsinn. [Holger Veit in doc]
signature.asc
Description: Digital signature