Bug#380089: possibly inadequate solution

2006-07-31 Thread martin f krafft
also sprach maximilian attems <[EMAIL PROTECTED]> [2006.07.31.1658 +0100]: > anyway the initramfs-tools implementation targets 1.9.0-4sarge1, > so i'm happy on your input for the sarge specific version. difficult to say. creating mdadm.conf (see /usr/share/mdadm/mkconf) and running `mdadm -Asayes

Bug#380089: possibly inadequate solution

2006-07-31 Thread maximilian attems
On Mon, Jul 31, 2006 at 03:13:32PM +0100, martin f krafft wrote: > also sprach maximilian attems <[EMAIL PROTECTED]> [2006.07.31.1439 +0100]: > > mdrun was avoided due too getting random md devices. > > although according to fjp older mdadm seems to have it's share > > of problems: > > http://lists

Bug#380089: possibly inadequate solution

2006-07-31 Thread martin f krafft
also sprach maximilian attems <[EMAIL PROTECTED]> [2006.07.31.1439 +0100]: > mdrun was avoided due too getting random md devices. > although according to fjp older mdadm seems to have it's share > of problems: > http://lists.debian.org/debian-boot/2006/07/msg00244.html These problems should be sol

Bug#380089: possibly inadequate solution

2006-07-31 Thread maximilian attems
On Sun, Jul 30, 2006 at 07:25:20PM -0700, Steve Langasek wrote: > On Sat, Jul 29, 2006 at 05:53:27PM +0100, martin f krafft wrote: > > Anyway, I disagree with the way 0.73 fixes the bug: it replicates > > the functionality provided by mdadm >=2.5-1 into a hack within the > > package. Granted, the h

Bug#380089: possibly inadequate solution

2006-07-30 Thread Steve Langasek
On Sat, Jul 29, 2006 at 05:53:27PM +0100, martin f krafft wrote: > Anyway, I disagree with the way 0.73 fixes the bug: it replicates > the functionality provided by mdadm >=2.5-1 into a hack within the > package. Granted, the hack is only used when mdadm >=2.5-1 is not > installed, but still, it's

Bug#380089: possibly inadequate solution

2006-07-29 Thread martin f krafft
I won't comment on the silliness of the severity tennis played by the maintainer. The bug is critical even according to the release team. Anyway, I disagree with the way 0.73 fixes the bug: it replicates the functionality provided by mdadm >=2.5-1 into a hack within the package. Granted, the hack