On Fri, 7 Sep 2018 at 10:11, Andrei Stebakov wrote:
> I was trying debug it a little to see if how iceberg uses the path to
> private and public keys. When I mangle the path to something non-existent I
> got no error saying that the path is wrong. What would be a way to verify
> that iceberg actu
I was trying debug it a little to see if how iceberg uses the path to
private and public keys. When I mangle the path to something non-existant I
got no error saying that the path is wrong. What would be a way to verify
that iceberg actually uses the keys?
On Thu, Sep 6, 2018, 16:35 Peter Uhnak w
> I need to get past that error since I get it even when I install Moose
via Metacello.
Note that Moose depends on projects that are on github, so if it is
misconfigured, then it will fail.
Maybe you can provide both the ssh key and regular key/password? I use both
and so far I had no problems on
On Thu, 6 Sep 2018 at 21:58, Andrei Stebakov wrote:
> I followed the tutorial
>
Hi Andrei, Could you be specific about which tutorial that was. I'm not
sure if I'm just getting by on old knowledge
or the much improved Iceberg UI and its good to refresh myself with such
tutorials.
> and prov
Hi,
I do not have an easy answer for you.
No, you don’t need to install ssh-agent.
But then, I do not understand why you can’t connect, since others have not
reported this problem, I just can guess: is your key password protected?
Has you provided it?
Also, password protected keys has had pr
I followed the tutorial and provided IceCredentialProvider with ssh
settings, also put the same settings in Settings-Tools-Software
Configuration Management.
It seems not to have any effect since when I try to create a repo using SSH
it gives the error "Failed to connect to github.com".
I need to g
