Error Unable To Write Sha1 Filename
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the
Unable To Create Temporary Sha1 Filename
company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions unable to create temporary sha1 filename read-only file system Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million
Fatal Unable To Write Sha1 File
programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Git pull error: unable to create temporary sha1 filename up vote 34 down vote favorite 12 I've got a small git error unable to write sha1 filename no such file or directory repo setup with the only real purpose to be able to develop locally on several machines (work, home, laptop). Thus I have one branch and I commit/push once I leave a computer, pull once I sit down at the next. Has worked fine, up to now that is. Now when I pull on my 'live test' machine, I get the following: remote: Counting objects: 38, done. remote: Compressiremote: ng objects: 100% (20/20), done. cannot store pack file remote: Total 20 (delta 17), reused 0 (delta 0) error: unable to create temporary sha1 filename .git/objects/ed: File exists fatal: failed to write object fatal: unpack-objects failed Searching around the net the only real answer I could find was the following: http://marc.info/?l=git&m=122720741928774&w=2 which basically states that this is a bogus error that's on top of the pile and thus says nothing about what really is wrong. Where do I go from here to find out what is wrong? Edit: Removed the local copy and re-cloned git share|improve this question edited Mar 26 '09 at 11:50 asked Mar 26 '09 at 11:08 Ickmund 338138 add a comment| 19 Answers 19 active oldest votes up vote 31 down vote accepted For what it's worth, when I had this problem—but when committing—I tried git-repack and git-gc, but neither worked. I got a permission denied error, which led me to chown the entire repo recursively to the user I expected it to be, and I could then commit/push/pull with no problem. share|improve this answer edited Mar 12 '15 at 0:47 answered Mar 28 '09 at 2:36 aresnick 827516 1 Interesting variation on this - I was using git-daemon with one of my repositories for a while, then switched to local check ins/outs for some hook testing I wanted to do because git-dae
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this
Git Clone Error: Unable To Write Sha1 Filename
site About Us Learn more about Stack Overflow the company Business Learn git unable to write sha1 filename windows more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question
Error: File Write Error (no Space Left On Device)
x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Write http://stackoverflow.com/questions/685319/git-pull-error-unable-to-create-temporary-sha1-filename error when cloning repository up vote 1 down vote favorite 1 $ sudo git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen remote:Counting objects:2275852,done. remote:Compressing objects:100%(362867/362867) done. Receiving objects:100%(2275852/2275852), 453.53MB | 37kiB/s, done remote:Total 2275852 (delta 1901047),reused 2265649 (delta 1891419) Resolving deltas:100% (1901047/1901047)done. error:unable to write sha1 filename /usr/src/linux-2.6-xen/.git/objects/pack/pck-176ee0822d6d3afed83c05b32f2125e49ede7f7c.pack: No such file or directory fatal :cannot store pack file fatal :index-pack failed git share|improve this question edited Jun 6 http://stackoverflow.com/questions/9512805/write-error-when-cloning-repository '14 at 14:00 isherwood 30.5k65586 asked Mar 1 '12 at 8:23 tony lv 1413 This usually happens when you halt a git clone for some reason, try deleting the folder and cloning it again. –Pedro Nascimento Mar 1 '12 at 8:31 another solution? the problem is still here. –tony lv Mar 1 '12 at 8:41 2 You could also check if you have enough free space left on your disk. –Pedro Nascimento Mar 1 '12 at 8:50 Thanks ,but there is enough space for this file. –tony lv Mar 1 '12 at 8:54 1 @Dave: I don't think whether using sudo or not when generating the key initially has anything to do with the problem at hand. He is cloning from a public git link after all, there is no need for keys. –Daniel Le Mar 1 '12 at 9:34 | show 5 more comments 1 Answer 1 active oldest votes up vote 0 down vote Are you sure your user has write permissions for the /usr/src directory? Try cloning to some other directory with full read/write access. (e.g: /tmp) share|im
from GoogleSign inHidden fieldsSearch for groups or messages