- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #900: 4961-moduleName-recursion

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

There is a new Pharo build available! The status of the build #900 was: FAILURE. The Pull Request #4962 was integrated: "4961-moduleName-recursion" Pull request url: https://github.com/pharo-project/pharo/pull/4962 Issue Url: https://github.com/pharo-project/pharo/issues/4961 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 21, 2019

[Pharo 8.0] Build #899: 4959-CompletionSorter-should-be-properly-initialized

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

There is a new Pharo build available! The status of the build #899 was: FAILURE. The Pull Request #4960 was integrated: "4959-CompletionSorter-should-be-properly-initialized" Pull request url: https://github.com/pharo-project/pharo/pull/4960 Issue Url: https://github.com/pharo-project/pharo/issues/4959 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 21, 2019

[Pharo 8.0] Build #898: 4941-Standalone-Glamour-and-GT

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

There is a new Pharo build available! The status of the build #898 was: SUCCESS. The Pull Request #4943 was integrated: "4941-Standalone-Glamour-and-GT" Pull request url: https://github.com/pharo-project/pharo/pull/4943 Issue Url: https://github.com/pharo-project/pharo/issues/4941 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 21, 2019

[Pharo 8.0] Build #897: 4957-safer-ensureCreateDirectory

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

There is a new Pharo build available! The status of the build #897 was: SUCCESS. The Pull Request #4958 was integrated: "4957-safer-ensureCreateDirectory" Pull request url: https://github.com/pharo-project/pharo/pull/4958 Issue Url: https://github.com/pharo-project/pharo/issues/4957 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 21, 2019

Re: [Pharo-dev] How top report a fix to github of Pharo????

by Pavel Krivanek

BTW. fix of this issue is already part of this PR that did changes is the Catalog loading: https://github.com/pharo-project/pharo/pull/4943 <https://github.com/pharo-project/pharo/pull/4943/files> -- Pavel ne 20. 10. 2019 v 22:07 odesÃlatel Brainstorms <wild.ideas(a)gmail.com> napsal: > Hi Casimiro, > > Since you have a coded fix, you should take a look at this web page: > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > > Alternatively, you can just enter an issue against Pharo here: > https://github.com/pharo-project/pharo/issues > > Cheers, > -Ted > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Oct. 21, 2019

[Pharo 8.0] Build #896: 4953-moduleName-needs-to-be-properly-deprecated

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

There is a new Pharo build available! The status of the build #896 was: SUCCESS. The Pull Request #4955 was integrated: "4953-moduleName-needs-to-be-properly-deprecated" Pull request url: https://github.com/pharo-project/pharo/pull/4955 Issue Url: https://github.com/pharo-project/pharo/issues/4953 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 21, 2019

[Pharo 7.0] Build #171: 4875-Recover-lost-changes-does-not-apply-changes-in-right-order

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

There is a new Pharo build available! The status of the build #171 was: SUCCESS. The Pull Request #4908 was integrated: "4875-Recover-lost-changes-does-not-apply-changes-in-right-order" Pull request url: https://github.com/pharo-project/pharo/pull/4908 Issue Url: https://pharo.fogbugz.com/f/cases/4875 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 21, 2019

[Pharo 8.0] Build #895: fix-old-workspace

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

There is a new Pharo build available! The status of the build #895 was: SUCCESS. The Pull Request #4954 was integrated: "fix-old-workspace" Pull request url: https://github.com/pharo-project/pharo/pull/4954 Issue Url: https://github.com/pharo-project/pharo/issues/fix Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 21, 2019

ThatÂ´s the error that happens during the load of Seaside3 in Pharo (7, 8) in Windows 10.

by casimiro.barreto＠gmail.com

Good morning, It seems to be related to filename and Windows conventions. The error message is: "LGit_GIT_EEXISTS: Failed to stat file 'C:/Users/casim/Documents/Pharo/images/Pharo 8.0 - 64bit (dev...uteAge.maximumRelativeAge.overflowAction..st': O nome do arquivo ou a extensÃÂ£o ÃÂ© muito grande." Self Seems the failed pathname is: 'C:/Users/casim/Documents/Pharo/images/Pharo 8.0 - 64bit (dev...uteAge.maximumRelativeAge.overflowAction..st' That kind of error was found while loading other packagesâ¦ The remedy I found was the ugly one: load the image in Linux and then copy to windowsâ¦ minus the cache because windows will complain about the filenamesâ¦ (nevermind if I unzip, untar or simply copy from a shared folder to a windows folder). Best regards, Casimiro Barreto

Oct. 21, 2019

[Pharo 8.0] Build #894: 3048-StringwithUnixLineEndings-shouldnt-modify-the-the-original-string

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

There is a new Pharo build available! The status of the build #894 was: SUCCESS. The Pull Request #4912 was integrated: "3048-StringwithUnixLineEndings-shouldnt-modify-the-the-original-string" Pull request url: https://github.com/pharo-project/pharo/pull/4912 Issue Url: https://github.com/pharo-project/pharo/issues/3048 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 21, 2019