Git-tag's over-aggressive pipework fails badly on fresh Ubuntu, over NFS.

From: Samium Gromoff <_deepfire@feelingofgreen.ru>
Date: Sep 25, 2007, 22:34 UTC
Message-ID: <87hclifk7i.wl@betelheise.deep.net>

Hello folks,

Without the following applied, git-tag -s gets zeroes into TAG_TMP in place of the .asc sig, resulting in an unsigned commit.

My repository is located on a NFS share, and I didn't check with NFS factored out, so it might be more extensive.

I'm not sure what's the policy -- "go and fix Ubuntu, your filesystem and your kernel", or "let's go the safe way", so there it is.

--- a/git-tag   2007-09-07 22:12:11.000000000 +0400
+++ b/git-tag   2007-09-26 02:19:42.000000000 +0400
@@ -143,7 +143,8 @@
     rm -f "$GIT_DIR"/TAG_TMP.asc "$GIT_DIR"/TAG_FINALMSG
     if [ "$signed" ]; then
        gpg -bsa -u "$username" "$GIT_DIR"/TAG_TMP &&
-       cat "$GIT_DIR"/TAG_TMP.asc >>"$GIT_DIR"/TAG_TMP ||
+       cat "$GIT_DIR"/TAG_TMP "$GIT_DIR"/TAG_TMP.asc > "$GIT_DIR"/TAG_TMP_RELAY &&
+       mv "$GIT_DIR"/TAG_TMP_RELAY "$GIT_DIR"/TAG_TMP ||
        die "failed to sign the tag with GPG."
     fi
     object=$(git-mktag < "$GIT_DIR"/TAG_TMP)

Git is 1.5.2.5-2build1/Gutsy.

regards, Samium Gromoff