[BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

On Jan 9, 2010, at 22:32 , Mariano Martinez Peck wrote:

> Thanks Benoit for the report and taking the time to run all the
> tests. I
> already knew that there are a lot failing tests. Unfortunately,
> there is not
> too much I can do:
>
> 1) Maintainers of packages with failures can tell me if they are
> failing for
> "my fault". I mean,  because I don't load a dependency or something
> like
> that. And if this is the case, I can fix that.
>
> 2) I can remove all the packages that have failing tests -> I think
> we will
> load very few packages.
>
> 3) We should ask maintainers to fix them. Of course, there are
> packages that
> even don't have maintainers.
>
> thoughts about this ?

Some time ago I individually talked with each maintainer and
eventually we managed to get all tests pass. That was with the
previous build of the Pharo image that Damien did. Now, I don't know
which additional tests you have loaded (?) but either these need to be
fixed or we should not load them. We want all tests to be green for
the release.

Cheers,
Adrian

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Bill,


all I wanted to do with that snippet was to help you install seaside.
I did not want to pretend that this is the 'blessed' way of doing it
;-)

Cheers

Matthias

On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K
<[hidden email]> wrote:
> Matthias,
>
> That appears to have worked.  Let's see, we have Installer, ScriptLoader, Configuration*, Gofer, etc., and now Loader =:0  I'm guilty too, because I ended up writing Migrate in self defense.  Clearly something is missing in package management or we would not have so many different solutions to strongly overlapping problems.
>
> I will have to repeat this because
>
>  Loader new load: 'Pharo' version: '1.0-rc2.10505'.
>
> did not seem to do much - makes me wonder whether I really ran it.  If not, then it appears not to be necessary for Seaside to at least load.
>
> If this is in fact the correct way to install Seaside (I submit we need direction on that, unless you or Esteban are the authoritative source??), then it needs to get a link on the download page.  Therein, we should refer to (Smalltalk at:#Loader) rather than directly to Loader.
>
> Please convey my thanks and respect to Esteban - not sure I want to know *how* this works :)
>
> Thanks!!
>
> Bill
>
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Matthias Berth
> Sent: Saturday, January 09, 2010 6:09 PM
> To: [hidden email]
> Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
>
> Hi Bill,
>
> this one works for me with the current pharo core 1.0 rc1, update upto 10505
>
> "execute this:"
> Gofer new
>       squeaksource: 'Loader';
>       package: 'Loader';
>       load.
> "then this"
> Loader new load: 'Pharo' version: '1.0-rc2.10505'.
> "then this"
> Loader new
>       load: 'Seaside28' version: '2.8.4.2'
>
> The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot of additional pharo packages. I guess you won't need that just to get seaside working.
>
> Ask Esteban Lorenzano for details about hw this works :)
>
> Cheers
>
> Matthias
>
> 2010/1/9 Schwab,Wilhelm K <[hidden email]>:
>> Two can be tired of this.  I could just use the official Seaside
>> images, but I thought it might be nice to help with testing the
>> monthly images.  I won't get very far with that if Seaside won't load.
>>
>>
>> ________________________________
>> From: [hidden email]
>> [mailto:[hidden email]] On Behalf Of
>> Mariano Martinez Peck
>> Sent: Saturday, January 09, 2010 4:38 PM
>> To: [hidden email]
>> Subject: Re: [Pharo-project] [BetaTesting] [ANN]
>> Pharo1.0-10505-rc1dev10.01.1
>>
>>
>>
>> 2010/1/9 Schwab,Wilhelm K <[hidden email]>
>>>
>>> Mariano,
>>>
>>> The reason I objected (and continue to do so) to clobbering the web
>>> image is that complete chaos of how to install things comes into
>>> play.  Assuming that I know what YOU said on the subject is a stretch
>>> to say the least: try a search engine on the subject.
>>>
>>
>> I am a bit tired of this. I will answer for the last time and I hope
>> you
>> understand: Do you want seaside ?
>>
>> 1) Volunteer yourself to build Web images. It is easy to ask, but what
>> about doing?
>>
>> 2) Take the Web Image before, analize how seaside was installed and do
>> it by yourself. I cannot take it more than half an hour.
>>
>> 3) Use official seaside image
>>
>> 4) Report what doesn't work with the ConfigurationOfSeaside in
>> Metacello mailing list so that everybody can collaborate and fix it.
>> If you see that mailing list, I did exactly that. Just saying "doesn't work"  does not help.
>>
>> Cheers
>>
>> Mariano
>>
>>>
>>> BTW, it does not work.  There is very little I can do until Seaside loads.
>>>
>>> Bill
>>>
>>> ________________________________
>>> From: [hidden email]
>>> [mailto:[hidden email]] On Behalf Of
>>> Mariano Martinez Peck
>>> Sent: Saturday, January 09, 2010 4:08 PM
>>> To: [hidden email]
>>> Subject: Re: [Pharo-project] [BetaTesting] [ANN]
>>> Pharo1.0-10505-rc1dev10.01.1
>>>
>>>
>>>
>>> 2010/1/9 Schwab,Wilhelm K <[hidden email]>
>>>>
>>>> Gofer seaside28 load
>>>>
>>>
>>> I didn't say that. I said:
>>>
>>> Gofer new
>>>     squeaksource: 'MetacelloRepository';
>>>     package: 'ConfigurationOfSeaside28';
>>>     load.
>>>
>>> (Smalltalk at: #ConfigurationOfSeaside28) load
>>>
>>> And I also said I was not sure of this is working.
>>>
>>> Cheers
>>>
>>> Mariano
>>>
>>>>
>>>> does not work.  What is the correct way to install Seaside - I can't
>>>> do much w/o it.
>>>>
>>>> ________________________________
>>>> From: [hidden email]
>>>> [mailto:[hidden email]] On Behalf Of
>>>> Mariano Martinez Peck
>>>> Sent: Saturday, January 09, 2010 3:01 PM
>>>> To: [hidden email]
>>>> Subject: Re: [Pharo-project] [BetaTesting] [ANN]
>>>> Pharo1.0-10505-rc1dev10.01.1
>>>>
>>>>
>>>>
>>>> 2010/1/9 Miguel Enrique Cobá Martinez <[hidden email]>
>>>>>
>>>>> Hi Mariano,
>>>>>
>>>>> good job. Some feedback.
>>>>>
>>>>> The installScript has unused variables and your proxy settings exposed.
>>>>> Maybe this should be deleted from the final build.
>>>>>
>>>>
>>>> hahahahah I knew I was going to forget about that :( Thanks. Some
>>>> bash guru that help me to automatize this? I would like something
>>>> that automatically removes that from the file if it is found.
>>>> Can you help me Miguel ?
>>>>
>>>>>
>>>>> Shouldn't be this a RC 2? because there is a new build process and
>>>>> has nothing to do with the RC1?
>>>>>
>>>>
>>>> I thought about putting it RC2, actually, I was going to do that.
>>>> But as the PharoCore was named rc1, I din't want to name it rc2
>>>> because maybe it was confusing.
>>>> I am not sure, thus. What do you think ?
>>>>
>>>>>
>>>>> Also, the changes files, shouldn't be compressed for each RC and
>>>>> for the final release?
>>>>
>>>> Excellent point. Do you rather to Smalltalk >> condenseChanges ?  It
>>>> can be perfectly added. Right now, we are doing all this:
>>>>
>>>>
>>>>     MCFileBasedRepository flushAllCaches.
>>>>     MCDefinition clearInstances.
>>>>     Smalltalk removeEmptyMessageCategories.
>>>>     Utilities cleanseOtherworldlySteppers.
>>>>     Undeclared removeUnreferencedKeys.
>>>>     Categorizer sortAllCategories.
>>>>     Symbol compactSymbolTable.
>>>>     Smalltalk at: #ReleaseBuilderDeveloper ifPresent: [:builder |
>>>> builder new fixObsoleteReferences].
>>>>     RequiredSelectors initialize.
>>>>     ProvidedSelectors initialize.
>>>>     LocalSends initialize.
>>>>     Smalltalk organization removeEmptyCategories.
>>>>     SystemBrowser removeObsolete.
>>>>     TheWorldMenu removeObsolete.
>>>>     AppRegistry removeObsolete.
>>>>     Set rehashAllSets.
>>>>     Smalltalk cleanOutUndeclared.
>>>>     Smalltalk garbageCollect.
>>>>
>>>>
>>>> Do you think something else should be addded?   Maybe we can reuse
>>>> ScriptLoader cleanings ?
>>>>
>>>>
>>>>>
>>>>> Also, the packages.txt file talks about PharoCore1.0 (#10505). Has
>>>>> someone thought about the name shown in System->About:
>>>>>
>>>>> PharoCore1.0rc1
>>>>> Latest update: #10505
>>>>>
>>>>> Because this is not a PharoCore image. Shouldn't this read
>>>>> something like
>>>>>
>>>>> Pharo 1.0 Dev image.
>>>>> Based on PharoCore1.0rc1
>>>>> Latest update: #10505
>>>>>
>>>>
>>>> Yes, that's true. I agree. At least it was not "my falt" as it was
>>>> already like that. But I am agree we should change that. However, I
>>>> don't know how to do it.
>>>> Maybe something related to SystemVersion? Any help ?
>>>>
>>>>
>>>>>
>>>>> What about the disabling of software updates in the Pharo dev/web
>>>>> images? Will this be implemented or a careful update stream will be
>>>>> made in order to not break a dev image with overrides (real
>>>>> difficult I think).
>>>>>
>>>>
>>>> Maybe. But in addition, sometimes there are bugs that updating just
>>>> fix them. I am not sure if I want to disable. I rather warn people about it.
>>>> Do you know if we break some overrrides doing an update?
>>>>
>>>>>
>>>>> Maybe all this setup can be put in a post-script in the
>>>>> ConfigurationOfPharo class.
>>>>
>>>> It is. We have pre and post do its. So, no problem :)
>>>>
>>>>>
>>>>> That's all for now. I'm going to use this image to work the
>>>>> following days.
>>>>>
>>>>>
>>>>> Cheers and keep the good work.
>>>>>
>>>>
>>>> Thanks Miguel for the excellent feedback. Let's hope to build better
>>>> images!
>>>>
>>>> Mariano
>>>>
>>>>
>>>>>
>>>>> --
>>>>> Miguel Cobá
>>>>> http://miguel.leugim.com.mx
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Pharo-project mailing list
>>>>> [hidden email]
>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> [hidden email]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Lukas is the official maintainer of the OB package for Pharo.
Therefore I assume OB should be loaded from his repository... Lukas?

Cheers,
Adrian

PS: I don't know why testFinalizationOfEquals sometimes fails (also in
PharoCore)

