LGit_GIT_ERROR: Invalid version 0 on git_remote_callbacks on latest 64bit 6.1 image?
Locked
LGit_GIT_ERROR: Invalid version 0 on git_remote_callbacks on latest 64bit 6.1 image?
 
|
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
|
|
|
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
|
Re: LGit_GIT_ERROR: Invalid version 0 on git_remote_callbacks on latest 64bit 6.1 image?
|
|
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/ | 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: [hidden email]: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
|
|
|
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: |
Re: LGit_GIT_ERROR: Invalid version 0 on git_remote_callbacks on latest 64bit 6.1 image?
|
|
On 8 November 2017 at 16:06, Paulo R. Dellani <[hidden email]> wrote:
> 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 Thanks for pointing this out. I had enough other fires that I'd given up on 64 bit, however it appears to be working now. I'll restart my efforts to move to 64 bit. Cheers, Alistair > 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/ | 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: > > [hidden email]: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 <[hidden email]> 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 <[hidden email]> 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 |
|
|
> On 12 Nov 2017, at 09:44, Alistair Grant <[hidden email]> wrote: > > On 8 November 2017 at 16:06, Paulo R. Dellani <[hidden email]> wrote: >> 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 > > Thanks for pointing this out. I had enough other fires that I'd given > up on 64 bit, however it appears to be working now. > > I'll restart my efforts to move to 64 bit. I found a but on 64bit 6.1 version. I will correct that, but in the mean time this is the workaround: LGitExternalStructure allSubclassesDo: #compileFields. Esteban > > Cheers, > Alistair > > > >> 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/ | 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: >> >> [hidden email]: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 <[hidden email]> 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 <[hidden email]> 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 > |
«
Return to Pharo Smalltalk Users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |