2017-08-09 9:33 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
On 8 Aug 2017, at 23:47, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
Le 08/08/2017 à 23:40, Nicolai Hess a écrit :
Thanks for the info, cyril.
What do you use for the ssh username in pharo setting and what username did you use for creating the ssh-key ? I tried both, my github-email and my github-username, I didn't get it to work.
I did not use anything special. While creating the ssh key I used all the default options and in the setting I do not change the username (see joined screenshot).
This is the command I probably used since I followed github tutorial[1]:
ssh-keygen -t rsa -b 4096 -C "cyril.ferlicot@gmail.com"
[1] https://help.github.com/articles/connecting-to-github-with-ssh/
yes, the keys may be an issue, but the standard rsa generated key should work. We need to do a pass in security/credentials system (and probably a revamp of some parts), but I still didnât find the time. about the 255 limitation, if you execute this in command line:
git config --system core.longpaths true
it should also fix the problem with pharo repo.
Esteban
Now I have the same problem. I can not get the pharo repo because it can not operate on files with long path names. even with longpaths true, this does not work ...
-- Cyril Ferlicot https://ferlicot.fr
http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France <PharoScreenshot.png>