2017-08-08 23:00 GMT+02:00 Esteban Lorenzano <[hidden email]>:
Like I described above. I followed this howto ( the first mail from pavel). But I get this error: 'LGit_GIT_ERROR: Failed to authenticate SSH session: Callback returned error' Now I enabled the setting for "Use custom SSH keys", followed the github-doc for adding a ssh-key on windows and add this key to my github-account. But I still get the same error.
|
In reply to this post by CyrilFerlicot
2017-08-08 23:05 GMT+02:00 Cyril Ferlicot D. <[hidden email]>: Le 08/08/2017 à 20: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.
|
In reply to this post by Nicolai Hess-3-2
Le 08/08/2017 à 23:37, Nicolai Hess a écrit :
> > > Like I described above. > > I followed this howto ( the first mail from pavel). > > But I get this error: > > 'LGit_GIT_ERROR: Failed to authenticate SSH session: Callback returned > error' > > > Now I enabled the setting for "Use custom SSH keys", followed the > github-doc for adding a ssh-key on windows and add this key to my > github-account. > But I still get the same error. > > and to commit on a repository with a ssh remote. If it works you'll be sure the ssh key is good. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France signature.asc (836 bytes) Download Attachment |
In reply to this post by Nicolai Hess-3-2
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 "[hidden email]" [1] https://help.github.com/articles/connecting-to-github-with-ssh/ -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France |
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
|
On Wed, Aug 9, 2017 at 9:33 AM, Esteban Lorenzano <[hidden email]> wrote:
> > > 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 > I already did it but I still get the problem :( > it should also fix the problem with pharo repo. > > Esteban > > > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France |
In reply to this post by CyrilFerlicot
2017-08-08 23:41 GMT+02:00 Cyril Ferlicot D. <[hidden email]>: Le 08/08/2017 à 23:37, Nicolai Hess a écrit : yes, just tested, this seems to work. I can use the key for a ssh remote commit from the command line. but somehow I can not use it with pharo /iceberg..
|
2017-08-09 23:18 GMT+02:00 Nicolai Hess <[hidden email]>:
Ah, I think I got it to work now. I created a new ssh key, but this time I did not set a passphrase. So maybe, ssh remotes with iceberg are only working if you don't use passphrases for you secret key!
|
In reply to this post by EstebanLM
2017-08-09 9:33 GMT+02:00 Esteban Lorenzano <[hidden email]>:
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 ...
|
In reply to this post by Pavel Krivanek-3
> On 26. Jun 2017, at 19:14, Pavel Krivanek <[hidden email]> wrote: > > Hi, Hey! thank you for this HOWTO! > username := 'YOUR-USER-NAME'. > repository := IceRepositoryCreator new > url: '[hidden email]:pharo-project/pharo.git'; > location: ('pharo-core' asFileReference ensureCreateDirectory); > subdirectory:'src'; > createRepository. > repository checkoutBranch: 'development'. > repository register. > > fork := (IceRemote name: 'myFork' url: ('[hidden email]:{1}/pharo.git' format: {username})). > repository addRemote: fork. > repository pushRemote: fork. > repository pullRemote: repository origin. I am using "pharo-mac-stable.zip" and "Pharo-7.0.0-alpha.build.27.sha.c1c8991.arch.32bit.zip" and followed your howto and run into various Iceberg issues. Where would be the best place to report them? Open Iceberg, selech "Pharo", click on Branches => Error LGit_GIT_ERROR: Reference 'HEAD' is not a local branch. Open Iceberg, double click on "Pharo" => DNU, #/ was sent to nil UndefinedObject(Object)>>doesNotUnderstand: #/ ... IceSavedPackage repository location seems to return nil. Are these known? Fogbugz? Github issues of Iceberg? cheers holger |
2017-08-12 11:36 GMT+02:00 Holger Freyther <[hidden email]>:
yes, because this HOWTO is already obsolete. See: -- Pavel
|
> On 12. Aug 2017, at 17:47, Pavel Krivanek <[hidden email]> wrote: > > > yes, because this HOWTO is already obsolete. See: > > https://github.com/guillep/PharoIntegrationProcess/wiki/Pharo-Development-Process Ah okay. The hidden system repository explains why the IceSavedPackage didn't point to the repository I had created/set-up but to something without a location:. thank you holger |
In reply to this post by Pavel Krivanek-3
Why is that document in the account of guille?
|
Because he wrote it but indeed it should be migrated to Pharo.
On Thu, Aug 24, 2017 at 11:12 AM, Norbert Hartl <[hidden email]> wrote: > > Why is that document in the account of guille? > > Norbert > > Am 12.08.2017 um 11:47 schrieb Pavel Krivanek <[hidden email]>: > > > > 2017-08-12 11:36 GMT+02:00 Holger Freyther <[hidden email]>: >> >> >> > On 26. Jun 2017, at 19:14, Pavel Krivanek <[hidden email]> >> > wrote: >> > >> > Hi, >> >> Hey! >> >> thank you for this HOWTO! >> >> > username := 'YOUR-USER-NAME'. >> > repository := IceRepositoryCreator new >> > url: '[hidden email]:pharo-project/pharo.git'; >> > location: ('pharo-core' asFileReference ensureCreateDirectory); >> > subdirectory:'src'; >> > createRepository. >> > repository checkoutBranch: 'development'. >> > repository register. >> > >> > fork := (IceRemote name: 'myFork' url: ('[hidden email]:{1}/pharo.git' >> > format: {username})). >> > repository addRemote: fork. >> > repository pushRemote: fork. >> > repository pullRemote: repository origin. >> >> I am using "pharo-mac-stable.zip" and >> "Pharo-7.0.0-alpha.build.27.sha.c1c8991.arch.32bit.zip" and followed your >> howto and run into various Iceberg issues. Where would be the best place to >> report them? >> >> Open Iceberg, selech "Pharo", click on Branches >> => Error LGit_GIT_ERROR: Reference 'HEAD' is not a local branch. >> >> Open Iceberg, double click on "Pharo" >> => DNU, #/ was sent to nil >> UndefinedObject(Object)>>doesNotUnderstand: #/ >> ... IceSavedPackage repository location seems to return nil. >> >> >> Are these known? Fogbugz? Github issues of Iceberg? > > > yes, because this HOWTO is already obsolete. See: > > https://github.com/guillep/PharoIntegrationProcess/wiki/Pharo-Development-Process > > -- Pavel > >> >> >> >> cheers >> holger >> >> >> >> > |
Free forum by Nabble | Edit this page |