Some issues with Pharo and Ubuntu
Locked
Some issues with Pharo and Ubuntu
 
|
Hello, I am trying Pharo with Docker and I will leave here some issues I had since I am unsure where I should report them. The command I am running is: Metacello new baseline: 'Employees';
repository: 'tonel:///home/employeesSource/pharo/';
ignoreImage;
onConflict: [ :ex | ex useIncoming ];
onWarning: [ :ex | Transcript crShow: ex ];
silently;
load: #(core).Ubuntu 16.04, Pharo 61 64bits -> Ok Ubuntu 16.04, Pharo 70 64bits -> Fail Loaded -> Seaside-Widgets-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache Loaded -> Seaside-RenderLoop-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache Loaded -> Seaside-Tools-Core-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache Please use #base64Decoded now. See issue #21937a MetacelloScriptApiExecutored from ThemeIcons>>#seasideAdaptorRunningIcon has been deprecated. Ubuntu 18.04, Pharo 61|Pharo 70 64bits -> Fail Seems like libgit is not found and it try to use one internal, but the link is broken. Fetched -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo Loaded -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo Loading baseline of BaselineOfEmployees...ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): libcurl-gnutls.so.4: cannot open shared object file: No such file or directory ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): libcurl-gnutls.so.4: cannot open shared object file: No such file or directory tryLoading(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/,libgit2.so): stat(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/) Not a directory [31mError: External module not found [0mExternalLibraryFunction(Object)>>error: ExternalLibraryFunction(Object)>>externalCallFailed ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: LGitLibrary>>libgit2_init FFICalloutAPI>>function:module: LGitLibrary(Object)>>ffiCall: LGitLibrary>>libgit2_init LGitLibrary>>initializeLibGit2 LGitGlobal class>>checkInitialized Regards, Vitor |
Re: Some issues with Pharo and Ubuntu
|
|
To load the latest Seaside in Pharo 7 I use the develop branch:
Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:develop/repository'; load. > On 17 Dec 2018, at 16:36, Vitor Medina Cruz <[hidden email]> wrote: > > Hello, > > I am trying Pharo with Docker and I will leave here some issues I had since I am unsure where I should report them. The command I am running is: > > Metacello new baseline: 'Employees'; > repository: 'tonel:///home/employeesSource/pharo/'; > ignoreImage; > onConflict: [ :ex | ex useIncoming ]; > onWarning: [ :ex | Transcript crShow: ex ]; > silently; > load: #(core). > > > Ubuntu 16.04, Pharo 61 64bits -> Ok > > Ubuntu 16.04, Pharo 70 64bits -> Fail > > Loaded -> Seaside-Widgets-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] > --- cache > Loaded -> Seaside-RenderLoop-CompatibleUserName.1544645021 --- > https://github.com/SeasideSt/Seaside.git[v3.2.5] > --- cache > Loaded -> Seaside-Tools-Core-CompatibleUserName.1544645021 --- > https://github.com/SeasideSt/Seaside.git[v3.2.5] > --- cache > Please use #base64Decoded now. See issue #21937a MetacelloScriptApiExecutored from ThemeIcons>>#seasideAdaptorRunningIcon has been deprecated. > > > Ubuntu 18.04, Pharo 61|Pharo 70 64bits -> Fail > > Seems like libgit is not found and it try to use one internal, but the link is broken. > > Fetched -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo > Loaded -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo > Loading baseline of BaselineOfEmployees...ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): > libcurl-gnutls.so.4: cannot open shared object file: No such file or directory > ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): > libcurl-gnutls.so.4: cannot open shared object file: No such file or directory > tryLoading(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/ > libgit2.so/.libs/,libgit2.so): stat(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/ > ) Not a directory > [31mError: External module not found > [0mExternalLibraryFunction(Object)>>error: > ExternalLibraryFunction(Object)>>externalCallFailed > ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: > LGitLibrary>>libgit2_init > FFICalloutAPI>>function:module: > LGitLibrary(Object)>>ffiCall: > LGitLibrary>>libgit2_init > LGitLibrary>>initializeLibGit2 > LGitGlobal class>>checkInitialized > > > > Regards, > Vitor |
Re: Some issues with Pharo and Ubuntu
|
|
In reply to this post by Vitor Medina Cruz
Hi, On Mon, Dec 17, 2018 at 4:38 PM Vitor Medina Cruz <[hidden email]> wrote:
http://bugs.pharo.org should be the correct place.
It looks like ubuntu 18.04 does not come with libcurl or they have renamed the package. Looks also that we are not the only ones that got bit by this: https://github.com/atom/github/issues/1680 Could you try installing curl in your system? Tx, Guille |
Re: Some issues with Pharo and Ubuntu
|
|
Oh well, I was focusing on the libgir stat thing, but it appears to be a problem with libcurl as you said... But it don't seems to be solved soon: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754686 and https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294 I will stay with ubuntu 16 for now. To load the latest Seaside in Pharo 7 I use the develop branch: I don't want to do that as it will make my build non repeatable. It is fine to load in an image to test, but it can create a number of problems if used into a dependency configuration. Regards, Vitor On Tue, Dec 18, 2018 at 7:39 AM Guillermo Polito <[hidden email]> wrote:
|
Re: Some issues with Pharo and Ubuntu
|
|
I searched a little bit and it seems there will be no action, and the same problem happened with minidebian, I expect that this will start to happen more as new updates of different linux distros are released with libcurl4. Older software depending on libcurl3 are broking and those who still have maintanace are switching to libcrul4 as well. I think sooner or later pharo will have to migrate as well... On Tue, Dec 18, 2018 at 10:41 AM Vitor Medina Cruz <[hidden email]> wrote:
|
«
Return to Pharo Smalltalk Users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |