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

Re: removal catch-22

On Thu, 3 May 2001, Hans wrote:

> >
> >dpkg --force-reinstreq --purge irda-common
> >
> >See dpkg(8) and dpkg --force-help for details. Be warned that this has the
> >potentiol to break your system. Realistically, it's probably ok for this
> >package, especially since you've never actually installed it properly.
> >
> I think you meant dpkg --force-remove-reinstreq --purge irda-common, but
> that returned..
> Removing irda-common ...
> Stopping IrDA Manager: dpkg: error processing irda-common (--purge):
>  subprocess post-removal script returned error exit status 1
> Stopping irmanager...
> Stopping IrDA Manager: dpkg: error while cleaning up:
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  irda-common

When all else fails, do it manually.
You can edit the entry for the package out of /var/lib/dpkg/status,
then use the info in /var/lib/dpkg/info/<package-name>.list to rm the
files in the package.  You'll also want to check for anything done by
the {pre,post}{inst,rm} scripts in the info dir.  Best to keep this
method as a last resort.

> Now I just checked the boot messages and saw this...
> Starting IrDA Manager: sh: /proc/sys/net/irda/devname: No such file or
> directory
> irmanager.
> irmanager is installed, but there isn't an entry in /proc/sys/net for irda.
> Could this be the reason? --Hans

<shrug> It sounds like you don't have IR stuff for your kernel, I
would expect that to result in warnings when booting, not a broken pkg
DB.  Once you get rid of the breakage you should be able to purge
any other IR related packages that were installed, without jumping
through any hoops.

- Bruce

Reply to: