Manoj Srivastava <[EMAIL PROTECTED]> writes: > Unfortunately, there is not a whole lot of detail to go on > here. As for the clean problem, do you see ./stamp-building? If so, > that is the culprit; normally, make-kpkg creates stamp-building while > calling dpkg-buildpackage (which in turn calls clean, and we do not > want dpkg-buildpackage to suddenly nuke ./debian). The stamp is > supposed to be removed immediately afterwards -- if someting failed, > well ... > > I'll add stuff to make it reover better. > > As for the postinst problem, Hmm. I am uploading a new > kernel-package that is slightly more verbose about when it calls > fork/exec, to make diagnosing issues like this easier. Please try > with 10.014, to be uploaded soon.
sorry, i even tried running dpkg in debug mode and i didn't get any more information and looking at the code i wasn't able to figure out what went wrong. it happens somewhere after checking for the symbolic links to kernel image. using kernel-package version 1.011 i created an image that installed on a system with grub. on the system i got the postinst failure i use lilo and i didn't get asked the usual questions: if i want to create a backup disk, if i want to run lilo and so on. maybe that's where the problem is. if you know of a way of tracing a perl script (equivalent to sh -x) i can also try to do that. thanks. --alex-- -- | I believe the moment is at hand when, by a paranoiac and active | | advance of the mind, it will be possible (simultaneously with | | automatism and other passive states) to systematize confusion | | and thus to help to discredit completely the world of reality. | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
