-
Notifications
You must be signed in to change notification settings - Fork 323
git2/sys/cred.h: No such file or directory #535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
seems like you have two choices:
|
Hi @lhchavez, I'm the libgit2 maintainer. And we're not using Debian stable for development, we use unstable (and from which, packages migrate to testing). So I'm getting this error while building against 0.28.4.1. Any clue how to go about it now? |
oh! sorry, i'm not very familiar with non-stable Debian ^^;;
let me try to spin up a Docker container. |
welp, i cannot reproduce this :S here's what I tried cat > Dockerfile<<EOF
FROM debian:unstable # debian:testing yields the same results
RUN apt-get update -y
RUN apt-get install -y curl libgit2-dev gcc git pkg-config
RUN curl --location https://dl.google.com/go/go1.13.8.linux-amd64.tar.gz | tar -xz
ENV PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/go/bin
WORKDIR /root/go
RUN go get gopkg.in/libgit2/git2go.v28
EOF
docker run -it --rm $(docker build -q .) go test -test.v gopkg.in/libgit2/git2go.v28/... the other weird thing is that the line that you shared does not match the current state of the is there anything I could have missed? |
Hi @lhchavez,
This is indeed a nice catch! Seems like I was pulling from the master instead of the v28 branch. I fixed that, pulled the right tar ball and everything worked! :D |
whew! glad that it all worked out in the end! |
While building the latest release in Debian, I get the following build failure:
Any idea how to go about it?
The text was updated successfully, but these errors were encountered: