February 2019 - Pharo-users

Re: [Pharo-users] Running test

by Hilaire

What is Smalltalk CI? Related to Chistophe? Thanks Le 07/02/2019 Ã 12:05, Tim Mackinnon a Ã©critÂ : > I think this is where having a build pipeline might be worth investigating - I think Smalltalk CI might let you automatically build on different machines, such that you can package each build on its native environment in an automated fashion. Maybe Christophe might chip in about how he builds Pharo Launcher? If you can make it automated and based on your git repo - it should simplify a lot for you, and make reliable builds much easier. (If not Smalltalk CI, then there might be others you can use) > > Tim -- Dr. Geo http://drgeo.eu

Feb. 7, 2019

Re: [Pharo-users] Running test

by Tim Mackinnon

> On 7 Feb 2019, at 11:15, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > To sign an app you need to use MacOS as you need some xcode tool from what I remember. Its worth checking with Christophe, as he may have automated this (there are tools that can do it - I recall). If Smalltalk CI canât do it - then something like DrGeo might benefit from something like: https://azure.microsoft.com/en-gb/services/devops/pipelines/?&OCID=AID73675… <https://azure.microsoft.com/en-gb/services/devops/pipelines/?&OCID=AID73675…> Free for open source - does linux, windows, osx build pipelines - presumably you can automate this once and for all and save yourself some of this hassle. It seems to suck a lot of your time from the fun stuff otherwise. Tim

Feb. 7, 2019

Re: [Pharo-users] Running test

by Andrei Chis

I tried the following: - download DrGeo.app-19.03a.zip <https://www.dropbox.com/s/z2acnw1yi77q4ps/DrGeo.app-19.03a.zip?dl=0> from the web browser, place it in Application and remove _CodeSignature; then it still appears as broken. - download DrGeo.app-19.03a.zip <https://www.dropbox.com/s/z2acnw1yi77q4ps/DrGeo.app-19.03a.zip?dl=0> using wget, place it in Applications and remove _CodeSignature: then it opens and asks for an image. But if I open it I get an error related to libgit. [image: Screen Shot 2019-02-07 at 12.09.21.png] For DrGeo.app-18.06a.zip <https://launchpad.net/drgeo/trunk/18.06/+download/DrGeo.app-18.06a.zip> I get the warning that it is from an unidentified developer but it works fine if I place it in the application folder. To sign an app you need to use MacOS as you need some xcode tool from what I remember. On Thu, Feb 7, 2019 at 11:06 AM Hilaire <hilaire(a)drgeo.eu> wrote: > Ok, one more thing that could be helpful to try and to give me > indication: remove the folder DrGeo.app/Contents/_CodeSignature and > start again DrGeo.app from the Application folder. > > What OS X says? > > Thanks > > Le 06/02/2019 Ã 22:02, john pfersich a Ã©crit : > > Yes before I tried to start it. > > > -- > Dr. Geo > http://drgeo.eu > > > >

Feb. 7, 2019

Re: [Pharo-users] Running test

by Tim Mackinnon

I think this is where having a build pipeline might be worth investigating - I think Smalltalk CI might let you automatically build on different machines, such that you can package each build on its native environment in an automated fashion. Maybe Christophe might chip in about how he builds Pharo Launcher? If you can make it automated and based on your git repo - it should simplify a lot for you, and make reliable builds much easier. (If not Smalltalk CI, then there might be others you can use) Tim > On 7 Feb 2019, at 09:40, Hilaire <hilaire(a)drgeo.eu> wrote: > > Can signing the bundle content be done from Linux? Or is it mandatory to > do it from OS X? > > From what I looked at the Linux Pharo Launcher, I can only fetch image > and associated VM for Linux but I may have miss something. > > Hilaire > > > Le 06/02/2019 Ã 21:41, Tim Mackinnon a Ã©crit : >> For OS X (and possibly Windows) itâs worth understanding how Pharo >> Launcher creates its installation program as thatâs the way to solve >> this properly and it makes it look much more polished as well. >> >> I think itâs not too hard too do, and you can copy those steps? >> > -- > Dr. Geo > http://drgeo.eu > > >

Feb. 7, 2019

Re: [Pharo-users] Running test

by Hilaire

Ok, one more thing that could be helpful to try and to give me indication: remove the folder DrGeo.app/Contents/_CodeSignature and start again DrGeo.app from the Application folder. What OS X says? Thanks Le 06/02/2019 Ã 22:02, john pfersich a Ã©critÂ : > Yes before I tried to start it.Â > -- Dr. Geo http://drgeo.eu

Feb. 7, 2019

Re: [Pharo-users] Running test

by Hilaire

...then look at how signing the functionnal bundle. The 18.06 bundle[1] is not signed and from feedback I got it can start once dragged in the Application folder. [1] https://launchpad.net/drgeo/trunk/18.06/+download/DrGeo.app-18.06a.zip -- Dr. Geo http://drgeo.eu

Feb. 7, 2019

Re: [Pharo-users] Running test

by Hilaire

I get another different feedback, while not good, it exposes a plugin error. https://twitter.com/gl_4/status/1093004875733106688 First should be to get a starting app with signature warning, then Le 06/02/2019 Ã 22:02, john pfersich a Ã©critÂ : > Yes before I tried to start it.Â > -- Dr. Geo http://drgeo.eu

Feb. 7, 2019

Re: [Pharo-users] Running test

by Hilaire

