You need to configure Iceberg with the path of the SSH key files you are using to authenticate with gitlab as well as the passphrase to unlock the private key, I only got it working after that. Have your done that? There is more information in the README/FAQ here: https://github.com/pharo-vcs/iceberg Cheers, Paulo On 11/08/2017 12:26 AM, Tim Mackinnon wrote:
Thanks for confirming this Esteban - perhaps I am doing something wrong - I tried using the steps I was using successfully several months ago namely:
curl get.pharo.org/64/ <http://get.pharo.org/64/> | bash ./pharo-ui Pharo.image
Which got me the latest image - which sys info says is (not sure why it still says 6.0 tho?):
Pharo 6.0 Latest update: #60520
I then open Iceberg, and click on Clone Repository
In the dialog I enter:
git@gitlab.com <mailto:git@gitlab.com>:macta/PharoLambda.git And put src in the code subdirectory field, and then click on Create.
I get the LGit_GIT_ERROR ???
Hmm, out of curiosity, I just tried leaving the src field empty and it then seemed to put an entry into Iceberg but then a Fetch gave me the same error?
Tim
On 7 Nov 2017, at 11:46, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote:
iceberg should work on 64bits, both on Pharo7 and Pharo6. Iâve been using it exclusively on 64bits since some months now and I know Iâm not the only one⦠can you send a way to reproduce your problem so I can take a look?
Esteban
On 6 Nov 2017, at 12:11, Tim Mackinnon <tim@testit.works <mailto:tim@testit.works>> wrote:
Hi - does Iceberg work on a 64bit image yet? Iâve not tried in a while, and was surprised when I went to get a new image via the command line that I am getting the error:Â LGit_GIT_ERROR: Invalid version 0 on git_remote_callbacks
I can see a post by Alistair in Jun asking about this, and it seems 64bit hadnât been updated to work back then - but is this still true in Nov?
We seem very much in turmoil at the moment - and its unclear what should work and not work. Is there a stable platform? If 64 bit is only working for 7.x - should we remove it from 6.x so that people donât inadvertently try to use it?
Tim