Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 12716] Sorcery doesn't register if a basesystem cast has been aborted when doing sorcery update

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 12716] Sorcery doesn't register if a basesystem cast has been aborted when doing sorcery update
  • Date: 18 Jun 2006 13:51:57 -0000

http://bugs.sourcemage.org/show_bug.cgi?id=12716





------- Additional Comments From acedit AT armory.com 2006-06-18 08:51 -------
What command did you run?

Theres really not much code between the interrupt handler and cast calling
exit.

trap gets registered and main code starts:
trap int_trap INT
main "$@"

int_trap function, which includes the message you saw and has an exit 1 at the
end. The only real code here is cast_cleanup since you're not in screen mode
presumably.

function int_trap()
{
message "${PROBLEM_COLOR}SIGINT${DEFAULT_COLOR}"
message "Cleaning up as well as I can..."
cast_cleanup
if [[ $SCREEN_NAME ]] ; then
message -n "Press a key to exit screen."
read -n 1
screen_quit "$SCREEN_NAME"
fi
exit 1
}

function cast_cleanup() {
$STD_DEBUG
cleanup_tmp_dir $TMP_DIR
}

cleanup_tmp_dir ()
{
local TMP_DIR=$1;
if [ ${TMP_DIR:0:13} == "/tmp/sorcery/" ]; then
rm -rf $TMP_DIR;
else
message "Cowardly refusing to remove $TMP_DIR, this may be a bug,"
"please alert the sorcery team.";
fi
}

Thats literally all the code there is. To do a sorcery update from inside cast
is pretty weird, the function that does that is only called from the sorcery
script.

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page