Le sam 09/10/2004 à 16:29, Wouter Verhelst a écrit : > On Sat, Oct 09, 2004 at 12:48:23PM +0200, Jérôme Warnier wrote: > > I got this strange behaviour on Sid today while upgrading > > kernel-image-2.6.8-1-686. Notice on the log that I answered "n" to "Do > > you want to stop now? [Y/n]", and it aborted just like if I answered > > "y". > > > > The only thing noticeable is that I took a long time (a few minutes) to > > answer. I suspect there should be no timeout in this case. > > > > I just wanted to let you know, just in case. > > > > > > > > Preparing to replace kernel-headers-2.6.8-1 2.6.8-3 (using > > .../kernel-headers-2.6.8-1_2.6.8-4_i386.deb) ... > > Unpacking replacement kernel-headers-2.6.8-1 ... > > Preparing to replace kernel-headers-2.6.8-1-686 2.6.8-3 (using > ^ > Notice the extra space here. It appears you inadvertently hit the space > bar while you were doing something else. As a result, you had that space > in your input buffer, so when you hit enter, it was the space, rather > than the 'n', which was processed. As this script interprets everything > which is not 'n' as the default value, it bailed out. You're perfectly right. This is just a problem of the input checking being really too weak. If you are all aware of it, I don't mind.
-- Jérôme Warnier Consultant BeezNest http://beeznest.net
