November 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Moving from mc to tonel?

by Julien

If you use Traits and want to have Epicea loadable from GitHub on Pharo 6.1, it will not work. There is an issue when you try to load a Trait in Tonel format in the image. --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille 1 http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > Le 6 nov. 2017 Ã 01:42, Martin Dias <tinchodias(a)gmail.com> a Ã©crit : > > Hi all, I'm considering to move Epicea (+Ombu+Hiedra) to github. I read that tonel is the new format and there is Peter's git-migration, which could be the tool to do it. > > Is it good idea to move now? > Is it the right tool? > > Bests, > MartÃn

Nov. 30, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Peter UhnÃ¡k

That sounds like a bug. Is the repo you are trying to migrate public? On Thu, Nov 30, 2017 at 6:01 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hi: > > 1. thanks for the tool and information. > 2. I forgot to tell you that I tried the tool some weeks ago and it ran > out of memory. I should try again with more memory or somehting different... > > Cheers, > Martin > > On Mon, Nov 6, 2017 at 5:49 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> Hi Martin, >> >> several people successfully migrated with git-migration... so I guess it >> works. >> >> > Is it good idea to move now? >> >> There is no risk in trying to use it. If it fails, you report a bug. :-) >> >> Is it the right tool? >> >> Yes. >> >> As for Tonel... git-migration uses FileTree, but I am looking into making >> it configurable. >> >> (I have filetree-tonel migration tool now... but that is a bit more >> hardcore and potentially destructive :) (unlike git-migration)). >> >> Cheers, >> Peter >> >> >> >> >> >> On Mon, Nov 6, 2017 at 1:42 AM, Martin Dias <tinchodias(a)gmail.com> wrote: >> >>> Hi all, I'm considering to move Epicea (+Ombu+Hiedra) to github. I read >>> that tonel is the new format and there is Peter's git-migration, which >>> could be the tool to do it. >>> >>> Is it good idea to move now? >>> Is it the right tool? >>> >>> Bests, >>> MartÃn >>> >> >> >

Nov. 30, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Martin Dias

Hi: 1. thanks for the tool and information. 2. I forgot to tell you that I tried the tool some weeks ago and it ran out of memory. I should try again with more memory or somehting different... Cheers, Martin On Mon, Nov 6, 2017 at 5:49 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi Martin, > > several people successfully migrated with git-migration... so I guess it > works. > > > Is it good idea to move now? > > There is no risk in trying to use it. If it fails, you report a bug. :-) > > Is it the right tool? > > Yes. > > As for Tonel... git-migration uses FileTree, but I am looking into making > it configurable. > > (I have filetree-tonel migration tool now... but that is a bit more > hardcore and potentially destructive :) (unlike git-migration)). > > Cheers, > Peter > > > > > > On Mon, Nov 6, 2017 at 1:42 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > >> Hi all, I'm considering to move Epicea (+Ombu+Hiedra) to github. I read >> that tonel is the new format and there is Peter's git-migration, which >> could be the tool to do it. >> >> Is it good idea to move now? >> Is it the right tool? >> >> Bests, >> MartÃn >> > >

Nov. 30, 2017

[Pharo 7.0-dev] Build #353: 20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #353 was: FAILURE. The Pull Request #564 was integrated: "20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages" Pull request url: https://github.com/pharo-project/pharo/pull/564 Issue Url: https://pharo.fogbugz.com/f/cases/20786 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 30, 2017

[Pharo 7.0-dev] Build #352: 20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #352 was: FAILURE. The Pull Request #564 was integrated: "20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages" Pull request url: https://github.com/pharo-project/pharo/pull/564 Issue Url: https://pharo.fogbugz.com/f/cases/20786 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 30, 2017

[Pharo 7.0-dev] Build #351: FAILURE

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #351 was: FAILURE. Could not extract further issue information from commit message: use new files.pharo.org (OVH) credentials Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 30, 2017

Re: [Pharo-dev] I love the launcher!!!!

by Norbert Hartl

Maybe we should make the pharo launcher move to opensuse build service as the vm did. This way it would be under the same umbrella and available for the main linux distributions Norbert > Am 30.11.2017 um 12:27 schrieb Christophe Demarey <christophe.demarey(a)inria.fr>: > > Hi Eduardo, > > Sadly, as far as I know, PPA are outdated, at least for pharo-launcher. > Thatâs why it does not work. You have an old version using an old VM unable to open recent images. > you should use http://files.pharo.org/platform/launcher/Pharo-linux-1.0.1.zip for now. > > Christophe > >> Le 30 nov. 2017 Ã 00:25, Eduardo de Oliveira Padoan <eduardo.padoan(a)gmail.com> a Ã©crit : >> >> I liked the launcher a lot, but It took me a while to get a version working out-of-the-box on Ubuntu. >> >> It's not available with the VM on the /download page for Linux. My preferred choice would be the PPA anyway, as I like to keep stuff under APT control, but I had to dig a lot to find a sources.list entry combination that worked: not all packages are available on all repositories, and some old repos have invalid crypto signatures. In the end, what worked was: >> >> - Xenial AND Trusty >> deb http://ppa.launchpad.net/pharo/stable/ubuntu xenial main >> deb http://ppa.launchpad.net/pharo/stable/ubuntu trusty main >> deb-src http://ppa.launchpad.net/pharo/stable/ubuntu xenial main >> deb-src http://ppa.launchpad.net/pharo/stable/ubuntu trusty main >> >> - Disabled signatures checking (at my own risk): >> sudo apt -o Acquire::AllowInsecureRepositories=true \ >> -o Acquire::AllowDowngradeToInsecureRepositories=true \ >> update >> - Finally: >> sudo apt install pharo-vm-core pharo-launcher >> >> But if I try to load a Pharo 5.0 image (created from the launcher's list, marked as beta), I get this on the terminal: >> >> "This interpreter (vers. 6505) cannot read image file (vers. 6521)." >> >> Pharo 4.0 is the most recent on that list that works, at least that I could find -- there are too many branches under Pharo Jenkins for instance, and I couldn't find a suitable image there. >> >> >> Att, >> >>> On Wed, Nov 29, 2017 at 5:13 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>> demarey wrote >>> > Maybe it could be related to this bug: >>> > https://github.com/pharo-project/pharo-launcher/issues/52 >>> >>> It is a different bug in the same behavior. >>> >>> The easy workaround is to manually create a pharo.version file for the >>> offending image. >>> >>> As to the bugâ¦ >>> >>> The immediate problem turned out to be that I had a startup error in certain >>> images due to a startup script that only worked in more recent Pharo >>> versions. So, suggestion #1: check that pharo.version has actually been >>> created, and if not produce a better error message. Also, ideally there >>> should probably also be a timeout in determining the image version because >>> sometimes the process returns without creating the file and other times it >>> doesn't return at all. >>> >>> However, even after disabling the startup scripts, I was only able to >>> generate pharo.version by replacing >>> "~/Documents/Pharo/vms/private/6505/Pharo.app" with >>> "~/Documents/Pharo/vms/30-x86/Pharo.app", so there does also seem to be >>> something fishy with the 6505 VM >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >>> >

Nov. 30, 2017

Re: [Pharo-dev] I love the launcher!!!!

by Christophe Demarey

Hi Eduardo, Sadly, as far as I know, PPA are outdated, at least for pharo-launcher. Thatâs why it does not work. You have an old version using an old VM unable to open recent images. you should use http://files.pharo.org/platform/launcher/Pharo-linux-1.0.1.zip <http://files.pharo.org/platform/launcher/Pharo-linux-1.0.1.zip> for now. Christophe > Le 30 nov. 2017 Ã 00:25, Eduardo de Oliveira Padoan <eduardo.padoan(a)gmail.com> a Ã©crit : > > I liked the launcher a lot, but It took me a while to get a version working out-of-the-box on Ubuntu. > > It's not available with the VM on the /download page for Linux. My preferred choice would be the PPA anyway, as I like to keep stuff under APT control, but I had to dig a lot to find a sources.list entry combination that worked: not all packages are available on all repositories, and some old repos have invalid crypto signatures. In the end, what worked was: > > - Xenial AND Trusty > deb http://ppa.launchpad.net/pharo/stable/ubuntu <http://ppa.launchpad.net/pharo/stable/ubuntu> xenial main > deb http://ppa.launchpad.net/pharo/stable/ubuntu <http://ppa.launchpad.net/pharo/stable/ubuntu> trusty main > deb-src http://ppa.launchpad.net/pharo/stable/ubuntu <http://ppa.launchpad.net/pharo/stable/ubuntu> xenial main > deb-src http://ppa.launchpad.net/pharo/stable/ubuntu <http://ppa.launchpad.net/pharo/stable/ubuntu> trusty main > > - Disabled signatures checking (at my own risk): > sudo apt -o Acquire::AllowInsecureRepositories=true \ > -o Acquire::AllowDowngradeToInsecureRepositories=true \ > update > - Finally: > sudo apt install pharo-vm-core pharo-launcher > > But if I try to load a Pharo 5.0 image (created from the launcher's list, marked as beta), I get this on the terminal: > > "This interpreter (vers. 6505) cannot read image file (vers. 6521)." > > Pharo 4.0 is the most recent on that list that works, at least that I could find -- there are too many branches under Pharo Jenkins for instance, and I couldn't find a suitable image there. > > > Att, > > On Wed, Nov 29, 2017 at 5:13 PM Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: > demarey wrote > > Maybe it could be related to this bug: > > https://github.com/pharo-project/pharo-launcher/issues/52 <https://github.com/pharo-project/pharo-launcher/issues/52> > > It is a different bug in the same behavior. > > The easy workaround is to manually create a pharo.version file for the > offending image. > > As to the bugâ¦ > > The immediate problem turned out to be that I had a startup error in certain > images due to a startup script that only worked in more recent Pharo > versions. So, suggestion #1: check that pharo.version has actually been > created, and if not produce a better error message. Also, ideally there > should probably also be a timeout in determining the image version because > sometimes the process returns without creating the file and other times it > doesn't return at all. > > However, even after disabling the startup scripts, I was only able to > generate pharo.version by replacing > "~/Documents/Pharo/vms/private/6505/Pharo.app" with > "~/Documents/Pharo/vms/30-x86/Pharo.app", so there does also seem to be > something fishy with the 6505 VM > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> >

Nov. 30, 2017

Re: [Pharo-dev] [ANN] files.pharo.org server move tomorrow, Nov 30

by Marcus Denker

Ok, it seems that was temporary. > On 30 Nov 2017, at 11:53, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > And now we have the problem that the hosting backend stopped working > > Error 503: Backend unavailable > > We are checking what the reason is. > >> On 30 Nov 2017, at 11:34, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Ok, and the last one: >> >> http://udpates.pharo.org >> >> The next step is to fix all the uploaders. >> >> This is, I think: >> >> -> Pharo6 build >> >> updates: >> https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-4-Release/configure >> images: >> https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-5-Publish/ >> >> -> Pharo7 build >> -> Pharo VM >> -> get script update / get-files >> -> Book Website >> -> Mooc Website/Videos/PDF >> >> >>> On 30 Nov 2017, at 11:25, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> >>> >>>> On 30 Nov 2017, at 10:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>> >>>> â¦ report: >>>> >>>> Move done: >>>> >>>> >>>> http://books.pharo.org >>>> http://lectures.pharo.org >>>> http://mooc.pharo.org >>>> >>>> https certificates are in creation, too. >>>> >>>> Ongoing: >>>> >>>> get >>>> files >>>> updates >>>> >>>> get: here the problem is that the files get-files on files.pharo.org uses lots of symbolic links, but >>>> with full path (which is different on the new server). >>>> >>>> We are now fixing these links once, then the script that creates them need to be updated >>>> >>> >>> Done. Now moved: >>> >>> http://files.pharo.org >>> http://get.pharo.org >>> >>> >>> Marcus >> > >

Nov. 30, 2017

Re: [Pharo-dev] [ANN] files.pharo.org server move tomorrow, Nov 30

by Marcus Denker

And now we have the problem that the hosting backend stopped working Error 503: Backend unavailable We are checking what the reason is. > On 30 Nov 2017, at 11:34, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Ok, and the last one: > > http://udpates.pharo.org > > The next step is to fix all the uploaders. > > This is, I think: > > -> Pharo6 build > > updates: > https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-4-Release/configure > images: > https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-5-Publish/ > > -> Pharo7 build > -> Pharo VM > -> get script update / get-files > -> Book Website > -> Mooc Website/Videos/PDF > > >> On 30 Nov 2017, at 11:25, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >> >>> On 30 Nov 2017, at 10:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> â¦ report: >>> >>> Move done: >>> >>> >>> http://books.pharo.org >>> http://lectures.pharo.org >>> http://mooc.pharo.org >>> >>> https certificates are in creation, too. >>> >>> Ongoing: >>> >>> get >>> files >>> updates >>> >>> get: here the problem is that the files get-files on files.pharo.org uses lots of symbolic links, but >>> with full path (which is different on the new server). >>> >>> We are now fixing these links once, then the script that creates them need to be updated >>> >> >> Done. Now moved: >> >> http://files.pharo.org >> http://get.pharo.org >> >> >> Marcus >

Nov. 30, 2017