From: Rafael Darder Calvo <rdarder@spiralti.com>
To: git@vger.kernel.org
Subject: git-push error: Cannot write keep file
Date: Tue, 24 Feb 2009 15:04:55 -0200 [thread overview]
Message-ID: <49A428B7.4000003@spiralti.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
Hello,
I am having the following error when I try to git push.
rdarder@shiny:~/Sources/promotoras$ git push origin ranto:ranto
Counting objects: 256, done.
Compressing objects: 100% (199/199), done.
Writing objects: 100% (213/213), 216.94 KiB, done.
Total 213 (delta 60), reused 1 (delta 0)
fatal: cannot write keep file
error: unpack failed: index-pack abnormal exit
To ssh://fherrero@10.7.1.20:2222/var/www/promotoras.git
! [remote rejected] ranto -> ranto (n/a (unpacker error))
error: failed to push some refs to
'ssh://fherrero@10.7.1.20:2222/var/www/promotoras.git'
I couldn't find any significant description on the error "cannot write
keep file". git-fsck passes without errors in both repositories, and I
find no permission problems. Can anyone give me some directions on how
to diagnose this?
Regards,
Rafael
[-- Attachment #2: rdarder.vcf --]
[-- Type: text/x-vcard, Size: 266 bytes --]
begin:vcard
fn:Rafael Darder Calvo
n:Darder Calvo;Rafael
org:;Infraestructura
adr:;;Mitre 1017 Piso 5;Rosario;Santa Fe;S2000COU;Argentina
email;internet:rdarder@spiralti.com
title:Spiralti Rosario
tel;work:+54 341 5302041
url:www.spiralti.com
version:2.1
end:vcard
next reply other threads:[~2009-02-24 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 17:04 Rafael Darder Calvo [this message]
2009-02-24 17:31 ` git-push error: Cannot write keep file Junio C Hamano
2009-02-24 21:21 ` Rafael Darder Calvo
2009-02-25 7:11 ` [PATCH v2] Make sure objects/pack exists before creating a new pack Junio C Hamano
2009-02-25 7:15 ` Junio C Hamano
2009-02-26 9:19 ` Johannes Sixt
2009-02-26 11:19 ` Mike Ralphson
2009-02-26 15:31 ` Johannes Sixt
2009-02-26 15:54 ` Mike Ralphson
2009-02-26 17:07 ` Junio C Hamano
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=49A428B7.4000003@spiralti.com \
--to=rdarder@spiralti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).