From: Matthias Fechner <idefix@fechner.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Cannot push a commit
Date: Tue, 17 Jan 2012 08:35:55 +0100 [thread overview]
Message-ID: <4F1524DB.2080009@fechner.net> (raw)
In-Reply-To: <20120116212036.GA21132@sigill.intra.peff.net>
Am 16.01.2012 22:20, schrieb Jeff King:
> 1. Something in the connection cut out but only in a half-duplex way.
> I guess I could see ssh doing that if its input pipe closed, but
> that would mean the local pack-objects failed, and I believe git
> already detects and reports that case.
>
> 2. The packfile sent indicated that it should have more bytes than it
> does (i.e., either git indicated there were more objects than there
> actually are, or zlib failed to give a stream-end marker in the
> middle of an object). This is one of:
>
> a. A bug in git or zlib.
>
> b. Something in the connection corrupting the data (e.g., a
> transport that is not 8-bit clean).
>
> But in either 2a or 2b, I would expect us to have seen this before, and
> I don't recall seeing anything like it.
>
> You could try generating a bundle with this pack, like:
>
> git bundle create foo.bundle master ^origin/master
>
> and then shipping the resulting foo.bundle to the other side, and
> pulling from it like:
>
> git pull /path/to/foo.bundle master
thanks a lot for your answer.
I created a new repository which is not a bare repo to use your commands
posted above (i tested it with the normal push command from the client
and same error).
I created the bundle on the client, copied it with winscp to the server
and it was applied fine to the repository:
$ git pull ../foo.bundle master
Receiving objects: 100% (3/3), 91.63 KiB, done.
From ../foo.bundle
* branch master -> FETCH_HEAD
Updating 53b9b5e..301e730
Fast-forward
APP_UD.sch |19643
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 19643 insertions(+), 0 deletions(-)
create mode 100644 APP_UD.sch
So the problem should be located anywhere else.
I tested now the same on a mac osx as client and there everything works
as expected, I added the file, commited it and pushed it without errors
to the server.
So the problem has something to do with windows as client. I will do
some additional test this evening.
Where can we continue to search?
Bye
Matthias
--
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
next prev parent reply other threads:[~2012-01-17 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 9:09 Cannot push a commit Matthias Fechner
2012-01-16 18:59 ` Matthias Fechner
2012-01-16 21:20 ` Jeff King
2012-01-17 7:35 ` Matthias Fechner [this message]
2012-01-18 18:25 ` Matthias Fechner
2012-01-19 2:09 ` Jeff King
2012-01-24 6:53 ` Matthias Fechner
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=4F1524DB.2080009@fechner.net \
--to=idefix@fechner.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).