Re: [PATCH] receive-pack: allow deletion of corrupt refs

Previous thread: Re: What's cooking in git.git (topics) by Junio C Hamano on Wednesday, November 28, 2007 - 6:00 pm. (5 messages)

Next thread: To push into a non-bare repository, or not to push into it... by Johannes Schindelin on Wednesday, November 28, 2007 - 6:33 pm. (1 message)
From: Johannes Schindelin
Date: Wednesday, November 28, 2007 - 6:02 pm

Occasionally, in some setups (*cough* forks on repo.or.cz *cough*) some
refs go stale, e.g. when the forkee rebased and lost some objects needed
by the fork.  The quick & dirty way to deal with those refs is to delete
them and push them again.

However, git-push first would first fetch the current commit name for the
ref, would receive a null sha1 since the ref does not point to a valid
object, then tell receive-pack that it should delete the ref with this
commit name.  delete_ref() would be subsequently be called, and check that
resolve_ref() (which does _not_ check for validity of the object) returns
the same commit name.  Which would fail.

The proper fix is to avoid corrupting repositories, but in the meantime
this is a good fix in any case.

Incidentally, some instances of "cd .." in the test cases were fixed, so
that subsequent test cases run in t/trash/ irrespective of the outcome of
the previous test cases.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---

	I was bitten one time too many by a rebased git/mingw.git/.

	Will work on the "proper fix" I hinted at.

 receive-pack.c        |    4 ++++
 t/t5516-fetch-push.sh |   41 ++++++++++++++++++++++++++---------------
 2 files changed, 30 insertions(+), 15 deletions(-)

diff --git a/receive-pack.c b/receive-pack.c
index ed44b89..fba4cf8 100644
--- a/receive-pack.c
+++ b/receive-pack.c
@@ -200,6 +200,10 @@ static const char *update(struct command *cmd)
 	}
 
 	if (is_null_sha1(new_sha1)) {
+		if (!parse_object(old_sha1)) {
+			warning ("Allowing deletion of corrupt ref.");
+			old_sha1 = NULL;
+		}
 		if (delete_ref(name, old_sha1)) {
 			error("failed to delete %s", name);
 			return "failed to delete";
diff --git a/t/t5516-fetch-push.sh b/t/t5516-fetch-push.sh
index fd5f284..9d2dc33 100755
--- a/t/t5516-fetch-push.sh
+++ b/t/t5516-fetch-push.sh
@@ -274,9 +274,8 @@ test_expect_success 'push with HEAD nonexisting at remote' '
 test_expect_success 'push with dry-run' '
 
 	mk_test ...
From: Johannes Schindelin
Date: Wednesday, November 28, 2007 - 6:04 pm

Hi,


Just to clarify: I was quite surprised that my test case did not succeed, 
and eventually found out that $(pwd) was t/trash/child/child after the 
last test.

Ciao,
Dscho

-

From: Petr Baudis
Date: Wednesday, November 28, 2007 - 8:55 pm

Hi,


  repo.or.cz now has this patch. I'm also repacking the kernel
repository which is in a pretty awful state, I'm hoping that will fix
some of the heavy performance problems repo.or.cz is hitting currently.

-- 
				Petr "Pasky" Baudis
We don't know who it was that discovered water, but we're pretty sure
that it wasn't a fish.		-- Marshall McLuhan
-

Previous thread: Re: What's cooking in git.git (topics) by Junio C Hamano on Wednesday, November 28, 2007 - 6:00 pm. (5 messages)

Next thread: To push into a non-bare repository, or not to push into it... by Johannes Schindelin on Wednesday, November 28, 2007 - 6:33 pm. (1 message)