PPS: Fixing testSymbolTableM6812 is on my todo list (it needs a change
in PharoCore)

On Jan 10, 2010, at 14:05 , Mariano Martinez Peck wrote:

>
>
> On Sun, Jan 10, 2010 at 11:34 AM, Adrian Lienhard <[hidden email]>
> wrote:
>
> On Jan 9, 2010, at 22:32 , Mariano Martinez Peck wrote:
>
> > Thanks Benoit for the report and taking the time to run all the
> > tests. I
> > already knew that there are a lot failing tests. Unfortunately,
> > there is not
> > too much I can do:
> >
> > 1) Maintainers of packages with failures can tell me if they are
> > failing for
> > "my fault". I mean,  because I don't load a dependency or something
> > like
> > that. And if this is the case, I can fix that.
> >
> > 2) I can remove all the packages that have failing tests -> I think
> > we will
> > load very few packages.
> >
> > 3) We should ask maintainers to fix them. Of course, there are
> > packages that
> > even don't have maintainers.
> >
> > thoughts about this ?
>
> Some time ago I individually talked with each maintainer and
> eventually we managed to get all tests pass. That was with the
> previous build of the Pharo image that Damien did. Now, I don't know
> which additional tests you have loaded (?) but either these need to be
> fixed or we should not load them. We want all tests to be green for
> the release.
>
>
> Adrian: Most of the failing tests are from OB. Someone said Lukas
> made all those tests green, but they are commited in his repo.
> Someone should merge that with the wiresong repo. If no one merge
> that, I don't know what to do: or remove them or keep them.
>
> The only 3 tests no related with OB that are failing are:
>
> ObjectFinalizerTests >> testFinalizationOfEquals
>
> This one is failure, but running it again, it is green. Any idea?
>
> ReleaseTest >> testUndeclared
>
> failes.
>
> WeakSetInspectorTest >> testSymbolTableM6812
>
> Related to NewInspector. I cc Frederic.
>
> Cheers
>
> Mariano
>
> Cheers,
> Adrian
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Hi,

