summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess2015-07-30 11:49:45 -0400
committerJoey Hess2015-07-30 11:49:45 -0400
commit0561935815d7b4a863806d65ca2e308f76e2ab53 (patch)
treec88355695be378a391e9af5e9ec037da1b0ba6db
parent4a935e9a5dd5d43ea37d154418e35fa0edbcf8dd (diff)
ugh
-rw-r--r--doc/forum/gitpush_problem/comment_3_419baa6f1738200b1368566a2e136d36._comment22
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/forum/gitpush_problem/comment_3_419baa6f1738200b1368566a2e136d36._comment b/doc/forum/gitpush_problem/comment_3_419baa6f1738200b1368566a2e136d36._comment
new file mode 100644
index 00000000..830ee7b0
--- /dev/null
+++ b/doc/forum/gitpush_problem/comment_3_419baa6f1738200b1368566a2e136d36._comment
@@ -0,0 +1,22 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2015-07-30T15:32:50Z"
+ content="""
+What's happening here is propellor is running: git pull --progress
+--upload-pack command, where command is "./propellor --gitpush".
+
+Apparently git's --upload-pack option parsing has changed in a way that
+breaks this.
+
+I think this is a straight-up git bug. I have reported the bug to the
+git mailing list.
+
+May have to work around the bug by just passing "./propellor" to
+--upload-pack, and using environment variables to tell it what to do.
+
+Erm.. AFAIKS, git pull is no longer running --upload-pack specified
+command at all. So it seems git has completely defeated how propellor --spin
+sends a git push over its ssh channel. I don't have any prospect of a fix
+right now.
+"""]]