maemo.org - Talk - Problem with git push to Garage: "cannot lock existing info/refs"

maemo.org - Talk (https://talk.maemo.org/index.php)

- Development (https://talk.maemo.org/forumdisplay.php?f=13)

- - Problem with git push to Garage: "cannot lock existing info/refs" (https://talk.maemo.org/showthread.php?t=89831)

Problem with git push to Garage: "cannot lock existing info/refs"

Hi folks,

I'm just getting back to coding for the N900 after a long hiatus, and wanted to push some changes up to my app's code repository (this being the Pierogi app). But, I kind of messed things up. First, I did a "git push", which did not succeed, because some files failed to be uploaded. This was a fault on my side -- my internet connection was acting flakey. I fixed that problem, and tried "git push" again. However, this time I got back the error message:

Code:

$ git push

Fetching remote heads...

  refs/

  refs/heads/

  refs/tags/

updating 'refs/heads/master'

  from 741e390184f91b94c413745f43820d59c7362530

  to   0a7fde1679bf2bccd4d4cc33a7f8241e649d6781

    sending 43 objects

MOVE f8872942bb7535edb070c6b76b78f6d125b50ae3 failed, aborting (22/502)

error: git-http-push died of signal 11

fatal: git-http-push failed

I'm not sure where the "signal 11" came from; it may be that the first git push left the repository in an unstable state? Anyway, not knowing what else to do, I simply tried "git push" one more time. This time, the error message was:

Code:

$ git push

error: cannot lock existing info/refs

fatal: git-http-push failed

And now, I get this message every time I try another push. I'm fairly certain at this point that I've messed something up here. I'm not a git expert, and I have to admit I haven't kept up as well as I should have with the changes made to the Maemo servers at the beginning of the year, so I figured I should ask the experts here first: is there something obvious that I've done wrong? Thanks! :)

Re: Problem with git push to Garage: "cannot lock existing info/refs"

A bit of an update; it appears that the lock and "signal 11" stuff cleared itself up after a while. The "22/502" message keeps coming up though; it doesn't seem to actually be related to my network issues.

I've found some info on this git error:

Quote:

If git-http-push shows you an error (22/502) when trying to MOVE a blob, it means that your web-server somehow does not recognize its name in the request; This can happen when you start Apache, but then disable the network interface. A simple restart of Apache helps.

It is quite possible, after all the changes at the beginning of the year, that the name of the web-server has in fact changed, and I've just got the old name embedded somewhere in my git configuration. Maybe someone else has already tripped over this, and knows how to set the correct name? :)

Re: Problem with git push to Garage: "cannot lock existing info/refs"

Alright, I'm about ready to throw in the towel here. Tonight, in total frustration, I cloned a fresh copy of Pierogi down from the garage website, painstakingly copied each file that had changed in the last month over to it, did a fresh commit, and tried to push it back up.

And yes, I'm still getting exactly the same "MOVE ... failed, aborting (22/502)" messages as before.

Is the garage still working for anybody at all?

At this rate, I guess I'll have to see if I can find a different site to host Pierogi. :(