October 2019 - Pharo-dev - lists.pharo.org

[Pharo 7.0] Build #171: 4875-Recover-lost-changes-does-not-apply-changes-in-right-order
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2019

Oct. 23, 2019

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…

2 1

[Pharo 8.0] Build #901: Commands for Iceberg to browse repository with Calypso
by ci-pharo-ci-jenkins2＠inria.fr Oct. 22, 2019

Oct. 22, 2019

There is a new Pharo build available! The status of the build #901 was: FAILURE. The Pull Request #4840 was integrated: "Commands for Iceberg to browse repository with Calypso" Pull request url: https://github.com/pharo-project/pharo/pull/4840 Issue Url: https://github.com/pharo-project/pharo/issues/iceRepoBrowser Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #900: 4961-moduleName-recursion
by ci-pharo-ci-jenkins2＠inria.fr Oct. 21, 2019

Oct. 21, 2019

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…

1 0

[Pharo 8.0] Build #899: 4959-CompletionSorter-should-be-properly-initialized
by ci-pharo-ci-jenkins2＠inria.fr Oct. 21, 2019

Oct. 21, 2019

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…

1 0

[Pharo 8.0] Build #898: 4941-Standalone-Glamour-and-GT
by ci-pharo-ci-jenkins2＠inria.fr Oct. 21, 2019

Oct. 21, 2019

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…

1 0

[Pharo 8.0] Build #897: 4957-safer-ensureCreateDirectory
by ci-pharo-ci-jenkins2＠inria.fr Oct. 21, 2019

Oct. 21, 2019

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…

1 0

How top report a fix to github of Pharo????
by casimiro.barreto＠gmail.com Oct. 21, 2019

Oct. 21, 2019

Hello, As mentioned before, thereÂ´s a problem with CatalobBrawser in Pharo 8. Basically the message: createRepositoryURLtoNameMappings "Return a mapping between repositories URLs and their user names" <script: 'self createRepositoryURLtoNameMappings inspect'> |repos| repos := Dictionary new. 3 to: SystemVersion current major do: [:v | repos at: ('http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo{1}0/main' format: v asArray) put: ('Pharo{1}.0' format: v asArray)]. repos at: 'http://www.squeaksource.com/MetacelloRepository' put: 'Unsorted'. ^repos Must be fixed so it goes to: createRepositoryURLtoNameMappings "Return a mapping between repositories URLs and their user names" <script: 'self createRepositoryURLtoNameMappings inspect'> |repos| repos := Dictionary new. 3 to: SystemVersion current major do: [:v | repos at: ('http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo{1}0/main' format: (Array with: v)) put: ('Pharo{1}.0' format: (Array with: v))]. repos at: 'http://www.squeaksource.com/MetacelloRepository' put: 'Unsorted'. ^repos Or something like it without the use of asArray. I was asked to report the bug in github, but IÂ´m not sure where. Thanx, Casimiro Barreto

4 3

[Pharo 8.0] Build #896: 4953-moduleName-needs-to-be-properly-deprecated
by ci-pharo-ci-jenkins2＠inria.fr Oct. 21, 2019

Oct. 21, 2019

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…

1 0

[Pharo 8.0] Build #895: fix-old-workspace
by ci-pharo-ci-jenkins2＠inria.fr Oct. 21, 2019

Oct. 21, 2019

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…

1 0

ThatÂ´s the error that happens during the load of Seaside3 in Pharo (7, 8) in Windows 10.
by casimiro.barreto＠gmail.com Oct. 21, 2019

Oct. 21, 2019

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

1 0