Re: [Pharo-users] Seaside not installing

I just uploaded a new Metacello config that, I hope, fixes a reference
to Cryptography package that for some reason stopped working.

After changing this I had 1010 (all) Seaside-Tests passing.


Name: ConfigurationOfSeaside3-EstebanMaringolo.312
Author: EstebanMaringolo
Time: 13 September 2016, 1:04:36.108636 am
UUID: 57a8dff5-a6da-4e91-be29-7628e93171ae
Ancestors: ConfigurationOfSeaside3-pmm.311

Fixes #baseline320security: that had a specific spec and package
reference for Pharo that wasn't working. Now it uses the same
#squeakCommon spec.

Regards,

Esteban A. Maringolo


2016-09-12 23:22 GMT-03:00 Ben Coman <[hidden email]>: _______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

On Tue, Sep 13, 2016 at 6:06 AM, Esteban A. Maringolo
<[hidden email]> wrote:
Not really excited about the fix. Loading Cryptography instead of
Cryptography-Pharo into Pharo causes a  issues like undeclareds and
dirty system packages.

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

2016-09-13 2:22 GMT-03:00 Philippe Marschall <[hidden email]>:
> On Tue, Sep 13, 2016 at 6:06 AM, Esteban A. Maringolo
> <[hidden email]> wrote:
>> I just uploaded a new Metacello config that, I hope, fixes a reference
>> to Cryptography package that for some reason stopped working.
>>
>> After changing this I had 1010 (all) Seaside-Tests passing.

>> Name: ConfigurationOfSeaside3-EstebanMaringolo.312

>> Fixes #baseline320security: that had a specific spec and package
>> reference for Pharo that wasn't working. Now it uses the same
>> #squeakCommon spec.
>
> Not really excited about the fix. Loading Cryptography instead of
> Cryptography-Pharo into Pharo causes a  issues like undeclareds and
> dirty system packages.

I didn't notice that, sorry. You're right.

I could configure it and make it load arranging the spec definitions
in a different order, but ended up duplicating some specs for #pharo
and #squeak. I'll test it in a clean image to see if it works.

Regards,


Esteban A. Maringolo
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

On Tue, Sep 13, 2016 at 8:04 AM, Esteban A. Maringolo
<[hidden email]> wrote:
That's probably the easiest way.

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Hi there, please read below,

2016-09-13 9:33 GMT-03:00 Philippe Marschall <[hidden email]>:
> On Tue, Sep 13, 2016 at 8:04 AM, Esteban A. Maringolo
> <[hidden email]> wrote:

>>> Not really excited about the fix. Loading Cryptography instead of
>>> Cryptography-Pharo into Pharo causes a  issues like undeclareds and
>>> dirty system packages.
>>
>> I didn't notice that, sorry. You're right.

The Cryptography package for Pharo was a mess, overriding system
classes, methods and hence dirtying packages.
I created a new package specific for Pharo (5.0) based on the latest
from SqueakSource, and commited it in SmalltalkHub.


So... I made some changes to the config and I think I know what
caused the errors...

To start with baseline320security: was defining a group named "Tests",
which I think was a misnomer considering how other special group of
packages were named, so I renamed it to "Security Tests".

So loading "Tests" was loading Seaside-Security-Tests, which failed...

>> I could configure it and make it load arranging the spec definitions
>> in a different order, but ended up duplicating some specs for #pharo
>> and #squeak. I'll test it in a clean image to see if it works.
>
> That's probably the easiest way.

Now baseline320security: uses SmalltalkHub for the Cryptography in
Pharo and SqueakSource for Squeak.

Also, in Seaside-Core-pmm.875 the  WAKeyGenerator class>>current: was
removed (probably because it had no users if the Seaside-Security
package wasn't installed), so whenever you installed Seaside-Security
it tried to initialize a secure generator defining a secure singleton
for WAKeyGenerator and it failed.

So I commited a new version that puts the accessor back, and also made
the change in Seaside-Core-EstebanMaringolo.870 that affects the
current stable version.

Name: Seaside-Core-EstebanMaringolo.881
Ancestors: Seaside-Core-pmm.880, Seaside-Core-EstebanMaringolo.870

I loaded both #bleedingEdge and #stable in a clean image and the
Seaside-Security are green for both branches, and al tests remain
green in the #stable version.

I hope this doesn't break anything else.

Best Regards,

Esteban A. Maringolo
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

> I created a new package specific for Pharo (5.0) based on the latest
> from SqueakSource, and commited it in SmalltalkHub.

Thanks a lot for that work!

> To start with baseline320security: was defining a group named "Tests",
> which I think was a misnomer considering how other special group of
> packages were named, so I renamed it to "Security Tests”.

You are right that this will cause issues when loading ‘Tests’ on Windows, so splitting it into a separate group seems like the right thing to do.

Just a remark: you updated version320SqueakCommon method, but really we need to create a new version.
The Seaside-Core package in that version now upgrades it in all 3.2.x versions.
I made the changes and commit a new configuration.

I’ll check now what needs to happen to fix a new version.

Johan

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

In the end, I did mark a new version 3.2.1 because as a user of a version I should not be exposed to silent package updates.
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

I agree with that. I didn't know how the versions were defined with such big definitions, I'll look at the code to see how you did it.

What I don't know is what broke the installation.

Can you grant me access to the Jenkins and GH repo?

Regards!

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev