On Thu, 25 Feb 2010 14:55:40 -0500 (EST), Guillem Jover wrote:
> The fact that the hook returns with 0 does not mean that the maintainer
> script or any of its childs is returning with 0, which is what's
> happening here, try using 'set -x' on the maintainer script itself
> and see what happens. Anyway, I doubt this is a problem in dpkg itself,
> but let's see.
Alas, it appears that the maintainer script is in perl;
and I don't know perl.
If I am in the right place, the maintainer script is
/var/lib/dpkg/info/linux-image-2.6.32-trunk-s390x.postrm. Here is an
excerpt from the area where I think run-parts is being called:
----------
if (-d "/etc/kernel/postrm.d") {
warn "Examining /etc/kernel/postrm.d .\n";
system ("run-parts --verbose --exit-on-error --arg=$version " .
"--arg=$realimageloc$kimage-$version " .
"/etc/kernel/postrm.d") &&
die "Failed to process /etc/kernel/postrm.d";
}
----------
run-parts itself, of course, is binary. Do you see a problem here?
How would I go about tracing a perl script? Is it being executed
directly from /var/lib/dpkg/info? Or is it copied somewhere else
during installation and executed from there?
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
