Michael Homer wrote: > On Wed, Jul 28, 2010 at 6:52 AM, MJ Ray <m...@phonecoop.coop> wrote: > > How do I find out what the failure is? > > > > The pre_install command seems to succeed when run in bash manually. > Except that it doesn't really, it just looks like it - `[ test ] && > Die` always fails, either because the test is true and it dies or the > test is false and the chain short-circuits. I'm not sure how that got > in there, but you can fix it just by changing the pre_install to use > != and || instead.
D'oh! I've done that and it works. I've now some problem with the install step trying to create /var/lib/postfix but that's a more usual fail type which I should be able to fix when I get time. > I'm not sure how we can give better failure message there. It really > is just that pre_install failed. Perhaps dump out the hook script, but > even that is just going to be a bunch of inclusions and variable > settings finishing with "pre_install". These bits are a pain to debug > so I would welcome any suggestions for making them more communicative. Returning the actual exit code ($? I think) would be helpful, as would dumping out what Compile thinks are relevant scripts. Maybe some way to leave the pre_install.sh temporary file around, for ease of testing? But maybe this exists and I've missed it. Thanks, -- MJ Ray (slef) Webmaster and developer for hire at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
