Error: ENOENT, No such file or directory 'packed-refs'

[TooTallNate]

When attempting to use this lib on a "bare" git repo with a single commit pushed to it, I get this:

/home/nrajlich/wheat/lib/wheat.js:74
            if (err) { throw err; }
                       ^
Error: ENOENT, No such file or directory '/home/nrajlich/blog.git/packed-refs'
at node.js:221:9

When does the packed-refs file get created in Git? I worked around it by commenting out everything related to packed-refs in the Git.getHead method, and it seems to work fine, but obviously that's not the right way.

Any heads up? Or I guess node-git should be patched to check for the existence of that file before trying to read it, so that this error never happens :)

EDIT: I was further able to fix the error by simply running:

git pack-refs

and then the packed-refs file was created. I'm still in favor of checking for the existence of the file first. I'll try and get a patch ready if I have time.

[creationix]

Is this still an issue? I want the code to always get the correct HEAD sha no matter what valid state the git repo is in.

[TooTallNate]

Ya it's pretty much fixed. Like I said, I just had to run git pack-refs to make the packed-refs file be created. After that everything worked fine.

I guess if somebody else tried this module on a bare repo without that file in it the same error would happen, which is why I was suggesting to check the existence of the file first. The error is gone for me though...

[XULRunner42]

How do I ensure that my remote repository uses packed-refs?

I am trying to deploy wheat on nodester platform... the main nodester remote at least does not do pack-refs, and is in a locked-down chroot with no "git" binary or even the correct libraries to run ls.

So, I've verified that I have description, refs, hooks, config, index, HEAD, logs, FETCH_HEAD, ORIG_HEAD, info, objects, branches, and no packed-refs... I'm going to see if they might consider running pack-refs. If no, is there something else we could use?

[creationix]

@XULRunner42, if you don't have a git binary I don't think this is going to work at all. This library uses the git binary for everything except for the quick check to find the latest hash.

[XULRunner42]

Ok thanks! I am working with nodester guys to redeploy their hosted
platform on my own hardware, once I'm there, it should be no trouble adding
the git binary to the chroot. Thanks for the advice!
On Feb 20, 2012 10:27 AM, "Tim Caswell" <
[email protected]>
wrote:

@XULRunner42, if you don't have a git binary, I don't think this is
going to work at all. This library uses the git binary for everything
except for the quick check to find the latest hash.

---

Reply to this email directly or view it on GitHub:
#1 (comment)