- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Conflict merging resolution is a bit doomed :)

by StÃ©phane Ducasse

Imagine that you have a conflict because a method changed in the image and that the resolution is please keep the version that was in the slice, then you republish a slice with the same method and when the integrator will do merge he will get again: there is a conflict with the different version that it is the image. So from a person performing a fix there is no way that I can produce a slice that does not produce a conflict. > I don't understand. If you merge and recommit it is fine, since the new slice will have different ancestors the 3-way merge won't complain a second time, no? > > On 2013-06-25, at 11:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> I do not know how I can republish a Slice when there is a conflict. Especially when I merged and say that I want to keep the change I did. So we are in the deadlock. There is no way for the fix producers to indicate that >> he merged and that his changes should be keep. >> >> So from a bug integration process this is not really good. >> >> Stef > >

June 25, 2013

Re: [Pharo-dev] [update 3.0] #30221

by Andrei Vasile Chis

> Also it would be good to sync with the content from the Debugger >> repository as it contains some bug fixes. >> What can I do to make this easy or you? (I can merge the version from >> pharo with the one from the Debugger repository; >> should I also create a slice?) >> >> Yeah please merge it and make a slice and a bug report in fogbugz. It > will be integrated the day after you create the slice and put the bug in > bugtracker to status 'fix review needed'. > Will do it by tomorrow. > Andrei I have a question. On the old debugger when I right click on the > stack I have a lot of features (as return value, browse class, ..). On the > new debugger with Spec UI and your model I don't have all these features. > > Are they implemented in the model and not in the spec UI ? Are they not > implemented because no one requested :) ?Could you add them ? > They are not implemented because at beginning I didn't needed them :). They will be added soon (https://pharo.fogbugz.com/default.asp?10952) Also I've created some more issues with the things that should be done in order for the new debugger to be ready for integration. I'd be online Friday afternoon during the sprint working on those issues. Andrei

June 25, 2013

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

by Pablo R. Digonzelli

+1 Ing. Pablo Digonzelli Sofware Solutions IP Soluciones SRL 25 de Mayo 521. Entrepiso A email: pdigonzelli(a)softsargentina.com email: pdigonzelli(a)gmail.com twitter: @pdigonzelli Tel: 0381 4227378 Cel: 0381 155982714 ----- Mensaje original ----- De: "Damien Cassou" <damien.cassou(a)gmail.com> Para: "Pharo Development List" <pharo-dev(a)lists.pharo.org> Enviados: Martes, 25 de Junio 2013 11:32:06 Asunto: Re: [Pharo-dev] Pharo does not work on ubuntu 13.04 On Tue, Jun 25, 2013 at 4:17 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hmm, you also need libssl0.9.8 or libssl0.9.8:i386 for Pharo since it includes SSL/TLS/HTTPS support out of the box. > > Anyway, missing deps are easily found using ldd. what is the problem with you guys? I spent and continue to spend days on packaging Pharo for Ubuntu so that everyone can forget about dependencies and 32 vs. 64 issues. So why do you keep on talking about this complex and undocumented method of installing Pharo? Just execute what is documented on the pharo.org website and you are guaranteed to have the latest version of the VM working whatever your Ubuntu is (provided it is still supported by Canonical) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 25, 2013

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

by Camillo Bruni

fixed On 2013-06-25, at 17:16, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Comment aside, there is a #!/bin/bash # line at the top of the > http://get.pharo.org/ page, which is outside of the comment that > immediately follows it (between ). > > That bang line, plus -1em margin rule applied to the html body causes > a visual glitch at the top, that ruins a perfectly minimal page style > :) >

June 25, 2013

Re: [Pharo-dev] [update 3.0] #30221

by ClÃ©ment Bera

2013/6/25 Andrei Vasile Chis <chisvasileandrei(a)gmail.com> > > 10817 Spec inspector >> https://pharo.fogbugz.com/f/cases/10817/ >> >> WARNING: This change sets new debugger as default :) >> > > > Had a quick look and saw that the old debugger is still the default one. > Yeah that was a miscommunication between Camillo, Esteban and I. > > Also it would be good to sync with the content from the Debugger > repository as it contains some bug fixes. > What can I do to make this easy or you? (I can merge the version from > pharo with the one from the Debugger repository; > should I also create a slice?) > > Yeah please merge it and make a slice and a bug report in fogbugz. It will be integrated the day after you create the slice and put the bug in bugtracker to status 'fix review needed'. Andrei I have a question. On the old debugger when I right click on the stack I have a lot of features (as return value, browse class, ..). On the new debugger with Spec UI and your model I don't have all these features. Are they implemented in the model and not in the spec UI ? Are they not implemented because no one requested :) ?Could you add them ? Because we will put the new debugger by default in a few weeks (We first wait a few time to confirm that Opal and spec inspectors are stable enough to support the new debugger) and people will blame us if these features are not here. > Andrei > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

June 25, 2013

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

by Camillo Bruni

On 2013-06-25, at 17:16, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > Comment aside, there is a #!/bin/bash # line at the top of the > http://get.pharo.org/ page, which is outside of the comment that > immediately follows it (between ). the bang is on purpose, this is a "dual" html/bash file. when you do curl get.pharo.org | bash it is this very file that gets downloaded and executed ;) > That bang line, plus -1em margin rule applied to the html body causes > a visual glitch at the top, that ruins a perfectly minimal page style > :) I will adapt the CSS, I think I modified the line-spacing and overlooked that.

June 25, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 3 regressions found. KernelTests.Numbers.NumberTest.testUnCategorizedMethods Spec.Inspector.Test.EyeInspectorTest.testErrorRaised ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812

June 25, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 3 regressions found. KernelTests.Numbers.NumberTest.testUnCategorizedMethods Spec.Inspector.Test.EyeInspectorTest.testErrorRaised ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812

June 25, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 4 regressions found. KernelTests.Numbers.NumberTest.testUnCategorizedMethods Spec.Inspector.Test.EyeInspectorTest.testErrorRaised Tests.Release.ReleaseTest.testObsoleteClasses ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812

June 25, 2013

Re: [Pharo-dev] [update 3.0] #30221

by ClÃ©ment Bera

No actually we changed our mind and there is still the old debugger by default. But there is the new inspectors by default. The ObjectExplorer uses the new inspector instead of the old one, so it is kind of new too. I fixed the objectExplorer for compatibility with the new inspectors (in 30221 it does not work), so next integration should re-enable them. Actually in latest images you have Opal and the new inspectors by default. It *might* happen then that the latest Pharo 3 alpha is a *little bit* unstable in *very rare and specific* cases. 2013/6/25 Sven Van Caekenberghe <sven(a)stfx.eu> > > On 25 Jun 2013, at 15:30, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > 30221 > > ----- > > > > 10545 Delays do not work properly directly on image startup > > > https://pharo.fogbugz.com/f/cases/10545/Delays-do-not-work-properly-directl… > > Fingers crossed ;-) > > > 10817 Spec inspector > > https://pharo.fogbugz.com/f/cases/10817/ > > > > WARNING: This change sets new debugger as default :) > > Yeah, living on the edgeâ¦ > > > Diff information: > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-EstebanLorenzano.1152.d… > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Tools-EstebanLorenzano… > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-EstebanLorenza… > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-EstebanLorenza… > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-EstebanLorenzano… > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-EstebanLorenzan… > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/MonticelloGUI-EstebanLorenzan… > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-EstebanLorenzano.1495.… > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/AST-Interpreter-Core-EstebanL… > > > > > > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

June 25, 2013