Moose loads well and the tests work as expected.

I will try to work with this image for a while, although it kills me
not to see the packages :).

Cheers,
Doru

On 9 Jan 2010, at 18:13, Mariano Martinez Peck wrote:

> Hi Folks/Beta-Testers!
>
> I have prepare a new PharoDev image. This image, has same
> differences with the previous ones that you should know:
>
> 1) This is the first Dev image I ever prepare. I adapt to Mac OS
> Damien's bash scripts to build them and I also cleanup all the
> Squeak stuff from those bash scripts. So, maybe there are some
> problems. Forgive me if this is the case. I would like you to check,
> not only the Image in itself but also the zip. The package.txt,
> changelog, the fonts, etc.
>
> 2) This image puts TrueType fonts again. We won't put StrikeFonts or
> DejaVu package until there is big bug with them. We know those fonts
> are faster, but still a bit buggy. If you fix those issues, cool!
>
> 3) This image DOES NOT include O2. I know there are a lot of people
> who use it (mostly in Moose), but unfortunately, this was a decision
> taken. O2 depends and overrides OB making this more unstable
> sometimes. The same as the TrueType, we will put O2 again when this
> can be perfectly load in a PharoCore image without anything about OB.
> Sorry, but we rather affect only O2 users and not all. If you want
> packages support, then help in O2 development.
>
> 4) In previous Dev images only tests from PharoCore were included.
> Now, it also includes the tests from the external packages loaded.
>
> 5) This image was build using Metacello configurations. If you want,
> compare the installScript.st from this image to the previous one.
>
> 6) There is no Web image this time. If you want to install Seaside
> 2.8.4 evaluate:
>
> Gofer new
>     squeaksource: 'MetacelloRepository';
>     package: 'ConfigurationOfSeaside28';
>     load.
>
> (Smalltalk at: #ConfigurationOfSeaside28) load
>
> And if you want Seaside 3.0 evaluate:
>
> Gofer new
>     squeaksource: 'MetacelloRepository';
>     package: 'ConfigurationOfSeaside30';
>     load.
>
> (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
>
> However, I am not sure if this is perfectly working in Pharo.
>
>
>
> Ok .... Here is the link:  https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1.zip
>
> I will wait a couple of days now and I will also start to use this
> image for my development. If there are issues, report them. If we
> have big issues, this image is not release. On the other hand, if it
> works well, we release it.

> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
www.tudorgirba.com

"Problem solving should be concentrated on describing
the problem in a way that is relevant for the solution."

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>> Lukas is the official maintainer of the OB package for Pharo.
>> Therefore I assume OB should be loaded from his repository... Lukas?
>
> Wait...this is not a little decision. This is really big. Because a lot of
> people commits stuff to wiresong repository. How this will be merged ? where
> people that wants to contribute to OB should commit ?

You ask a maintainer to pull your changes from your or a separate
public repository. Like about any other open-source project does.
Linux. Pharo. Seaside.

It does not work when everybody publishes random changes to a
repository that everybody else is pulling from. Even if this looks
like really open open open-source, it is the inferno. This is how you
can turn in no time an excellent piece of software with hundreds of
tests into battlefield of bugs, broken tests, and messed up design.

Lukas

-
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________

Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project