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

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Stephane Ducasse

Hi Peter If you can go ahead please. I do not remember if I started to migrate PharoExtras/BitmapCharacterSet PharoExtras/OrderPreservingDictionary Now I suggested to Cyril to create a ston file that we archive with all the mappings that we need. So this way we will avoid that every body has to find all the bindings for jb jba jean-baptiste anrut jean-baptiste arnaud.... Stef On Wed, Oct 3, 2018 at 7:56 AM monty <monty2(a)programmer.net> wrote: > > That would be appreciated, if you can do it and preserve the history. > But you also need: > PharoExtras/BitmapCharacterSet > PharoExtras/OrderPreservingDictionary > > ___ > montyos.wordpress.com > > > Sent: Saturday, September 29, 2018 at 6:18 AM > From: "Peter Uhnak" <i.uhnak(a)gmail.com> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Cc: monty <monty2(a)programmer.net> > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > Hi Stef, > > XMLParser is maintained by monty (I've CCed him). > > > Now the question still remains: who is planning to migrate the XML packages. > > I'd be happy to do that (including preserving the history), unless monty wants to do it themselves. > > Peter > > On Sat, Sep 29, 2018 at 10:39 AM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi >> >> I contacted the maintainer (but I'm not sure in fact who it is :) ) >> about the XML related packages in Pharo extras. >> >> XMLParser >> XMLParserHTML >> XMLParserStAX >> XMLSupport >> XMLWriter >> XPath >> >> I did not get any answer so may be I sent a mail to the wrong email address. >> Probably. >> Now the question still remains: who is planning to migrate the XML packages. >> I was planning to do it but I will not consider history because I do >> not know how to do it and I do not have the time to do it (sorry). And >> yes I work the weekends and this is bad and this is not even on Pharo. >> >> I was planning to spend some time on the baseline and making sure that >> we can load everything and run the tests. >> So let me know. >> >> Stef >>

Oct. 5, 2018

Re: [Pharo-dev] Conversion of my Libraries/Frameworks to GitHub/Tonel/TravisCI, Part 1

by Norbert Hartl

Great! And yet another reminder that all projects should consider moving to git. Norbert > Am 05.10.2018 um 14:05 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > Hi, > > I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. > So far I did the following: > > https://github.com/svenvc/NeoJSON > https://github.com/svenvc/NeoCSV > https://github.com/svenvc/ztimestamp > https://github.com/svenvc/P3 > https://github.com/svenvc/stamp > https://github.com/svenvc/SimpleRedisClient > https://github.com/svenvc/NeoConsole > > More will follow, in particular Zinc/Zodiac and STON, both of which are more complex. > > The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. > By loading the latest Metacello and Tonel, the code is also loadable in Pharo 6 or 5. > > After a while I will switch the Catalog entries and declare these repo the main ones. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Oct. 5, 2018

[Pharo 7.0-dev] Build #1309: 22538 Tag ManifestFileSystemZip and related classes in FileSystem-Zip package

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

There is a new Pharo build available! The status of the build #1309 was: FAILURE. The Pull Request #1876 was integrated: "22538 Tag ManifestFileSystemZip and related classes in FileSystem-Zip package" Pull request url: https://github.com/pharo-project/pharo/pull/1876 Issue Url: https://pharo.fogbugz.com/f/cases/22538 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 5, 2018

Re: [Pharo-dev] Conversion of my Libraries/Frameworks to GitHub/Tonel/TravisCI, Part 1

by Gabriel Cotelli

+100 Thank you Sven. On Fri, Oct 5, 2018 at 9:06 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. > So far I did the following: > > https://github.com/svenvc/NeoJSON > https://github.com/svenvc/NeoCSV > https://github.com/svenvc/ztimestamp > https://github.com/svenvc/P3 > https://github.com/svenvc/stamp > https://github.com/svenvc/SimpleRedisClient > https://github.com/svenvc/NeoConsole > > More will follow, in particular Zinc/Zodiac and STON, both of which are > more complex. > > The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. > By loading the latest Metacello and Tonel, the code is also loadable in > Pharo 6 or 5. > > After a while I will switch the Catalog entries and declare these repo the > main ones. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > >

Oct. 5, 2018

Conversion of my Libraries/Frameworks to GitHub/Tonel/TravisCI, Part 1

by Sven Van Caekenberghe

Hi, I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. So far I did the following: https://github.com/svenvc/NeoJSON https://github.com/svenvc/NeoCSV https://github.com/svenvc/ztimestamp https://github.com/svenvc/P3 https://github.com/svenvc/stamp https://github.com/svenvc/SimpleRedisClient https://github.com/svenvc/NeoConsole More will follow, in particular Zinc/Zodiac and STON, both of which are more complex. The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. By loading the latest Metacello and Tonel, the code is also loadable in Pharo 6 or 5. After a while I will switch the Catalog entries and declare these repo the main ones. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Oct. 5, 2018

[Pharo 7.0-dev] Build #1308: 22532-Adding-repository-to-package-via-MonticelloBrowser-is-broken

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

There is a new Pharo build available! The status of the build #1308 was: FAILURE. The Pull Request #1870 was integrated: "22532-Adding-repository-to-package-via-MonticelloBrowser-is-broken" Pull request url: https://github.com/pharo-project/pharo/pull/1870 Issue Url: https://pharo.fogbugz.com/f/cases/22532 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 5, 2018

[Pharo 7.0-dev] Build #1307: 22520-Deprecate-HistoryCollection

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

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

Oct. 5, 2018

[Pharo 7.0-dev] Build #1306: 22533-WelcomeHelp-should-not-have-hardcoded-version

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

There is a new Pharo build available! The status of the build #1306 was: SUCCESS. The Pull Request #1868 was integrated: "22533-WelcomeHelp-should-not-have-hardcoded-version" Pull request url: https://github.com/pharo-project/pharo/pull/1868 Issue Url: https://pharo.fogbugz.com/f/cases/22533 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 5, 2018

[Pharo 7.0-dev] Build #1305: 22500-LinkedListrejectthenCollect-is-slow

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

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

Oct. 5, 2018

[Pharo 7.0-dev] Build #1304: 22505-Storing-and-restoring-of-settings-cause-startup-errors

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

There is a new Pharo build available! The status of the build #1304 was: SUCCESS. The Pull Request #1867 was integrated: "22505-Storing-and-restoring-of-settings-cause-startup-errors" Pull request url: https://github.com/pharo-project/pharo/pull/1867 Issue Url: https://pharo.fogbugz.com/f/cases/22505 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 5, 2018