[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#346028: linux-2.6: Hangs while attempting to purge



On Thu, Jan 05, 2006 at 01:19:17AM +0100, Cesare Leonardi wrote:
> Sven Luther wrote:
> >It would be great if you could confirm the exact version of those two
> >packages, and could provide us some log of what is happening, as this bug
> >report doesn't seem to be very informative.
> 
> For me, i have provided information in bug #344767, as i explained in 
> the previous message: versions, logs, ecc.

Ah, looking at this one now.

> >This issue should have been fixed in linux-image-2.6.15-1-686 though, so we
> >really need to find out what did go wrong.
> 
> I haven't tested 2.6.15 because it isn't available in my mirror yet. But 
> the Nathanael posts tell us that the problem is still present in the 
> latest kernel.

But it should not, which is why it is important to investigate. 2.6.14-2 is no
more in the archive as of today, and thus no longer relevant.

For information, i had this problem on powerpc, where the debconfified
mkvmlinuz package used debconf script in the /etc/kernel way described below,
but we fixed it last week, and the new 2.6.15-1 kernel build depend on at
least the 10.028 or 10.029 kernel-package version with this fixed.

So, either it is a new problem, or somehow the version Nathanael has built was
done so using an older kernel-package which was buggy.

> As soon as it will be available on the mirror i use, i'll test 2.6.15.

Thanks.

> >Also, could you please give us the output of ls -lR /etc/kernel, and 
> >append it
> >to the bug report ?
> 
> Do you mean this?
> $ ls -lR /etc/kernel-*
> -rw-r--r-- 1 root root  179 2005-09-11 20:55 /etc/kernel-img.conf
> -rw-r--r-- 1 root root 1006 2005-11-08 00:35 /etc/kernel-pkg.conf

No, the kernel-packahe generated postinst and co script have support for
script hooks, found under /etc/kernel/postinst.d/ and co, i want to know what
exactly you have there, because it is probable that some random third party
hook (like grub-update call maybe) causes this problem.

Friendly,

Sven Luther




Reply to: