-
Notifications
You must be signed in to change notification settings - Fork 71
Using private Julia package SSH fails #80
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
Is the URL definitely correct? The convention is to use the suffix Otherwise try adding the package from the Julia REPL to see if it is an issue with PythonCall (I doubt it is). |
You are right that it is not PythonCall. I could reproduce the problem in the REPL. Sorry for not trying that and thanks for the suggestion. I created the repo before I learnt of the .jl convention and I think the URL is correct. The Julia creators must own GitHub stock ;) |
It seems there is an issue with a non-standard SSH port. The message in the REPL has swapped : for /
I was using:
It started working with:
|
Great glad it's working. If you think that's a bug in Julia, report it over on the Julia repo. |
I created JuliaLang/Pkg.jl#2894 |
There seems to be a bunch of issues with Julia and SSH with private packages. I'm not sure if the issues I'm seeing are specific to PythonCall. The error I'm seeing is
I'm not using the default .ssh/id_rsa so I enter the path to the private key when prompted. I can clone the repository using git outside of PythonCall using the SSH key.
The text was updated successfully, but these errors were encountered: