{"thread":{"id":"45304","subject":"Re: regression: git push in non-shared repo stalls (v2.11.0+)","startedAt":"2017-03-07T11:21:30Z","lastAt":"2017-03-07T13:47:30Z","messageCount":2,"participants":["Horst Schirmeier"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"313406","messageId":"20170307111406.GB1955@quickstop.soohrt.org","threadId":"45304","inReplyTo":"20170307110328.GE7566@quickstop.soohrt.org","subject":"Re: regression: git push in non-shared repo stalls (v2.11.0+)","fromName":"Horst Schirmeier","fromEmail":"horst@schirmeier.com","sentAt":"2017-03-07T11:14:06Z","receivedAt":"2017-03-07T11:21:30Z","isPatch":false,"sender":{"key":"horst@schirmeier.com","avatar":null},"body":"On Tue, 07 Mar 2017, Horst Schirmeier wrote:\n> I observe a regression that seems to have been introduced between\n> v2.10.0 and v2.11.0.  When I try to push into a repository on the local\n> filesystem that belongs to another user and has not explicitly been\n> prepared for shared use, v2.11.0 shows some of the usual diagnostic\n> output and then freezes instead of announcing why it failed to push.\n\nBisecting points to v2.10.1-373-g722ff7f:\n\n722ff7f876c8a2ad99c42434f58af098e61b96e8 is the first bad commit\ncommit 722ff7f876c8a2ad99c42434f58af098e61b96e8\nAuthor: Jeff King <peff@peff.net>\nDate:   Mon Oct 3 16:49:14 2016 -0400\n\n    receive-pack: quarantine objects until pre-receive accepts\n\n-- \nPGP-Key 0xD40E0E7A\n"},{"id":"313412","messageId":"20170307110328.GE7566@quickstop.soohrt.org","threadId":"45304","inReplyTo":null,"subject":"regression: git push in non-shared repo stalls (v2.11.0+)","fromName":"Horst Schirmeier","fromEmail":"horst@schirmeier.com","sentAt":"2017-03-07T11:03:28Z","receivedAt":"2017-03-07T13:47:30Z","isPatch":false,"sender":{"key":"horst@schirmeier.com","avatar":null},"body":"Hi,\n\nI observe a regression that seems to have been introduced between\nv2.10.0 and v2.11.0.  When I try to push into a repository on the local\nfilesystem that belongs to another user and has not explicitly been\nprepared for shared use, v2.11.0 shows some of the usual diagnostic\noutput and then freezes instead of announcing why it failed to push.\n\nHorst\n\nSteps to reproduce (tested on Debian 8 \"Jessie\" amd64):\n -  User A creates a bare repository:\n    mkdir /tmp/gittest\n    git init --bare /tmp/gittest\n -  User B clones it, adds and commits a file:\n    git clone /tmp/gittest\n    cd gittest\n    echo 42 > x\n    git add x\n    git commit -m test\n -  User B tries to push to user A's bare repo:\n    git push\n\nExpected result (git v2.10.0 and earlier):\ntest@ios:~/gittest$ git push\nCounting objects: 3, done.\nWriting objects: 100% (3/3), 230 bytes | 0 bytes/s, done.\nTotal 3 (delta 0), reused 0 (delta 0)\nremote: error: insufficient permission for adding an object to repository database objects\nremote: fatal: failed to write object\nerror: unpack failed: unpack-objects abnormal exit\nTo /tmp/gittest\n ! [remote rejected] master -> master (unpacker error)\nerror: failed to push some refs to '/tmp/gittest'\n\nActual result (git v2.11.0, v2.12.0, and 2.12.0.189.g3bc53220c):\ntest@ios:~/gittest$ git push\nCounting objects: 3, done.\nWriting objects: 100% (3/3), 230 bytes | 0 bytes/s, done.\nTotal 3 (delta 0), reused 0 (delta 0)\n[... git freezes here ...]\n\n-- \nPGP-Key 0xD40E0E7A\n"}]}