- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PharoLauncher - upgrading to 1.6 on Windows

by Christophe Demarey

Hi Petr, Thanks for the feedback. I opened a bu entry for it: https://github.com/pharo-project/pharo-launcher/issues/310 I'm able to reproduce the problem. I need to investigate because it looks fine from what I see (see attached screenshots). Regards, Christophe > Le 12 fÃ©vr. 2019 Ã 08:17, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> a Ã©crit : > > > De: Petr Fischer <petr.fischer(a)me.com> > Objet: PharoLauncher - upgrading to 1.6 on Windows > Date: 12 fÃ©vrier 2019 08:17:30 UTC+1 > Ã: pharo-dev(a)lists.pharo.org > > > Hello. > > I thought I'd try PharoLauncher again after some time and I really have a bad luck with this product. > > I have a PharoLauncher version 1.5.1 installed. If I run new 1.6 installer, this error occurs: > > "A more recent version of PharoLauncher is already installed on this computer" > https://app.box.com/s/rbn1n12zvx5rvy4zb1s0fujhkbzwvone > > "More recent?..." Really? > > I uninstalled old version manually of course, but... PharoLauncher can't update itself? > > Platform: Windows 10 Pro [1809] > > pf > > >

Feb. 12, 2019

Re: [Pharo-dev] File problems in Pharo 8

by Cyril Ferlicot

On Tue, Feb 12, 2019 at 11:47 AM Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Cyril, > > In not at my PC at the moment, sorry. > > Can you try with vmLatest80? > > curl get.pharo.org/64/vmLatest80 | bash > > This looks like an issue I resolved recently. > I can commit with this vm. Thank you. I have the impression that the commit takes longer now but I don't have any bench. (maybe it's just my imagination). > > Cheers, > Alistair > (on phone) > >> -- Cyril Ferlicot https://ferlicot.fr

Feb. 12, 2019

Re: [Pharo-dev] File problems in Pharo 8

by Alistair Grant

Hi Cyril, In not at my PC at the moment, sorry. Can you try with vmLatest80? curl get.pharo.org/64/vmLatest80 | bash This looks like an issue I resolved recently. Cheers, Alistair (on phone) On Tue., 12 Feb. 2019, 11:16 Cyril Ferlicot, <cyril.ferlicot(a)gmail.com> wrote: > Hi, > > In Pharo 8 I have troubles because I get an error each time I try to > do an action calling a #deleteAll. > > I think the problem might have been introduced by the changes on Files > that were done to introduce FIleAttributes. > > I don't have much knowledge on this area and this is a little blocking > for me because when the problem triggers I cannot commit my changes > with Iceberg since it needs to delete folders. > > Bug report: https://github.com/pharo-project/pharo/issues/2495 > > -- > Cyril Ferlicot > https://ferlicot.fr > >

Feb. 12, 2019

File problems in Pharo 8

by Cyril Ferlicot

Hi, In Pharo 8 I have troubles because I get an error each time I try to do an action calling a #deleteAll. I think the problem might have been introduced by the changes on Files that were done to introduce FIleAttributes. I don't have much knowledge on this area and this is a little blocking for me because when the problem triggers I cannot commit my changes with Iceberg since it needs to delete folders. Bug report: https://github.com/pharo-project/pharo/issues/2495 -- Cyril Ferlicot https://ferlicot.fr

Feb. 12, 2019

[Pharo 8.0] Build #65: [IGNORE]2466-Remove-unused-variables

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

There is a new Pharo build available! The status of the build #65 was: FAILURE. The Pull Request #2468 was integrated: "[IGNORE]2466-Remove-unused-variables" Pull request url: https://github.com/pharo-project/pharo/pull/2468 Issue Url: https://pharo.fogbugz.com/f/cases/2466 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 12, 2019

Re: [Pharo-dev] PharoLauncher - upgrading to 1.6 on Windows

by Franz Josef Konrad

Am 12.02.2019 um 08:17 schrieb Petr Fischer via Pharo-dev: > > PharoLauncher - upgrading to 1.6 on Windows.eml > > Betreff: > PharoLauncher - upgrading to 1.6 on Windows > Von: > Petr Fischer <petr.fischer(a)me.com> > Datum: > 12.02.2019, 08:17 > > An: > pharo-dev(a)lists.pharo.org > > > Hello. > > I thought I'd try PharoLauncher again after some time and I really have a bad luck with this product. > > I have a PharoLauncher version 1.5.1 installed. If I run new 1.6 installer, this error occurs: > > "A more recent version of PharoLauncher is already installed on this computer" > https://app.box.com/s/rbn1n12zvx5rvy4zb1s0fujhkbzwvone > > "More recent?..." Really? > > I uninstalled old version manually of course, but... PharoLauncher can't update itself? > > Platform: Windows 10 Pro [1809] > > pf > I had the same problem and deleted the Pharo entries in the registry manually with regedit. After that I was able to use the installer. I suspect that the PharoLauncher does not yet contain the correct version information in the registry or that it is not evaluated correctly. Franz Josef

Feb. 12, 2019

PharoLauncher - upgrading to 1.6 on Windows

by Petr Fischer

Hello. I thought I'd try PharoLauncher again after some time and I really have a bad luck with this product. I have a PharoLauncher version 1.5.1 installed. If I run new 1.6 installer, this error occurs: "A more recent version of PharoLauncher is already installed on this computer" https://app.box.com/s/rbn1n12zvx5rvy4zb1s0fujhkbzwvone "More recent?..." Really? I uninstalled old version manually of course, but... PharoLauncher can't update itself? Platform: Windows 10 Pro [1809] pf

Feb. 12, 2019

[Pharo 8.0] Build #64: 2489-DatePrintFormatTester-should-be-removed

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

There is a new Pharo build available! The status of the build #64 was: FAILURE. The Pull Request #2490 was integrated: "2489-DatePrintFormatTester-should-be-removed" Pull request url: https://github.com/pharo-project/pharo/pull/2490 Issue Url: https://pharo.fogbugz.com/f/cases/2489 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 11, 2019

[Pharo 8.0] Build #63: 2476-Cleaning-initialize-categorisation

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

There is a new Pharo build available! The status of the build #63 was: FAILURE. The Pull Request #2477 was integrated: "2476-Cleaning-initialize-categorisation" Pull request url: https://github.com/pharo-project/pharo/pull/2477 Issue Url: https://pharo.fogbugz.com/f/cases/2476 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 11, 2019

Re: [Pharo-dev] Esteban's ChangeLog week of 4 February 2019

by Sean P. DeNigris

NorbertHartl wrote >> Or FixedLayout :P. Because actually it's not absolute, it's relative to >> its parent xD. > > The layout is absolute for the component it is applied to. Doesnât matter > if the component itself is layouted relative to something else. We donât > need to try hard to come up with new terms just be different to e.g. CSS Only skimmed the thread, but +1 to leaning heavily to accepted domain terms even if they are not "perfect". IMHO, for common domains, the tower of babel creates more accidental complexity than imperfect names. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 11, 2019