Can signing the bundle content be done from Linux? Or is it mandatory to do it from OS X? >From what I looked at the Linux Pharo Launcher, I can only fetch image and associated VM for Linux but I may have miss something. Hilaire Le 06/02/2019 Ã 21:41, Tim Mackinnon a Ã©critÂ : > For OS X (and possibly Windows) itâs worth understanding how Pharo > Launcher creates its installation program as thatâs the way to solve > this properly and it makes it look much more polished as well. > > I think itâs not too hard too do, and you can copy those steps? > -- Dr. Geo http://drgeo.eu

Feb. 7, 2019

Re: [Pharo-users] Why DirectoryIsNotEmpty on FileReference>>deleteAll ?

by Albrecht Baur

it is not urgent for me - I have a workaround. So for me it can wait until the next stable is released. Albrecht On 07.02.19 09:58, Alistair Grant wrote: > Hi Esteban, > > On Thu, 7 Feb 2019 at 09:41, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Means we will need a new stable for Pharo 7/8 ? >> >> Esteban > Albrecht will obviously be the one to say how urgent it is for him, or > whether he can get by with vmLatest80. From my perspective: the issue > has been there "forever" (2010 or earlier) and has only just been > reported. I expect that we'll eventually update the Pharo 7 VM > anyway, and this can probably wait until then. Pharo 8 can wait as > well, for the same reasons. > > Cheers, > Alistair > > > >>> On 7 Feb 2019, at 09:23, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> >>> On Thu, 7 Feb 2019 at 09:08, Albrecht Baur <baur.albrecht(a)googlemail.com> wrote: >>>> Hi Alistair, >>>> >>>> I have tested it and works with the latest VM. >>> Great, thanks for the confirmation. >>> >>> Cheers, >>> Alistair >>> >>> >>> >>>> thanks, >>>> >>>> Albrecht >>>> >>>> On 07.02.19 07:56, Alistair Grant wrote: >>>>> Hi Albrecht, >>>>> >>>>> On Wed, 6 Feb 2019 at 19:51, Albrecht Baur via Pharo-users >>>>> <pharo-users(a)lists.pharo.org> wrote: >>>>>> thank you! That is good news. >>>>>> >>>>>> best, >>>>>> >>>>>> Albrecht >>>>> Would you please download the latest VM and confirm that it resolves the issue: >>>>> >>>>> curl get.pharo.org/64/vmLatest80 | bash >>>>> >>>>> The Pharo 8 VM works with Pharo 7 images. >>>>> >>>>> Thanks, >>>>> Alistair >>>>> >>>>> >>>>>> On 06.02.19 09:34, Alistair Grant wrote: >>>>>>> Hi Albrecht, >>>>>>> >>>>>>> On Tue, 5 Feb 2019 at 15:26, Albrecht Baur <baur.albrecht(a)googlemail.com> wrote: >>>>>>>> Hi Alistair, >>>>>>>> >>>>>>>> here the system report output: >>>>>>>> >>>>>>>> ... >>>>>>> Thanks for the info. Please see: >>>>>>> >>>>>>> Issue: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/368 >>>>>>> PR: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/371 >>>>>>> >>>>>>> Assuming the CI build passes, I'll wait a day or so to give the VM >>>>>>> guys a chance to review the changes and comment before merging. >>>>>>> >>>>>>> Cheers, >>>>>>> Alistair >>>>>>> >>

Feb. 7, 2019

Re: [Pharo-users] Why DirectoryIsNotEmpty on FileReference>>deleteAll ?

by Alistair Grant

Hi Esteban, On Thu, 7 Feb 2019 at 09:41, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Means we will need a new stable for Pharo 7/8 ? > > Esteban Albrecht will obviously be the one to say how urgent it is for him, or whether he can get by with vmLatest80. From my perspective: the issue has been there "forever" (2010 or earlier) and has only just been reported. I expect that we'll eventually update the Pharo 7 VM anyway, and this can probably wait until then. Pharo 8 can wait as well, for the same reasons. Cheers, Alistair > > On 7 Feb 2019, at 09:23, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > On Thu, 7 Feb 2019 at 09:08, Albrecht Baur <baur.albrecht(a)googlemail.com> wrote: > >> > >> Hi Alistair, > >> > >> I have tested it and works with the latest VM. > > > > Great, thanks for the confirmation. > > > > Cheers, > > Alistair > > > > > > > >> thanks, > >> > >> Albrecht > >> > >> On 07.02.19 07:56, Alistair Grant wrote: > >>> Hi Albrecht, > >>> > >>> On Wed, 6 Feb 2019 at 19:51, Albrecht Baur via Pharo-users > >>> <pharo-users(a)lists.pharo.org> wrote: > >>>> thank you! That is good news. > >>>> > >>>> best, > >>>> > >>>> Albrecht > >>> Would you please download the latest VM and confirm that it resolves the issue: > >>> > >>> curl get.pharo.org/64/vmLatest80 | bash > >>> > >>> The Pharo 8 VM works with Pharo 7 images. > >>> > >>> Thanks, > >>> Alistair > >>> > >>> > >>>> On 06.02.19 09:34, Alistair Grant wrote: > >>>>> Hi Albrecht, > >>>>> > >>>>> On Tue, 5 Feb 2019 at 15:26, Albrecht Baur <baur.albrecht(a)googlemail.com> wrote: > >>>>>> Hi Alistair, > >>>>>> > >>>>>> here the system report output: > >>>>>> > >>>>>> ... > >>>>> Thanks for the info. Please see: > >>>>> > >>>>> Issue: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/368 > >>>>> PR: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/371 > >>>>> > >>>>> Assuming the CI build passes, I'll wait a day or so to give the VM > >>>>> guys a chance to review the changes and comment before merging. > >>>>> > >>>>> Cheers, > >>>>> Alistair > >>>>> > > > >

Feb. 7, 2019