Git push error - fatal: the remote end hung up unexpectedly

I'm hoping this will be an easy fix. When attempting to git push, I get the following

grommish@norwits:~/openwrt/bin$ git push origin r13628+5
Enumerating objects: 31247, done.
Counting objects: 100% (31247/31247), done.
Delta compression using up to 8 threads
Compressing objects: 100% (31139/31139), done.
client_loop: send disconnect: Broken pipe
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly

Now, searching online brings several expanding the postBuffer posts, and I've done that..

grommish@norwits:~/openwrt/bin$ git config --global ssh.postBuffer 1000000000
grommish@norwits:~/openwrt/bin$ git config --global http.postBuffer 1000000000
grommish@norwits:~/openwrt/bin$ git remote -v
origin (fetch)
origin (push)

I'm not setup for https, though I expanded it just in case.

Any advice would be appreciated!

It's not at all clear what you're trying to accomplish, neither what OS you're trying (it's obviously not OpenWrt), nor what server/ repo you're trying to push.

Just for the avoidance of doubt, OpenWrt's git repositories don't accept pushes from non-developers, you can only push to a private fork somewhere else.

1 Like

Fair enough, let's start over :blush:

I'm pushing the output of the BUILDROOT/bin directory to the github repo used to hold the opkg files for my unsupported device.

In doing this, I had setup a master branch and was able to git push without issue. I switched branches from master to r13628+5 to denote the revision.

I switched branches, added the directory tree, made the commit.

git push origin r13628+5 resulted in the

When attempting to correct the issue, the consensus was to increase the postBuffer size, and I did on both ssh/http

The results are the same error.

If I then switch back to master, re-do the commit and do git push origin master, it's fine

Yes :slight_smile: That is what pull requests are for :wink: I appreciate the patience!

Also, yes the branch ID's are different, as I've rebuilt a few time since I posted this originally. It's safe to assume those would be changed to whatever the current version tag is.

This was a git lfs issue.. Refreshing the branch fixed the issue.

Thank you for attempting to help @slh!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.