could not determine kind of name for C.GIT_CHECKOUT_SAFE_CREATE

[shawnl]

commit 98793509039cc80b774c527d9e5a7b5d70e3b6c4
Author: Shawn Landden <shawn@churchofgit.com>
Date:   Sat Mar 14 15:42:25 2015 -0700

    GIT_CHECKOUT_SAFE_CREATE has been removed in libgit2

    Signed-off-by: Shawn Landden <shawn@churchofgit.com>

diff --git a/checkout.go b/checkout.go
index 6eb6098..9456168 100644
--- a/checkout.go
+++ b/checkout.go
@@ -15,7 +15,6 @@ type CheckoutStrategy uint
 const (
        CheckoutNone                      CheckoutStrategy = C.GIT_CHECKOUT_NONE                         // Dry run, no actual updates
        CheckoutSafe                      CheckoutStrategy = C.GIT_CHECKOUT_SAFE                         // Allow safe updates that cannot overwrite uncommitted data
-       CheckoutSafeCreate                CheckoutStrategy = C.GIT_CHECKOUT_SAFE_CREATE                  // Allow safe updates plus creation of missing files
        CheckoutForce                     CheckoutStrategy = C.GIT_CHECKOUT_FORCE                        // Allow all updates to force working directory to look like index
        CheckoutAllowConflicts            CheckoutStrategy = C.GIT_CHECKOUT_ALLOW_CONFLICTS              // Allow checkout to make safe updates even if conflicts are found
        CheckoutRemoveUntracked           CheckoutStrategy = C.GIT_CHECKOUT_REMOVE_UNTRACKED             // Remove untracked files not in index (that are not ignored)

[shawnl]

Sorry about the formatting. I hate github pull requests.

[carlosmn]

This is just one change that would have to be made to let the master branch build with libgit2's master, but this doesn't update the bundled libgit2 to a version which would need this change so it's just removing some functionality which we do ship with.

[b35li]

Yeah, I got this error when I run "go install" in git2go. Do you know what version of git2go to use? Now I am working on master branch.

[b35li]

When I checked out to next, I saw the change above, when will you merge to master? Otherwise ,what version of libgit2 I should use for the git2go on master?

[carlosmn]

See the README file for which branch goes with with libgit2 branch. next will be merged to master when libgit2 makes a release with those changes in it.

[carlosmn]

This change is now in next along with the rest of changes needed to make it compile against libgit2 master, so I'm going to close this.

[shawnl]

upsteam became incompatible again:
./merge.go:100: opts.flags undefined (type *C.struct___2 has no field or method flags)
./merge.go:126: unknown C.struct___2 field 'flags' in struct literal
./merge.go:336: cannot use C.git_merge_file_flags_t(options.Flags) (type C.git_merge_file_flags_t) as type C.uint in assignment

[b35li]

@carlosmn Thanks. Got it, wonderful.

[b35li]

@carlosmn when will the changes be merged to master and be made a release?

[shawnl]

When upstream makes a release

[carlosmn]

The master branch for libgit2 did move, but that doesn't matter because git2go has the submodule with the working version.

[tony]

I was able to fix this by moving checking out v0.22.2 (the latest stable release available through git tags) for libgit2.

[gbbr]

On branch next I get:

# github.com/libgit2/git2go
could not determine kind of name for C.GIT_ECONFLICT

[carlosmn]

It looks like you forgot to run git submodule update

[gbbr]

Even with git submodule update the same thing happens on OS X. For context:

gbbr@mecca:git2go (next)$ git submodule status
 b6011e296e4db6942d71f5a8548d1308353927ee vendor/libgit2 (v0.16.0-6344-gb6011e2)

[gbbr]

Nevermind, I had to RTFM :) Thanks

[gr4y]

I didn't want to create an new issue, so I just dug that old issue out of the trash. Sorry, about that.

$ ~/git-webhook[master]: go get gopkg.in/libgit2/git2go.v22
# gopkg.in/libgit2/git2go.v22
could not determine kind of name for C.GIT_CHECKOUT_SAFE_CREATE

go version: go1.4.2 darwin/amd64

I don't have any submodules to update, so I can't do that.

[gr4y]

So I found out that homebrew provides version 0.23.0, so I installed 0.22.3 manually and pinned it for now.

Edit:
I will put that here for any developers on OS X who run into the same problem and don't know what to do:

brew unlink libgit2
brew install https://raw.githubusercontent.com/Homebrew/homebrew/d6a9bb6adeb2043c5c5e9ba3a878decdefc1d240/Library/Formula/libgit2.rb
brew switch libgit2 0.22.3
brew pin libgit2

The last line pins libgit2 to 0.22.3, so if you want to use 0.23.0 or later you have to brew unpin libgit2 first!

[phonyphonecall]

@gr4y that worked perfect for me. Thanks! 👍

[ef2k]

Ran into this issue, solved by @gr4y above. Thanks.