How to Fix Pack Header Issues

[SageDev]

Hi

 

We've recently begun picking up an issue with one of our repositories.

Every time one dev attempts to push, or anybody attempts to clone the repository, we get the following errors:

 

Cloning into 'repository name' ...

remote: internal server error

fatal: protocol error: bad pack header

 

(I have noticed that the activity graph and the small "railway tracks" graph next to the commits fail to show up on the gitblit site for this repository. Not sure if that is related.)

 

I've looked around the web, and found posts addressing this issue with "normal" git, but I have so far been unable to find a solution for gitblit.

I've updated our gitblit to the latest version as well. (Didn't resolve anything, but it was a bit overdue.)

 

Please help, this is a project in active development and the situation is becoming a real issue.

 

Thanks in advance

[Tamas Papp]

If I remember correctly, this fixes this issue:

$git config --global http.postBuffer"524288000"


tamas

[SageDev]

On Tuesday, June 10, 2014 3:37:39 PM UTC+2, Tamás PAPP wrote:

If I remember correctly, this fixes this issue:

$git config  --global  http.postBuffer"524288000"


tamas

Thank you for the reply.

 

I must confess thought that I am not very familiar with gitblit (I am not the actual maintainer of the server.). It is also running in a Windows environment without normal git installed.

Could you therefore perhaps elaborate how I should go about entering the command?

 

Thanks

[SageDev]

Ok, so I copied the repository to my local machine where I have git.

 

I ran fsck and found 2 broken links, a dangling tree, commit and blob and a missing commit and tree.

I've tried unpacking the pack files to try and fix it, but no joy so far.

I guess I'll either just drop and recreate the repo, or take it to a dedicated git forum.

 

My remaining question though:

It seems that all this may have happened during a period where my workflow was roughly:

 

finish functionality -> commit

finish functionality -> new commit

finish functionality -> new commit

.

.

end of day -> push all commits to server

 

Could this habit of making a new commit each time, then pushing them in one go have broken the repository? Is it bad form? Should I always just amend one commit and push it at the end of the day?

 

Thanks

[James Moger]

Git is not opinionated on workflow.  If that flow works for you then stick to it.

What version of Gitblit had you been running before the upgrade?

-J

--
You received this message because you are subscribed to the Google Groups "gitblit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gitblit+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[SageDev]

That's good to know, thanks.

 

It was version 1.1.0, if I recall correctly. It was long past due for an upgrade.