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

Re: dpkg error help



Dave Wiard <dave@lister.acm.wwu.edu> writes:

> could somebody clue me in on this one?  i've got an almost fully slink
> install with a couple (maybe 5) potato packages..
> 
> dpkg (subprocess): unable to execute old pre-removal script: No such file or directory
> dpkg: warning - old pre-removal script returned error exit status 2
> dpkg - trying script from the new package instead ...
> dpkg: error processing libncurses4_4.2-3.deb (--install):
>  there is no script in the new version of the package - giving up
> dpkg (subprocess): unable to execute post-installation script: No such file or directory
> dpkg: error while cleaning up:
>  subprocess post-installation script returned error exit status 2
> Errors were encountered while processing:
>  libncurses4_4.2-3.deb
> 
> i know my X-Windows is hosed until i can get this lib installed (any
> version >= 4_4.2-3)..

I don´t know whats wrong, but try to use the files found on my system
(libncurses4 4.2-3.4):

------------------- /var/lib/dpkg/libncurses4.prerm ----------------------
#!/bin/sh -e
# Automatically added by dh_installdocs
if [ \( "$1" = "upgrade" -o "$1" = "remove" \) -a -L /usr/doc/libncurses4 ]; then
	rm -f /usr/doc/libncurses4
fi
# End automatically added section
---------------------------------------------------------------------------

------------------- /var/lib/dpkg/libncurses4.postins ---------------------
#!/bin/sh

# Make sure errors report (since we try to weed out potential spurious ones)
set -e

# Make sure ld knows about the new library
ldconfig
---------------------------------------------------------------------------

After replacing/ceating those files, reinstall the package (you
probably have to use dpkg -i for that).

Could it be that you filesystem is full? I had that problem when
updating libc, since it has grown dramatically. Could be that there
isn´t enough space for the new scripts or so.

May the Source be with you.
			Goswin


Reply to: