- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] FOSDEM rooms are available

by Santiago Bragagnolo

That is great. We should post in all of them if possible. I think that Steven could show object centric debugging, someone (anne maybe? ) present moose. and for minimalistic experimental emerging languages carolina could propose candle and the bootstrap processes. I think that Steven and Carolina talks are mature enough after all the trials, and a moose talk could be really cool. Maybe Julien's SQL or Benoit's translations should be really good for catching potential students and specially some investment capital for the team :). Sadly me i don't have much to show :(. But if we have the stand i plan to be there. El lun., 28 oct. 2019 a las 16:41, ducasse (<stepharo(a)netcourrier.com>) escribiÃ³: > > https://fosdem.org/2020/news/2019-10-01-accepted-developer-rooms/ > I do not know in which one we want to participate > > Debugging Tools > Minimalistic, Experimental and Emerging Languages > Open Research Tools and Technologies > > How do we coordinate? > > S. >

Oct. 28, 2019

FOSDEM rooms are available

by ducasse

https://fosdem.org/2020/news/2019-10-01-accepted-developer-rooms/ I do not know in which one we want to participate Debugging Tools Minimalistic, Experimental and Emerging Languages Open Research Tools and Technologies How do we coordinate? S.

Oct. 28, 2019

[Pharo 8.0] Build #919: Update Tonel to v1.0.15

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

There is a new Pharo build available! The status of the build #919 was: SUCCESS. The Pull Request #5022 was integrated: "Update Tonel to v1.0.15" Pull request url: https://github.com/pharo-project/pharo/pull/5022 Issue Url: https://github.com/pharo-project/pharo/issues/update Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 28, 2019

[Pharo 8.0] Build #918: Boolean-method

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

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

Oct. 28, 2019

[Pharo 8.0] Build #917: Go-over-some-flags

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

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

Oct. 28, 2019

Re: [Pharo-dev] Git URL issues

by Sven Van Caekenberghe

I am still at a loss with this issue. When loading from github://svenvc/ztimestamp using Metacello (see original mail) the code in MCGitBasedNetworkRepository>>#createIcebergRepositoryWithFallbackFor:url: clearly switches to using https://github.com/svenvc/ztimestamp.git - I traced it. So obviously, Pharo 7 is capable of accessing it. However, starting directly with https://github.com/svenvc/ztimestamp.git I end up in a totally different place. Why ? This code is so complex... > On 25 Oct 2019, at 14:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > I asked this before, but I still have trouble with this. > > What I ultimately want is what I used for years now: use the zero config tools to point to my private repo and install my code and all its dependencies from a single Metacello config. > > Basically, > > $vm $image config _CONFIG_REPO_ _CONFIG_NAME_ --username=_CONFIG_USER_ --password=_CONFIG_PASS_ --install=_CONFIG_VERSION_ --group=_CONFIG_GROUP_ > > towards a private server. > > In the new world of git(hub)/tonel/iceberg I am trying the following (not using the 'config' but the new 'metacello' command line handler): > > $ uname -a > Linux audio359 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux > > $ curl get.pharo.org/64/70+vm | bash > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 100 3054 100 3054 0 0 57622 0 --:--:-- --:--:-- --:--:-- 57622 > Downloading the latest 70 Image: > http://files.pharo.org/get-files/70/pharo64.zip > Pharo.image > Downloading the latest pharoVM: > http://files.pharo.org/get-files/70/pharo64-linux-stable.zip > pharo-vm/pharo > Creating starter scripts pharo and pharo-ui > > $ ./pharo Pharo.image printVersion > [version] 'Pharo7.0.4' 'Pharo-7.0.4+build.168.sha.ccd1f6489120f58ddeacb2cac77cd3a0f0dcfbe6 (64 Bit)' > > $ ./pharo Pharo.image save build > > $ ./pharo build.image metacello install github://svenvc/ztimestamp BaselineOfZTimestamp > > 3. using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) I will try to clone the HTTPS variant. > Fetched -> BaselineOfZTimestamp-CompatibleUserName.1554735117 --- https://github.com/svenvc/ztimestamp.git[master] --- https://github.com/svenvc/ztimestamp.git[master] > Loaded -> BaselineOfZTimestamp-CompatibleUserName.1554735117 --- https://github.com/svenvc/ztimestamp.git[master] --- https://github.com/svenvc/ztimestamp.git[master] > Loading baseline of BaselineOfZTimestamp... > Fetched -> ZTimestamp-CompatibleUserName.1554735117 --- https://github.com/svenvc/ztimestamp.git[master] --- https://github.com/svenvc/ztimestamp.git[master] > Loaded -> ZTimestamp-CompatibleUserName.1554735117 --- https://github.com/svenvc/ztimestamp.git[master] --- cache > ...finished baseline > > $ ./pharo build.image eval ZTimestamp now > 2019-10-25T12:28:34Z > > So although it gave a warning, it worked fine. > > The warning said, > > using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) I will try to clone the HTTPS variant. > > so let's try that after cleaning everything: > > $ rm -rf pharo-local/ build.* > > $ ./pharo Pharo.image save build > > $ ./pharo build.image metacello install https://github.com/svenvc/ztimestamp.git BaselineOfZTimestamp > > ...RETRY->BaselineOfZTimestamp > ...RETRY->BaselineOfZTimestamp > ...FAILED->BaselineOfZTimestampCould not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /home/sven/pharo7/pharo-local/package-cache https://github.com/svenvc/ztimestamp.git > MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: > > WTF ? Why does this not work (I can perfectly git clone that URL) ? > > Of course, this would just be the first step, eventually I want to use my own private server with a URL like > > https://deploy:secret@bitbucket.myserver.be/scm/xyz/xyz-pharo.git > > How do you build/deploy non-public production code using the command line ? > > Help would be much appreciated. > > Sven >

Oct. 28, 2019

[Pharo 8.0] Build #916: 5018-RPackageSetcollectFromAllPackages-and-collectFromAllPackageswith-can-be-replaced-by-flatCollect

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

There is a new Pharo build available! The status of the build #916 was: FAILURE. The Pull Request #5019 was integrated: "5018-RPackageSetcollectFromAllPackages-and-collectFromAllPackageswith-can-be-replaced-by-flatCollect" Pull request url: https://github.com/pharo-project/pharo/pull/5019 Issue Url: https://github.com/pharo-project/pharo/issues/5018 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 28, 2019

[Pharo 8.0] Build #915: Do-a-pass-on-some-flags

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

There is a new Pharo build available! The status of the build #915 was: SUCCESS. The Pull Request #5009 was integrated: "Do-a-pass-on-some-flags" Pull request url: https://github.com/pharo-project/pharo/pull/5009 Issue Url: https://github.com/pharo-project/pharo/issues/Do Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 27, 2019

[Pharo 8.0] Build #914: 5015-Epicea-EpLostCHangesDetector-should-be-Spec2fied

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

There is a new Pharo build available! The status of the build #914 was: SUCCESS. The Pull Request #5016 was integrated: "5015-Epicea-EpLostCHangesDetector-should-be-Spec2fied" Pull request url: https://github.com/pharo-project/pharo/pull/5016 Issue Url: https://github.com/pharo-project/pharo/issues/5015 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 27, 2019

[Pharo 8.0] Build #913: 4864-Add-a-browse-menu-item

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

There is a new Pharo build available! The status of the build #913 was: SUCCESS. The Pull Request #5014 was integrated: "4864-Add-a-browse-menu-item" Pull request url: https://github.com/pharo-project/pharo/pull/5014 Issue Url: https://github.com/pharo-project/pharo/issues/4864 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 27, 2019