July 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] renggli mirror created on smalltalkhub

by phil＠highoctane.be

There must be a business behind all this to take care of the funding and the daily operations. Is the consortium going to be taking care of these aspects? Phil 2012/7/4 Torsten Bergmann <astares(a)gmx.de> > > Norbert wrote: > >Ok, nothing to do here. Thank you, Captain Hindsight! > > While I enjoy your humor and politeness on one side I really > doubt that there is nothing to do here. > > How often do we face the outage of SqS. And now a private > server is yet again gone without an easy restore/access to > the backup. It's nice that we can all check our caches to > find the mcz's - but is this the backup strategy to go for > the future? > > I provided the ConfigurationBrowser in Pharo to easily load > Metacello packages directly from within the image and spend > a lot of time checking appropriate configs for the various > Pharo versions. On one side we invest in making it easier > for people to load packages on the other side it often > did not work due to this brickle hosting we currently have. > > Don't we need a serious discussion and actions on how > to get a reliable infrastructure with official mirrors? > > By providing a prebuilt SqueakSource in the past [1] I hoped > the SqS situation will get better when people may setup own > servers and we have more and more mirrors on the net. It did > not happen. We now know that SqS is the "old way". > > We currently face decisions what servers to use (SS3, SmalltalkHub, ...) > see issue #6093 [2] > > Now we move to SS3 and SmalltalkHub. Can we answer the question > how reliable they are? > > I like SmalltalkHub a lot. But still it is centralized and > if it is down it is down for all. Dont we need answers to the > question how independent our infrastructure will be in the future? > If it is backuped, mirrored or restorable? > > Dale proposed mirroring for Metacello [3]. We also have filetree [4] > for directory-based Monticello packages enabling the use of Git, > SVN, ... allowing us to use more reliable infrastructure like GitHub, ... > Should we care? > > But maybe I should shut up and wait until someone reboots > Squeaksource again (which is down today yet again) > > Bye > T. > > [1] http://astares.blogspot.de/2005/12/squeaksource-server-image.html > [1] http://code.google.com/p/pharo/issues/detail?id=6093 > [2] http://code.google.com/p/metacello/issues/detail?id=152 > [3] https://github.com/dalehenrich/filetree > > > >

July 4, 2012

Re: [Pharo-project] Problem with FileSystem primitives in latest Pharo2.0

by Marcus Denker

Are you using a current VM from Jenkins? I think FileSystem needs some fixes in the Vm File plugin... On Jul 4, 2012, at 9:23 AM, Fernando Olivero wrote: > Hi, i found an error in the latest Pharo2.0 build, at least in OSX , > that prevents from using Gofer and monticello. > > Its related to the FileSystem primitives, when trying to delete a file. > > To reproduce evaluate the following code ( change 'PharoDebug.log' for > any existing file in the same directory as the image). > > | path | > path := FileSystem disk workingDirectory. > p := FilePluginPrims new . > p deleteDirectory: (path / 'PharoDebug.log') fullName. > > > Any idea why? > > Thanks, > Fernando > -- Marcus Denker -- http://marcusdenker.de

July 4, 2012

[Pharo-project] Problem with FileSystem primitives in latest Pharo2.0

by Fernando Olivero

Hi, i found an error in the latest Pharo2.0 build, at least in OSX , that prevents from using Gofer and monticello. Its related to the FileSystem primitives, when trying to delete a file. To reproduce evaluate the following code ( change 'PharoDebug.log' for any existing file in the same directory as the image). | path | path := FileSystem disk workingDirectory. p := FilePluginPrims new . p deleteDirectory: (path / 'PharoDebug.log') fullName. Any idea why? Thanks, Fernando

July 4, 2012

[Pharo-project] [Issue Tracker] a push to get the numbers down

by Marcus Denker

