- Pharo-dev - lists.pharo.org

[Pharo-project] issue 26 / squeak 7073
by Norbert Hartl July 3, 2008

July 3, 2008

I've uploaded a new slice which incorporates the squeak update changes for version 7073. SLICE-squeakUpdate7073-noha.5 I can't change the status of the ticket as google is not allowing me to do any single action today :) First I got captchas for submitting issues and now I'm locked out. "You have performed the requested action too many times in a 24-hour time period. Or, you have performed the requested action too many times since the creation of your account." The last sentence makes me a bot afraid :) Norbert

2 2

[Pharo-project] 3.9.1, version numbers and fixes
by Norbert Hartl July 3, 2008

July 3, 2008

I'm a little bit confused. I started to have a look at the squeak fixes of 3dot10 we like to integrate. Looking at the version number I marked all version number up to 7075 as being duplicate (in the issue trackr) as we started from 3.9.1 which is 7075. But now I think I misunderstand something. I tried to merge squeak version 7076 into pharo. I did some stuff manually to be able to merge the monticello packages of that release. But the changes are massive. It's collections, collectionstests and kernel. There are even changes for widestring which I don't found in previous updates. Can somebody explain where we started off and what needs to be included. Pharo seems to be completely out of sync with 3.10. Norbert

3 2

[Pharo-project] Broken tests in Pharo-dev
by Oscar Nierstrasz July 3, 2008

July 3, 2008

Hi Folks, Just for phun, I checked the status of broken tests in the pharo-dev image. Since the Test Runner froze up on me, I tried to find out which are the offending test packages. Here is what I found: - Installer-Test brings up the Pre-Debugger due to non-existent classes (ClassClonerTestResource etc.) - Refactoring-Engine-Testing freezes with a Syntax Error window popping up. (Didn't yet find out which test is causing this.) - VB-Regex-Test stops due to a self halt in RxParserTest>>testMatchesInwW The remaining tests run, with a few uglies. Some tests are creating OB Package Browser windows and not cleaning them up. There are also some tests that prompt for user input. Otherwise there are 2329 run, 2302 passes, 15 expected failures, 12 failures, 0 errors, 0 unexpected passes amongst the remaining tests. Once we get core pharo cleaned up, it would be nice to get the tests running in pharo-dev too. - on

2 1

[Pharo-project] Fix for Issue 113 in PharoInbox
by Serge Stinckwich July 3, 2008

July 3, 2008

Look at : http://code.google.com/p/pharo/issues/detail?id=113 -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

1 0

[Pharo-project] Issue 29 fix in PharoInbox
by Serge Stinckwich July 3, 2008

July 3, 2008

I put the fix (with the tests) of issue 29 in PharoInbox : Collections-zz.85.mcz and CollectionsTests-zz.41.mcz -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

3 4

[Pharo-project] UI plans Question
by michael_atkisson＠comcast.net July 3, 2008

July 3, 2008

Are there any plans to make it possible to be able to move windows out of the main ui environment window.

2 1

[Pharo-project] 7072 and universes
by Norbert Hartl July 2, 2008

July 2, 2008

Squeak update 7072 updates the universes package. Do we want universes in the image or should I leave it out? Norbert

2 1

July 2, 2008

Hi all, I would really like that we start to think about a build server. ie a system that starts with an image and a package list and run the test. Here is a list of paths - using Installer - using Sake (I have to have a look at it). - DevImageCreator Do you have other pointers? Stef

3 4

[Pharo-project] 3dot10 fixes
by Norbert Hartl July 2, 2008

July 2, 2008

I had a look at the wiki page of 3dot10 fixes. The wiki page is good but I have the impression that putting all changes in the issue tracker could be worth it. I would create another type Type-squeak to track every update from squeak. I would prefer not to put the mantis issues into it but each squeak version. That would enable us to see if we are in sync with squeak. What do you think? I could do it in the next spare time. Norbert

6 13

[Pharo-project] 3dot10 issues
by Norbert Hartl July 2, 2008

July 2, 2008

I have created issues for all of the fixes mentioned on http://code.google.com/p/pharo/wiki/ThreeDotTenFixes After that I scanned the numbering (I chose the summary to include the number at beginning for sorting) and closed to gaps. The gaps have type comment and appear on the open issues list. I didn't take the time to scan mantis for the mantis number which includes the fix. We can arrange that. All issues have "Type-Squeak" being source of a squeak version fix and "Fixed" as a status. My proposal is that everyone takes tickets produces slices from it and changes the status to verified after uploading. To see all issues have a look at: http://code.google.com/p/pharo/issues/list?can=1&q=type:Squeak&sort=summary… Norbert

3 6