From: Horst Schirmeier <horst@schirmeier.com>
To: git@vger.kernel.org
Subject: regression: git push in non-shared repo stalls (v2.11.0+)
Date: Tue, 7 Mar 2017 12:03:28 +0100 [thread overview]
Message-ID: <20170307110328.GE7566@quickstop.soohrt.org> (raw)
Hi,
I observe a regression that seems to have been introduced between
v2.10.0 and v2.11.0. When I try to push into a repository on the local
filesystem that belongs to another user and has not explicitly been
prepared for shared use, v2.11.0 shows some of the usual diagnostic
output and then freezes instead of announcing why it failed to push.
Horst
Steps to reproduce (tested on Debian 8 "Jessie" amd64):
- User A creates a bare repository:
mkdir /tmp/gittest
git init --bare /tmp/gittest
- User B clones it, adds and commits a file:
git clone /tmp/gittest
cd gittest
echo 42 > x
git add x
git commit -m test
- User B tries to push to user A's bare repo:
git push
Expected result (git v2.10.0 and earlier):
test@ios:~/gittest$ git push
Counting objects: 3, done.
Writing objects: 100% (3/3), 230 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: error: insufficient permission for adding an object to repository database objects
remote: fatal: failed to write object
error: unpack failed: unpack-objects abnormal exit
To /tmp/gittest
! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to '/tmp/gittest'
Actual result (git v2.11.0, v2.12.0, and 2.12.0.189.g3bc53220c):
test@ios:~/gittest$ git push
Counting objects: 3, done.
Writing objects: 100% (3/3), 230 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
[... git freezes here ...]
--
PGP-Key 0xD40E0E7A
next reply other threads:[~2017-03-07 13:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 11:03 Horst Schirmeier [this message]
2017-03-07 11:14 ` regression: git push in non-shared repo stalls (v2.11.0+) Horst Schirmeier
2017-03-07 13:34 ` [PATCH 0/6] deadlock regression in v2.11.0 with failed mkdtemp Jeff King
2017-03-07 13:35 ` [PATCH 1/6] receive-pack: fix deadlock when we cannot create tmpdir Jeff King
2017-03-07 13:35 ` [PATCH 2/6] send-pack: extract parsing of "unpack" response Jeff King
2017-03-07 13:36 ` [PATCH 3/6] send-pack: use skip_prefix for parsing unpack status Jeff King
2017-03-07 13:37 ` [PATCH 4/6] send-pack: improve unpack-status error messages Jeff King
2017-03-07 22:56 ` Junio C Hamano
2017-03-08 5:45 ` Jeff King
2017-03-08 17:19 ` Junio C Hamano
2017-03-07 13:38 ` [PATCH 5/6] send-pack: read "unpack" status even on pack-objects failure Jeff King
2017-03-07 13:39 ` [PATCH 6/6] send-pack: report signal death of pack-objects Jeff King
2017-03-07 13:50 ` [PATCH 0/6] deadlock regression in v2.11.0 with failed mkdtemp Jeff King
2017-03-08 17:58 ` Horst Schirmeier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170307110328.GE7566@quickstop.soohrt.org \
--to=horst@schirmeier.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.