On Thu, 25 Feb 2010, Stephen Powell wrote:
> If I am in the right place, the maintainer script is
> /var/lib/dpkg/info/linux-image-2.6.32-trunk-s390x.postrm.
Yes.
> 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?
No, what leads you to believe that this is the part that is failing ?
The error is probably later in the script.
> 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?
It's executed directly from there. You can always use the poor man's
tracer, adding print calls in it:
print STDERR "After run-parts, I'm still running\n";
Cheers,
--
Raphaël Hertzog
Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/
My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
