log not always copied to cwd

[sam tygier]

Binary package hint: rootstock

rootstock writes its log file to LOG="$BUILDDIR/$(basename $0)-$STAMP.log" where BUILDDIR is something like /tmp/tmp.lrtzNBD9a9/

there is a function to copy the log into the cwd at the end of the run, or when the clean up script function is called. however i have experienced several rootstock crashes where the log is not copied across. finding the log file is tedious as due to the random location, and the permissions on the folder.

i think the 'trap' is meant to catch errors and call the cleanup, but if fails to do this for my crashes. eg if i already have 8 loopmounts then the mount will fail, and the script stops.

i suggest that the logging is always done to the current directory, so that the log can always be read easily.

-LOG="$BUILDDIR/$(basename $0)-$STAMP.log"
+LOG="$(basename $0)-$STAMP.log"

and the savelog function can be removed

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: rootstock 0.1.99.3-0ubuntu1 [modified: usr/bin/rootstock]
Uname: Linux 2.6.34-020634rc5-generic x86_64
Architecture: amd64
Date: Tue Apr 27 23:39:15 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.utf8
SourcePackage: rootstock

[dino99 (9d9)]

There is no support for deprecated version having died a long time ago