Subject: Cannot obtain needed blob error while using http
When I try to use http: to clone, pull or submodulize a repository it fails with an error that it cannot obtain a needed blob.
I am unable to use git transferring due to a bug with GIT
[I know, git's still beta and all that. Their looking into it over
at the project page.]
I see many other threads with very similar complaints, and they
all end with defunkt saying the problem is fixed.
Could I get some of the same magic?
The project:
http://github.com/digitarald/digitarald-fancyupload.git
The error:
error: Unable to verify pack
8efa9b32a1742a5d6aa01dd15711d13ebd8ddf42 is available
error: Unable to find 3469ef36bb5082d6032ade2632151096605908c1
under http://github.com/digitarald/digitarald-fancyupload.git
Cannot obtain needed blob
3469ef36bb5082d6032ade2632151096605908c1
while processing commit
d87fa23946b6d7ad4d3103d0a7b5b068e4752cef.
fatal: Fetch failed.
Off Topic:
The only reason I continue suffering at the hands of GIT is for the
community, features, and related projects here on GITHUB.
I greatly admire your ability to make such a wonderful asset out of
such a poorly executed system.
Keep up the great work!
Support Staff 2 Posted by Tekkub on 26 Aug, 2009 01:13 AM
Are you unable to clone over git due to a firewall or something, and thus forced to clone over http? Http cloning can be a pain sometimes, the server has to do extra work to keep the data fresh and the limits of http slow down the transfer. I'd suggest you only use it as a last resort, cloning over git works much better.
That being said, I've bumped the repo for you, http cloning should work again.
3 Posted by ssgoodman on 26 Aug, 2009 08:42 AM
Thanks, but it still does not work.
I am unable to clone over git due to GIT being buggy software (and that may the least of its flaws).
Originally I was unable to connect to git at all:
See one of my threads here: http://code.google.com/p/msysgit/issues/detail?id=243
Now that that has been resolved (with a lot of very helpful work by one Johannes from GIT) I am able to connect to my GITHub account using my private git@.. url.
But NOT when using a public URL - only when using the git@.. url.
This appears to be a problem with GIT's SSH implementation, and is being looked into.
[Please forgive the attitude. My boss is not thrilled with with the many days I have already put into helping debug GIT. The connection problem is one of many. ]
That fortunately doesn't seem to be a problem. Perhaps due to the small size of the project.
It still doesn't work.
end of the output looks like:
got 955c55154575bf6df741c27350a437d305b8bff6 error: Unable to verify pack 8efa9b32a1742a5d6aa01dd15711d13ebd8ddf42 is available<br/> error: Unable to find 3469ef36bb5082d6032ade2632151096605908c1 under http://github.com/digitarald/digitarald-fancyupload.git<br/> Cannot obtain needed blob 3469ef36bb5082d6032ade2632151096605908c1<br/> while processing commit 357869a229e2876cd5b8418b26425cd247eddcb5.<br/> fatal: Fetch failed.<br/> Clone of 'http://github.com/digitarald/digitarald-fancyupload.git' into submodul<br/> e path 'siteroller/classes/fancyupload/repo' failedSupport Staff 4 Posted by Tekkub on 26 Aug, 2009 11:13 PM
The "attitude" is understandable, don't apologize. You're running into some weird errors that I've not seen any other users hitting. Usually it's just a straight shot, install, clone, code.
When I sent that message,
git clone http://github.com/digitarald/digitarald-fancyupload.gitworked for me. I tested again just now and didn't encounter any errors. It doesn't look like anyone has pushed to the repo recently, but when they do there is likely to be a delay before the http cloning info is updated, and errors could happen then but are unlikely.Here's the output of my clone (run on my vista box): https://gist.github.com/b1fb997d2481de81e13d
If you search, you'll see that it fetches each SHA1 that your output is erroring on. You don't have a firewall or proxy that might be interfering with the http clone do you?
5 Posted by ssgoodman on 27 Aug, 2009 07:27 AM
Thanks for checking. Rather odd, that.
The firewall and anti-virus were shut down for testing, and there are no proxies or packet sniffers running. Running XP Pro.
I don't understand the concern though - if there was a firewall issue, wouldn't it have balked before even getting the first commit?
Also, is there a way I can check if the 'cannot obtain blob' error is being generated by the GITHub server and passed down, or if it is being generated by my local instance of GIT?
The actual blob it errors on is not actually called - it is included inside a verified pack. Whatever the problem is seems to be coming from the fact that the pack is unverified.
Your working response:
My non-working response:
Git does not call the commits in easily discernible order, so each time I attempt this I get a slightly different output. But the err on all is the same.
I have posted my multiple attempt track record, in the hope that it might be useful:
http://gist.github.com/176152
Thank you.
6 Posted by ssgoodman on 30 Aug, 2009 08:34 AM
On the thread over at msysgit I mentioned the problem, and it seems I am not the only one who has it. Any ideas of a workaround? I am a bit stuck here.
http://code.google.com/p/msysgit/issues/detail?id=316
Support Staff 7 Posted by defunkt on 31 Aug, 2009 07:54 PM
What version of git are you using? Sorry if I missed it, I can't find the info in this thread.
Chris
8 Posted by ssgoodman on 31 Aug, 2009 08:47 PM
Oops, guess I should've included that.
Thanks
Support Staff 9 Posted by Tekkub on 03 Sep, 2009 01:18 AM
Good news everyone!
Well okey might not be good news but I like saying that. Anywho, another test: http://gist.github.com/180066 The difference there? That's git version 1.6.4-preview20090730, the other tests I ran on Windows were git version 1.6.0.2.1172.ga5ed0
You might want to try an earlier version of msysgit instead of the "preview" and see if things work correctly.