Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Qmail-Scanner-Diagnostics: from mailout3.w1.samsung.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(210.118.77.13):SA:0(-1.3/5.0):. Processed in 0.153871 secs); 31 Jul 2016 11:10:27 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: p.stephenson@samsung.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts) X-AuditID: cbfec7f5-f792a6d000001302-50-579dda3f528b Date: Sun, 31 Jul 2016 12:00:15 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: push error Re: git-subtree completions Message-id: <20160731120015.3e3ec899@pwslap01u.europe.root.pri> In-reply-to: <20160728182845.GB8472@tarsus.local2> References: <27621.1463140958__28965.9567446963$1463141465$gmane$org@thecus.kiddle.eu> <20160707020010.GA25225@tarsus.local2> <20160713042354.GA3279@tarsus.local2> <20160713045910.GB3279@tarsus.local2> <20160728182845.GB8472@tarsus.local2> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: quoted-printable X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsVy+t/xq7r2t+aGG/TtUrA42PyQyYHRY9XB D0wBjFFcNimpOZllqUX6dglcGV9WBRXc4aiYsXMZUwNjI3sXIyeHhICJxNkvb1khbDGJC/fW s4HYQgJLGSX+/IvpYuQCsmcwSTT1z2eGcM4xSqz4+44RwjnLKPF68WxmkBYWAVWJj1ung41i EzCUmLppNiOILSIgLnF27XkWEFtYwFhi3/nfYCt4Bewlura8BDuDU8BI4tXTM0wQQ/cwSez/ MBFsEL+AvsTVv5+YIO6zl5h55QwjRLOgxI/J98CGMguoS0yat4gZwtaWePLuAivED+oSN+7u Zp/AKDwLScssJC2zkLQsYGRexSiaWppcUJyUnmukV5yYW1yal66XnJ+7iRESzl93MC49ZnWI UYCDUYmHdwbn3HAh1sSy4srcQ4wSHMxKIryLrgKFeFMSK6tSi/Lji0pzUosPMUpzsCiJ887c 9T5ESCA9sSQ1OzW1ILUIJsvEwSnVwNj/9aSTpmympm5iNOf6b32lnb4nYnKMn8z81Cd4c3rc p1ufWZrf3srrWyu6/XbZHtcHN2Vbuz801ix9nRsvu1PUboZokEDTFT7POfMXKrTLPhPKTLyn +f/E5gVOq8qdJmZ4Pt0xe/f2Jw9/bPzUcXkTm+2rI9ITrCQflIXwR+0x5zt57bLft1YlluKM REMt5qLiRADoPdVAYwIAAA== X-Seq: zsh-workers 38977 On Thu, 28 Jul 2016 18:28:45 +0000 Daniel Shahaf wrote: > Daniel Shahaf wrote on Wed, Jul 13, 2016 at 04:59:10 +0000: > > % git push=20 > > =E2=8B=AE > > error: insufficient permission for adding an object to repository datab= ase ./objects > >=20 > > fatal: failed to write object > > error: unpack failed: unpack-objects abnormal exit > > To ssh://git.code.sf.net/p/zsh/code > > ! [remote rejected] master -> master (n/a (unpacker error)) > > error: failed to push some refs to 'ssh://git.code.sf.net/p/zsh/code' > > zsh: exit 1 >=20 > I'm getting this again trying to push two other patches. It occurs even > if I push --no-thin and/or from a fresh 'git clone --reference=3D..' clon= e. I think this has just been occasional server trouble when I've seen it. "unpacker" certainly suggests it's the far end. Consequently, I just wait and see if they go away --- which they always have so far ---, checking the SourceForge status to see if there's something they know about, and ultimately would end up raising the issue there, but I haven't had to yet. pws