Hello, There are 531 issues on the tracker: http://code.google.com/p/pharo/issues/list?can=2 We should realize that just adding things will not scale.. we need to close issues, too. This is especially true for -> duplicates -> things that have already been fixed -> reports on code that has been removed or deprecated Another kind of reports cluttering the system are "small" code smells that are easy to fix. But fixing we need to...we can not just add and add and add. So which of the trivial-to-fix reports *you* did you can fix yourself? Which ones are actually so un-important that they are not even worth your time fixing and thus should be closed? It would be nice if everyone would at least look at the issues that he/she submitted. One can easily search for the owner of a report: http://code.google.com/p/pharo/issues/list?can=2&q=owner%3AMarcus.Denker -- Marcus Denker -- http://marcusdenker.de

July 4, 2012

[Pharo-project] renggli mirror created on smalltalkhub

by Torsten Bergmann

Norbert wrote: >Ok, nothing to do here. Thank you, Captain Hindsight! While I enjoy your humor and politeness on one side I really doubt that there is nothing to do here. How often do we face the outage of SqS. And now a private server is yet again gone without an easy restore/access to the backup. It's nice that we can all check our caches to find the mcz's - but is this the backup strategy to go for the future? I provided the ConfigurationBrowser in Pharo to easily load Metacello packages directly from within the image and spend a lot of time checking appropriate configs for the various Pharo versions. On one side we invest in making it easier for people to load packages on the other side it often did not work due to this brickle hosting we currently have. Don't we need a serious discussion and actions on how to get a reliable infrastructure with official mirrors? By providing a prebuilt SqueakSource in the past [1] I hoped the SqS situation will get better when people may setup own servers and we have more and more mirrors on the net. It did not happen. We now know that SqS is the "old way". We currently face decisions what servers to use (SS3, SmalltalkHub, ...) see issue #6093 [2] Now we move to SS3 and SmalltalkHub. Can we answer the question how reliable they are? I like SmalltalkHub a lot. But still it is centralized and if it is down it is down for all. Dont we need answers to the question how independent our infrastructure will be in the future? If it is backuped, mirrored or restorable? Dale proposed mirroring for Metacello [3]. We also have filetree [4] for directory-based Monticello packages enabling the use of Git, SVN, ... allowing us to use more reliable infrastructure like GitHub, ... Should we care? But maybe I should shut up and wait until someone reboots Squeaksource again (which is down today yet again) Bye T. [1] http://astares.blogspot.de/2005/12/squeaksource-server-image.html [1] http://code.google.com/p/pharo/issues/detail?id=6093 [2] http://code.google.com/p/metacello/issues/detail?id=152 [3] https://github.com/dalehenrich/filetree

July 4, 2012

[Pharo-project] pharo-2.0-tests Â» 32,mac - Build # 179 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

July 4, 2012

[Pharo-project] pharo-2.0-tests Â» 32,linux - Build # 179 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

July 4, 2012

[Pharo-project] pharo-2.0-tests Â» 32,win - Build # 179 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

July 4, 2012

[Pharo-project] [update 2.0] #20179

by Marcus Denker

20179 ----- Issue 6241: Fix NewVersionBorwser http://code.google.com/p/pharo/issues/detail?id=6241 Issue 6246: RGMethodDefintion asMCMethodDefinition cache was removed http://code.google.com/p/pharo/issues/detail?id=6246 Issue 6232: Remove SystemChangeNotifierTests http://code.google.com/p/pharo/issues/detail?id=6232 Issue 6215: Test failing for MCDirectoryRepositoryTest http://code.google.com/p/pharo/issues/detail?id=6215 Issue 6138: AbsolutePath not absolute on Windows http://code.google.com/p/pharo/issues/detail?id=6138 -- Marcus Denker -- http://marcusdenker.de

July 4, 2012

Re: [Pharo-project] ohloh is sad

by Sean P. DeNigris

Camillo Bruni-3 wrote > > now I want to see everybody from the mailinglist on there :P > Done -- View this message in context: http://forum.world.st/ohloh-is-sad-tp4637961p4637990.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 4, 2012