-
Notifications
You must be signed in to change notification settings - Fork 421
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
libssh-dev installed instead of libssh2-1-dev? #423
Comments
Thanks for the report, @vin01. @aboe76 @javierbertoli Any ideas about this? |
@vin01 installing from git is trickier because of tracking al depencies, if you want to fix the git build with a PR to include libssh2-1-devel I'm all for it, having a functional gitfs with pygit2 because that's what saltstack is preferring according to the docs. |
Thanks for your quick responses @aboe76 @myii I had to choose installation from git to be able to use specific versions because of issues like this one which will be fixed in the next release. @aboe76 Since you mentioned libssh2-1- I did a quick check on
|
@vineet-kum I was just checking the page on libgit2 on debian and saw the depency. see: and checking the dsc file for libgit2: http://cdn-fastly.deb.debian.org/debian/pool/main/libg/libgit2/libgit2_0.27.7+dfsg.1-0.2.dsc Build-Depends: debhelper (>= 11~), python-minimal (>= 2.4.0), pkg-config, cmake, libz-dev, libmbedtls-dev, libssh2-1-dev, libhttp-parser-dev, libkrb5-dev |
@aboe76 Thanks once again! That is correct. With package based installation, it is perfectly fine and all dependencies are taken care of however with installation from git or let's say from source is what gets tricky. adding |
@aboe76 Just to follow up on this and make a decision. I think other than |
Hi Team!
Currently, the formula does not seem to support SSH auth for gitfs. I am not sure if this is intentional as I can see
libssh-dev
is being installed here as a dependency sincelibgit2
needs it to be able to support SSH. However, it does not work becauselbigit2
needs libssh2..I also noticed this issue where migration to
libssh
was being discussed but apparently, it has been a while now without any updates on this.In my fork I am using
libssh2-1-dev
and it works as expected.I will like to know why
libssh-dev
is being used in the formula instead oflibssh2-1-dev
and if it makes sense, I will be happy to send a PR to fix the same.Thanks!
The text was updated successfully, but these errors were encountered: