- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60009 Home: https://github.com/pharo-project/pharo-core

May 17, 2016

[pharo-project/pharo-core] 2c1c3f: 60009

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 2c1c3fbfb52006c6c1d6aadc6518a42230638777 https://github.com/pharo-project/pharo-core/commit/2c1c3fbfb52006c6c1d6aadc… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-17 (Tue, 17 May 2016) Changed paths: A Reflectivity-Tools.package/extension/CompiledMethod/instance/hasBreakpoint.st A Reflectivity-Tools.package/extension/RBProgramNode/instance/hasBreakpoint.st R Reflectivity.package/extension/CompiledMethod/instance/hasBreakpoint.st R Reflectivity.package/extension/RBProgramNode/instance/hasBreakpoint.st M ReleaseTests.package/ReleaseTest.class/instance/testing/testKeyClassesArePresentInStartupList.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60008.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60009.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60008.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60009.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60009 18191 remove FFI classes from ReleaseTest>>#testKeyClassesArePresentInStartupList https://pharo.fogbugz.com/f/cases/18191 18201 Reflectivity depends on Relfectivity-Tools https://pharo.fogbugz.com/f/cases/18201 http://files.pharo.org/image/60/60009.zip

May 17, 2016

Re: [Pharo-dev] PhD Thesis offer

by jannik laval

nop, I don't know these lists. Jannik 2016-05-15 22:49 GMT+02:00 stepharo <stepharo(a)free.fr>: > did you forward it to spanish speaking mailing lists? > > > Stef > > Le 4/5/16 Ã 12:37, jannik laval a Ã©crit : > > Dear friends, > > I am looking for a french student (or someone speaking french) who wants > to engage in a CIFRE PhD thesis (it is a thesis with a french company). > > The subject is attached to the mail. > > Best regards, > -- > ~~Jannik Laval~~ > Enseignant-chercheur > Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨me > d'Information > IUT LumiÃ¨re, UniversitÃ© Lyon LumiÃ¨re > laboratoire DISP > http://www.jannik-laval.eu > http://www.phratch.com > http://www.approchealpes.info > > > -- ~~Jannik Laval~~ Enseignant-chercheur Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨me d'Information IUT LumiÃ¨re, UniversitÃ© Lyon LumiÃ¨re laboratoire DISP http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

May 17, 2016

Re: [Pharo-dev] PharoVM-spur32 test newVMTestImage --> Pharo 2.0 ??

by Esteban Lorenzano

newVMtestImage is old, yes. we are not using it for now because Iâm running tests in github, before build it (but Iâm missing windows tests, a situation I will fix soon (â¢)) Esteban > On 17 May 2016, at 12:44, Ben Coman <btc(a)openinworld.com> wrote: > > In the PharoVM-spur32 CI build, newVMTestImage.sh [1] doesn't seem current? > >> wget http://files.pharo.org/vm/src/vm-test-image-20.zip 1>&2 >> unzip vm-test-image-20.zip -d vm-test-image 1>&2 >> >> wget http://files.pharo.org/sources/PharoV20.sources --output-document=vm-test-image/PharoV20.sources 1>&2 >> >> PHARO_IMAGE=`find vm-test-image -name \*.image` 1>&2 >> echo $PHARO_IMAGE > > cheers -ben > > [1] https://ci.inria.fr/pharo/job/PharoVM-spur32/Architecture=32,Slave=vm-build… >

May 17, 2016

PharoVM-spur32 test newVMTestImage --> Pharo 2.0 ??

by Ben Coman

In the PharoVM-spur32 CI build, newVMTestImage.sh [1] doesn't seem current? > wget http://files.pharo.org/vm/src/vm-test-image-20.zip 1>&2 > unzip vm-test-image-20.zip -d vm-test-image 1>&2 > > wget http://files.pharo.org/sources/PharoV20.sources --output-document=vm-test-image/PharoV20.sources 1>&2 > > PHARO_IMAGE=`find vm-test-image -name \*.image` 1>&2 > echo $PHARO_IMAGE cheers -ben [1] https://ci.inria.fr/pharo/job/PharoVM-spur32/Architecture=32,Slave=vm-build…

May 17, 2016

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

by Pavel Krivanek

I copied all current Pharo 6 packages to the Pharo60 and Pharo60Inbox repositories. It should solve at least part of the problems. -- Pavel 2016-05-17 11:08 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Copy slice from Monticello Browser also copies dependencies. > But now I always got merge conflicts from Monkey while no conflicts when I > merge it manually > > 2016-05-17 9:06 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > >> Yes, it is fragile. >> >> It's a bit like an application that saves a document as a couple of >> files. When you later copy only one file, you break the format. >> >> > On 17 May 2016, at 08:37, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> > >> > But how come saving a slice in the beginning also saves the dependents? >> I thought it acted like a package. >> > >> > Wouldn't this be a bug then? It is certainly bug-inducing. >> > >> > On Tue, May 17, 2016 at 8:12 AM, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >> > >> > > On 17 May 2016, at 08:01, ClÃ©ment Bera <bera.clement(a)gmail.com> >> wrote: >> > > >> > > Well I tried that and sometimes the integrator can't integrate >> because of a "Missing ancestor". >> > >> > You have to copy all dependents as well, a slice is just an empty >> holder. But I guess you already know. >> > >> > > I guess I will do what you say for my bugs and when the problem >> arises again I will ask again with a concrete example. >> > > >> > > Nvm >> > > >> > > On Mon, May 16, 2016 at 3:34 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> >> wrote: >> > > Is there a problem in simply adding Inbox50 repo and clicking on the >> "Copy" button to put it to Inbox60? Or am I missing something? >> > > >> > > Peter >> > > >> > > On Mon, May 16, 2016 at 2:12 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> >> wrote: >> > > Hello, >> > > >> > > I have a problem in several bugs I opened on the bug tracker. When I >> opened them, Pharo 6 development has not started, so the slices were >> committed in the Pharo 5 inbox. As Pharo 5 was in stabilization phasis for >> release, my slices were not integrated but postponed to Pharo 6 (which I >> understand and accept). But since now the development is in Pharo 6, the >> monkey checks the slice in Pharo 6 inbox and can't find my slices because >> they are in Pharo 5 inbox. See for example 18039 or 17451. >> > > >> > > What is the right way to move the slices from Pharo 5 inbox to Pharo >> 6 inbox ? I don't want to end up in a situation where it is not possible to >> integrate my slice because of a "Missing ancestor", so how can I move the >> slices from Pharo 5 inbox to Pharo 6 inbox without having that problem ? >> > > >> > > Thanks. >> > > >> > > >> > >> > >> > >> >> >> >

May 17, 2016

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

by Denis Kudriashov

Copy slice from Monticello Browser also copies dependencies. But now I always got merge conflicts from Monkey while no conflicts when I merge it manually 2016-05-17 9:06 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Yes, it is fragile. > > It's a bit like an application that saves a document as a couple of files. > When you later copy only one file, you break the format. > > > On 17 May 2016, at 08:37, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > But how come saving a slice in the beginning also saves the dependents? > I thought it acted like a package. > > > > Wouldn't this be a bug then? It is certainly bug-inducing. > > > > On Tue, May 17, 2016 at 8:12 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > > > > On 17 May 2016, at 08:01, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > > > > Well I tried that and sometimes the integrator can't integrate because > of a "Missing ancestor". > > > > You have to copy all dependents as well, a slice is just an empty > holder. But I guess you already know. > > > > > I guess I will do what you say for my bugs and when the problem arises > again I will ask again with a concrete example. > > > > > > Nvm > > > > > > On Mon, May 16, 2016 at 3:34 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> > wrote: > > > Is there a problem in simply adding Inbox50 repo and clicking on the > "Copy" button to put it to Inbox60? Or am I missing something? > > > > > > Peter > > > > > > On Mon, May 16, 2016 at 2:12 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> > wrote: > > > Hello, > > > > > > I have a problem in several bugs I opened on the bug tracker. When I > opened them, Pharo 6 development has not started, so the slices were > committed in the Pharo 5 inbox. As Pharo 5 was in stabilization phasis for > release, my slices were not integrated but postponed to Pharo 6 (which I > understand and accept). But since now the development is in Pharo 6, the > monkey checks the slice in Pharo 6 inbox and can't find my slices because > they are in Pharo 5 inbox. See for example 18039 or 17451. > > > > > > What is the right way to move the slices from Pharo 5 inbox to Pharo 6 > inbox ? I don't want to end up in a situation where it is not possible to > integrate my slice because of a "Missing ancestor", so how can I move the > slices from Pharo 5 inbox to Pharo 6 inbox without having that problem ? > > > > > > Thanks. > > > > > > > > > > > > > > >

May 17, 2016

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

by Max Leske

> On 17 May 2016, at 09:09, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 17 May 2016, at 06:48, Max Leske <maxleske(a)gmail.com> wrote: >> >>> >>> On 16 May 2016, at 22:49, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> >>> Hi, >>> >>> I'm attempting to upload a SLICE for issue 18248 to: >>> >>> MCHttpRepository >>> location: 'http://smalltalkhub.com/mc/Pharo/Pharo60Inbox/main' >>> user: '' >>> password: '' >>> >>> with username: Alistair >>> >>> following the instructions in the video at >>> https://www.youtube.com/watch?v=iFomI-7h4qQ (from the Contributing to >>> Pharo video at pharo.org) >>> >>> but am getting a Error 500 Internal Server Error response. >>> >>> I can log in to the smalltalkhub.com website without any problems, so I >>> believe my password is correct. >>> >>> Do I need to be granted write access? The Pharo60Inbox project doesn't >>> have the mailing list link at the bottom of the page anymore. >> >> No, itâs publicly writeable. You may have found a bug. Can you link to the .mcz youâre trying to upload? Then we can give it a try. > > Don't you have to be part of team Pharo ? Hmâ¦ then âpublicâ is certainly a misleading label... > >> Cheers, >> Max >> >>> >>> Thanks! >>> Alistair

May 17, 2016

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

by Sven Van Caekenberghe

> On 17 May 2016, at 06:48, Max Leske <maxleske(a)gmail.com> wrote: > >> >> On 16 May 2016, at 22:49, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi, >> >> I'm attempting to upload a SLICE for issue 18248 to: >> >> MCHttpRepository >> location: 'http://smalltalkhub.com/mc/Pharo/Pharo60Inbox/main' >> user: '' >> password: '' >> >> with username: Alistair >> >> following the instructions in the video at >> https://www.youtube.com/watch?v=iFomI-7h4qQ (from the Contributing to >> Pharo video at pharo.org) >> >> but am getting a Error 500 Internal Server Error response. >> >> I can log in to the smalltalkhub.com website without any problems, so I >> believe my password is correct. >> >> Do I need to be granted write access? The Pharo60Inbox project doesn't >> have the mailing list link at the bottom of the page anymore. > > No, itâs publicly writeable. You may have found a bug. Can you link to the .mcz youâre trying to upload? Then we can give it a try. Don't you have to be part of team Pharo ? > Cheers, > Max > >> >> Thanks! >> Alistair

May 17, 2016

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

by Sven Van Caekenberghe

Yes, it is fragile. It's a bit like an application that saves a document as a couple of files. When you later copy only one file, you break the format. > On 17 May 2016, at 08:37, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > But how come saving a slice in the beginning also saves the dependents? I thought it acted like a package. > > Wouldn't this be a bug then? It is certainly bug-inducing. > > On Tue, May 17, 2016 at 8:12 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 17 May 2016, at 08:01, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > > Well I tried that and sometimes the integrator can't integrate because of a "Missing ancestor". > > You have to copy all dependents as well, a slice is just an empty holder. But I guess you already know. > > > I guess I will do what you say for my bugs and when the problem arises again I will ask again with a concrete example. > > > > Nvm > > > > On Mon, May 16, 2016 at 3:34 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Is there a problem in simply adding Inbox50 repo and clicking on the "Copy" button to put it to Inbox60? Or am I missing something? > > > > Peter > > > > On Mon, May 16, 2016 at 2:12 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > Hello, > > > > I have a problem in several bugs I opened on the bug tracker. When I opened them, Pharo 6 development has not started, so the slices were committed in the Pharo 5 inbox. As Pharo 5 was in stabilization phasis for release, my slices were not integrated but postponed to Pharo 6 (which I understand and accept). But since now the development is in Pharo 6, the monkey checks the slice in Pharo 6 inbox and can't find my slices because they are in Pharo 5 inbox. See for example 18039 or 17451. > > > > What is the right way to move the slices from Pharo 5 inbox to Pharo 6 inbox ? I don't want to end up in a situation where it is not possible to integrate my slice because of a "Missing ancestor", so how can I move the slices from Pharo 5 inbox to Pharo 6 inbox without having that problem ? > > > > Thanks. > > > > > > >

May 17, 2016