On Thursday 02 August 2007, Salvatore Bonaccorso wrote:
> I can't help you to solve the problem, to say it first. But I had the
> exactly the same Problem with a self-compiled 2.6.14 kernel (from the
> kernel-source-2.6.14 package) and packaged with make-kpkg.
Yes I compile with make-kpkg.
> Trying
Hello
On Tue, Jul 31, 2007 at 11:15:50PM +0300, Alexandar Angelov wrote:
> On Tuesday 31 July 2007, Karl E. Jorgensen wrote:
> > On Tue, Jul 31, 2007 at 01:15:19AM +0300, Sasho Angelov wrote:
> > > When I try to purge old linux image:
> > >
> > > sudo dpkg --purge --force-all linux-image-2.6.14-2-
Sasho Angelov wrote:
> When I purge other linux-images everything is fine.
Hmm... It is hard to debug remotely.
If you are at the end of the possibilities then I would simply disable
the prerm and postrm scripts entirely. This is a serious "force"
action but if you have exhausted your other opt
On 8/1/07, Bob Proulx <[EMAIL PROTECTED]> wrote:
>
>
> Does running update-grub by itself complete? Or hang?
>
>
> update-grub complete successfully
When I purge other linux-images everything is fine.
--
Alexandar Angelov
Alexandar Angelov wrote:
> Bob Proulx wrote:
> > After fixing and running update-grub inspect the file. If update-grub
> > runs without hanging then you should be able to purge the package.
Does running update-grub by itself complete? Or hang?
> > If all else fails and a package simply will not
On Wednesday 01 August 2007, Bob Proulx wrote:
/boot/grub/menu.lst is not corrupted
> After fixing and running update-grub inspect the file. If update-grub
> runs without hanging then you should be able to purge the package.
>
> If all else fails and a package simply will not pass the prerm or
>
Sasho Angelov wrote:
> Updating /boot/grub/menu.lst ... done
> And stop here. Only I can do is to press Ctrl+C
That is running update-grub. You should be able to run that command
manually.
sudo update-grub
If that hangs (hopefully it will) then you can debug from that point.
It is a shel
On Tuesday 31 July 2007, Karl E. Jorgensen wrote:
> On Tue, Jul 31, 2007 at 01:15:19AM +0300, Sasho Angelov wrote:
> > When I try to purge old linux image:
> >
> > sudo dpkg --purge --force-all linux-image-2.6.14-2-k7
>
> Why --force-all ?
>
Without --force-all the result is the same.
>
> Which deb
On Tue, Jul 31, 2007 at 01:15:19AM +0300, Sasho Angelov wrote:
> When I try to purge old linux image:
>
> sudo dpkg --purge --force-all linux-image-2.6.14-2-k7
Why --force-all ?
> (Reading database ... 259033 files and directories currently installed.)
> Removing linux-image-2.6.14-2-k7 ...
> Pu
On Tue, Jul 31, 2007 at 01:15:19AM +0300, Sasho Angelov wrote:
> When I try to purge old linux image:
>
> sudo dpkg --purge --force-all linux-image-2.6.14-2-k7
Why do you need to force things? This may be a clue.
What package manager do you use and why don't you use it to remove this?
[snip]
When I try to purge old linux image:
sudo dpkg --purge --force-all linux-image-2.6.14-2-k7
(Reading database ... 259033 files and directories currently installed.)
Removing linux-image-2.6.14-2-k7 ...
Purging configuration files for linux-image-2.6.14-2-k7 ...
Searching for GRUB installation direc
11 matches
Mail list logo
