Bug#358397: initramfs-tools initrd.img update

2006-08-13 Thread Steve Langasek
Hi maks, On Fri, Aug 04, 2006 at 04:18:14PM +0200, maximilian attems wrote: > rechecking the issues that were reported on #358397 and #362064 > 6) debconf note > a preinst warning of the update. See Manoj's reply for concerns about note vs. question here. I also don't see any reason why the no

Bug#358397: initramfs-tools initrd.img update

2006-08-07 Thread Manoj Srivastava
The following message is a courtesy copy of an article that has been posted to gmane.linux.debian.devel.kernel as well. On Sun, 6 Aug 2006 02:16:59 +0200, Adeodato Simó <[EMAIL PROTECTED]> said: > * Manoj Srivastava [Sat, 05 Aug 2006 00:25:05 -0500]: >> > 6) debconf note >> > a preinst warning o

Bug#358397: initramfs-tools initrd.img update

2006-08-07 Thread Adeodato Simó
* Manoj Srivastava [Mon, 07 Aug 2006 13:40:09 -0500]: > I am assuming you are not trolling, but merely do not know the > behaviour of the image preinst script. I know the behavior I observe in my systems. I have not read the code. > The difference is that first, if kernel image

Bug#358397: initramfs-tools initrd.img update

2006-08-05 Thread Adeodato Simó
* Manoj Srivastava [Sat, 05 Aug 2006 00:25:05 -0500]: > > 6) debconf note > > a preinst warning of the update. > Not a note. A question asked, and action taken based on the > answer. You mean like kernel-package's "Heya, I'm unpacking the a new version of the same kernel, so you bette

Bug#358397: initramfs-tools initrd.img update

2006-08-04 Thread Manoj Srivastava
The following message is a courtesy copy of an article that has been posted to gmane.linux.debian.devel.kernel as well. On Fri, 4 Aug 2006 16:18:14 +0200, maximilian attems <[EMAIL PROTECTED]> said: > hello Manoj and vorlon! rechecking the issues that were reported on > #358397 and #362064 > 1

Bug#358397: initramfs-tools initrd.img update

2006-08-04 Thread maximilian attems
hello Manoj and vorlon! rechecking the issues that were reported on #358397 and #362064 1) fails to install on read-only /boot this is correct and not yet checked, boot is assumed rw. we currently fail to check that, but non standard setup. 2) overwriting yaird generated image only happened in s