RE: [julia-users] Cloning private package with 0.5
https://github.com/JuliaLang/julia/issues/16041
We can continue this discussion there. I think that issue should get a 0.5.0
label, i.e. this should be treated as a regression that has to be fixed before
0.5 can be released.
Cheers,
David
From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On
Behalf Of David Anthoff
Sent: Monday, April 25, 2016 11:16 AM
To: julia-users@googlegroups.com
Subject: RE: [julia-users] Cloning private package with 0.5
That doesn’t work for bitbucket repos, though…
From: karbar...@gmail.com <mailto:karbar...@gmail.com>
[mailto:karbar...@gmail.com] On Behalf Of Jacob Quinn
Sent: Sunday, April 24, 2016 8:49 PM
To: julia-users@googlegroups.com <mailto:julia-users@googlegroups.com>
Subject: Re: [julia-users] Cloning private package with 0.5
Note that it's currently possible to clone private GitHub repos using "personal
access tokens" from Github. If you go to your profile/settings, you can
generate private access tokens that allow access to private Github repos and
then from Julia, you can clone with the following format:
Pkg.clone("https://username:to...@github.com/username/private_repo.jl;)
On Fri, Apr 22, 2016 at 5:57 PM, Eric Forgy <eric.fo...@gmail.com
<mailto:eric.fo...@gmail.com> > wrote:
I have the same problem (on Windows) and really hoping this gets fixed before
0.5 is released. I have a ton of private repos.
I'd prefer a solution that lets me keep my remotes at
g...@github.com:EricForgy/MyPrivateRepo.jl
<mailto:g...@github.com:EricForgy/MyPrivateRepo.jl> . It would be more than a
little annoying if I have to change every one to https. Hopefully, Pkg can do
some magic and make the changes for me if needed.
RE: [julia-users] Cloning private package with 0.5
That doesn’t work for bitbucket repos, though…
From: karbar...@gmail.com [mailto:karbar...@gmail.com] On Behalf Of Jacob Quinn
Sent: Sunday, April 24, 2016 8:49 PM
To: julia-users@googlegroups.com
Subject: Re: [julia-users] Cloning private package with 0.5
Note that it's currently possible to clone private GitHub repos using "personal
access tokens" from Github. If you go to your profile/settings, you can
generate private access tokens that allow access to private Github repos and
then from Julia, you can clone with the following format:
Pkg.clone("https://username:to...@github.com/username/private_repo.jl;)
On Fri, Apr 22, 2016 at 5:57 PM, Eric Forgy <eric.fo...@gmail.com
<mailto:eric.fo...@gmail.com> > wrote:
I have the same problem (on Windows) and really hoping this gets fixed before
0.5 is released. I have a ton of private repos.
I'd prefer a solution that lets me keep my remotes at
g...@github.com:EricForgy/MyPrivateRepo.jl
<mailto:g...@github.com:EricForgy/MyPrivateRepo.jl> . It would be more than a
little annoying if I have to change every one to https. Hopefully, Pkg can do
some magic and make the changes for me if needed.
RE: [julia-users] Cloning private package with 0.5
None of the suggestions in [1,2] work. They are all based on command line git
using a credential helper. I have a working credential helper for command line
git on my system, but Pkg.clone doesn’t seem to know or use that credential
helper at all. As far as I can tell, libgit2 is not using credential helpers in
the first place, so that whole route probably doesn’t help.
About SSH, is the plan to make those changes to the makefile and include
libssh2 in the windows binary distribution, so that one can just clone private
repos via ssh? That would be great!
From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On
Behalf Of Isaiah Norton
Sent: Saturday, April 23, 2016 12:56 PM
To: julia-users@googlegroups.com
Subject: Re: [julia-users] Cloning private package with 0.5
I would hope that this is a release blocker issue, given that private package
repos have been supported forever.
So right now there seems no way to use them on 0.5 from Windows...
https:// should be supported, although I haven't tried it on Windows. See [1,2]
for configuration details and instructions to avoid password prompts.
Regarding ssh, see [3]:
building against libssh2 is explicitly disabled by our Makefile.
(this line [2])
Switching ssh on for windows would require Makefile rules to build and package
libssh2 along with libgit2 and the rest of the libraries. Note that libssh2 can
use native windows crypto functionality ("WinCNG" backend), so it should not
impose any further requirements.
[1]
https://help.github.com/articles/which-remote-url-should-i-use/#cloning-with-https-urls-recommended
[2]
http://stackoverflow.com/questions/13800289/configure-git-clients-like-github-for-windows-to-not-ask-for-authentication/18607931#18607931
[3] https://groups.google.com/d/msg/julia-users/GEwX49wwmdo/CihXC62yCAAJ
[4]
https://github.com/JuliaLang/julia/blob/c2042326cc5d68db01c0b2e0d12a15f48b03563a/deps/Makefile#L2094
On Fri, Apr 22, 2016 at 8:30 PM, David Anthoff <anth...@berkeley.edu
<mailto:anth...@berkeley.edu> > wrote:
Yes, I would hope that this is a release blocker issue, given that private
package repos have been supported forever. I also have a very large number of
private repos.
So right now there seems no way to use them on 0.5 from Windows...
I also would prefer to use SSH keys for authentication. If it does have to be
https, I guess it would be ok if things are integrated with the git credential
storage infrastructure. What would really be sort of a disaster is if I was
asked for a username and password every time I do an Pkg.update() or something
like that...
> -Original Message-
> From: julia-users@googlegroups.com <mailto:julia-users@googlegroups.com>
> [mailto:julia- <mailto:julia->
> us...@googlegroups.com <mailto:us...@googlegroups.com> ] On Behalf Of Eric
> Forgy
> Sent: Friday, April 22, 2016 4:58 PM
> To: julia-users <julia-users@googlegroups.com
> <mailto:julia-users@googlegroups.com> >
> Subject: RE: [julia-users] Cloning private package with 0.5
>
> I have the same problem (on Windows) and really hoping this gets fixed
> before 0.5 is released. I have a ton of private repos.
>
> I'd prefer a solution that lets me keep my remotes at
> g...@github.com:EricForgy/MyPrivateRepo.jl
> <mailto:g...@github.com:EricForgy/MyPrivateRepo.jl> . It would be more than a
> little
> annoying if I have to change every one to https. Hopefully, Pkg can do some
> magic and make the changes for me if needed.
Re: [julia-users] Cloning private package with 0.5
Thanks Jacob. I'll have a look at that, but would that help with Travis and Appveyor? In Git for Windows, am I really going to have to change all my remotes for all my private repos now? That will be a huge pain. Can Pkg please do this for me? Where would be a good place to raise this issue?
Re: [julia-users] Cloning private package with 0.5
Note that it's currently possible to clone private GitHub repos using
"personal access tokens" from Github. If you go to your profile/settings,
you can generate private access tokens that allow access to private Github
repos and then from Julia, you can clone with the following format:
Pkg.clone("https://username:to...@github.com/username/private_repo.jl;)
On Fri, Apr 22, 2016 at 5:57 PM, Eric Forgy wrote:
> I have the same problem (on Windows) and really hoping this gets fixed
> before 0.5 is released. I have a ton of private repos.
>
> I'd prefer a solution that lets me keep my remotes at
> g...@github.com:EricForgy/MyPrivateRepo.jl.
> It would be more than a little annoying if I have to change every one to
> https. Hopefully, Pkg can do some magic and make the changes for me if
> needed.
Re: [julia-users] Cloning private package with 0.5
>
> I would hope that this is a release blocker issue, given that private
> package repos have been supported forever.
>
So right now there seems no way to use them on 0.5 from Windows...
https:// should be supported, although I haven't tried it on Windows. See
[1,2] for configuration details and instructions to avoid password prompts.
Regarding ssh, see [3]:
building against libssh2 is explicitly disabled by our Makefile.
(this line [2])
Switching ssh on for windows would require Makefile rules to build and
package libssh2 along with libgit2 and the rest of the libraries. Note that
libssh2 can use native windows crypto functionality ("WinCNG" backend), so
it should not impose any further requirements.
[1]
https://help.github.com/articles/which-remote-url-should-i-use/#cloning-with-https-urls-recommended
[2]
http://stackoverflow.com/questions/13800289/configure-git-clients-like-github-for-windows-to-not-ask-for-authentication/18607931#18607931
[3] https://groups.google.com/d/msg/julia-users/GEwX49wwmdo/CihXC62yCAAJ
[4]
https://github.com/JuliaLang/julia/blob/c2042326cc5d68db01c0b2e0d12a15f48b03563a/deps/Makefile#L2094
On Fri, Apr 22, 2016 at 8:30 PM, David Anthoff <anth...@berkeley.edu> wrote:
> Yes, I would hope that this is a release blocker issue, given that private
> package repos have been supported forever. I also have a very large number
> of private repos.
>
> So right now there seems no way to use them on 0.5 from Windows...
>
> I also would prefer to use SSH keys for authentication. If it does have to
> be https, I guess it would be ok if things are integrated with the git
> credential storage infrastructure. What would really be sort of a disaster
> is if I was asked for a username and password every time I do an
> Pkg.update() or something like that...
>
> > -Original Message-
> > From: julia-users@googlegroups.com [mailto:julia-
> > us...@googlegroups.com] On Behalf Of Eric Forgy
> > Sent: Friday, April 22, 2016 4:58 PM
> > To: julia-users <julia-users@googlegroups.com>
> > Subject: RE: [julia-users] Cloning private package with 0.5
> >
> > I have the same problem (on Windows) and really hoping this gets fixed
> > before 0.5 is released. I have a ton of private repos.
> >
> > I'd prefer a solution that lets me keep my remotes at
> > g...@github.com:EricForgy/MyPrivateRepo.jl. It would be more than a
> little
> > annoying if I have to change every one to https. Hopefully, Pkg can do
> some
> > magic and make the changes for me if needed.
>
RE: [julia-users] Cloning private package with 0.5
Yes, I would hope that this is a release blocker issue, given that private package repos have been supported forever. I also have a very large number of private repos. So right now there seems no way to use them on 0.5 from Windows... I also would prefer to use SSH keys for authentication. If it does have to be https, I guess it would be ok if things are integrated with the git credential storage infrastructure. What would really be sort of a disaster is if I was asked for a username and password every time I do an Pkg.update() or something like that... > -Original Message- > From: julia-users@googlegroups.com [mailto:julia- > us...@googlegroups.com] On Behalf Of Eric Forgy > Sent: Friday, April 22, 2016 4:58 PM > To: julia-users <julia-users@googlegroups.com> > Subject: RE: [julia-users] Cloning private package with 0.5 > > I have the same problem (on Windows) and really hoping this gets fixed > before 0.5 is released. I have a ton of private repos. > > I'd prefer a solution that lets me keep my remotes at > g...@github.com:EricForgy/MyPrivateRepo.jl. It would be more than a little > annoying if I have to change every one to https. Hopefully, Pkg can do some > magic and make the changes for me if needed.
RE: [julia-users] Cloning private package with 0.5
I have the same problem (on Windows) and really hoping this gets fixed before 0.5 is released. I have a ton of private repos. I'd prefer a solution that lets me keep my remotes at g...@github.com:EricForgy/MyPrivateRepo.jl. It would be more than a little annoying if I have to change every one to https. Hopefully, Pkg can do some magic and make the changes for me if needed.
RE: [julia-users] Cloning private package with 0.5
Oh, and I'm on Windows. From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On Behalf Of David Anthoff Sent: Friday, April 22, 2016 3:35 PM To: julia-users@googlegroups.com Subject: [julia-users] Cloning private package with 0.5 I'm trying to clone a package that is hosted as a private package on bitbucket. I'm calling Pkg.clone(url), and have tried both the https and the ssh variant of the repo URL. Neither one works. When I use the SSH link I get an error "Unsupported URL protocol", when I use the https variant I get a prompt asking for the username, and once I've entered that, I get this error: ERROR: ccal: could not find function getpass Is there currently any way to clone private repos with julia 0.5? On julia 0.4 I can use the SSH URL without problems (my SSH keys are all set up properly). Thanks, David -- David Anthoff University of California, Berkeley http://www.david-anthoff.com
[julia-users] Cloning private package with 0.5
I'm trying to clone a package that is hosted as a private package on bitbucket. I'm calling Pkg.clone(url), and have tried both the https and the ssh variant of the repo URL. Neither one works. When I use the SSH link I get an error "Unsupported URL protocol", when I use the https variant I get a prompt asking for the username, and once I've entered that, I get this error: ERROR: ccal: could not find function getpass Is there currently any way to clone private repos with julia 0.5? On julia 0.4 I can use the SSH URL without problems (my SSH keys are all set up properly). Thanks, David -- David Anthoff University of California, Berkeley http://www.david-anthoff.com
