Ou, Nov 19 2009, Alan BRASLAU wrote:

> kernel-package is now severly broken!  Building and installing a[nd]
> new kernel image now results in *two* identical vmlinuz nodes with
> *identical* names under /boot.  grub then rightly finds both images,
> *neither one which is bootable*.

        I can't reproduce this with 12.029.


> The bug report should therefore be *reopened* and marked *critical*.
>
> Not only did the new handling of XEN schemes "caused no end of
> confusion", it was broken and is still the source of system damage.
> This is rather severe as a less experienced user trying to install a
> custom tailored kernel can easily end up with an unbootable
> installation.

        Well, this is _unstable_, after all. But thanks for testing,
 things should be better now.

        manoj
-- 
Each person has the right to take the subway.  -- Carlos Eduardo Novaes
Manoj Srivastava <sriva...@acm.org> <http://www.golden-gryphon.com/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to