[Pharo-dev] OpenSSL binding Re: About strange email related to smalltalkhub read-only on squeak-dev

[Pierce Ng]

On Tue, Jun 02, 2020 at 11:17:30AM +0200, Norbert Hartl wrote:
> PierceNg has an implementation that implements a subset of openssl.
> This implementation is modeled after the library so lots of class
> methods. I'd prefer to have something more object model like. 

A very small subset currently, as my original need was to create an X509
request in code. PRs welcome.

  https://github.com/PierceNg/OpenSSL-Pharo

Pierce

Re: [Pharo-dev] #(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4))

[Torsten Bergmann]

Hi Stef,
 
from the (incomplete) sample it is unclear what is really needed:
 
 1. Both return the same result: #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4))  which is 
syntactically equal to #(#(1 1 1) #(2 2 2) #(3 3 3) #(4 4 4))

    So why did you leave out the # for the contained sub-array with 2's and 3's?

 2. When the result is equal in both examples why give a different argument 
like 3 and 4? 

 3. What about edge case inputs like:   #(1 1 1 2 2 2 4 4 4)          not 
having sucessors/predecessor order
                                        #(2 2 2 1 1 1 3 3 3 4 4 4)    with 
different order (not ascending)
                                        #(1 1 1 1 2 2 2 3 3 3 4 4 4)  where 1 
is included more often than the other   

 4. ...


Nonetheless: the closest that might possibly be of use is #groupByRuns: message 


    #(1 1 1 2 2 2 3 3 3 4 4 4) groupByRuns: [:e | e ]    ->  #(#(1 1 1) #(2 2 
2) #(3 3 3) #(4 4 4))

Have fun
T.
  

Gesendet: Mittwoch, 03. Juni 2020 um 22:53 Uhr
Von: "Stéphane Ducasse" 
An: "Pharo Development List" 
Betreff: [Pharo-dev] #(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 
3) #(4 4 4))

Hi guys 
 
do you know if we have around a method doing the following?
 
#(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) 
 
it could also be another one
 
#(1 1 1 2 2 2 3 3 3 4 4 4) . 4 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) 
 
S
 


Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org[http://www.pharo.org] 
03 59 35 87 52
Assistant: Aurore Dalle 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza

Villeneuve d'Ascq 59650
France

Re: [Pharo-dev] #(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4))

[Todd Blanchard via Pharo-dev]

--- Begin Message ---
I don't understand your intent.

Do they group together because they have the same value or do they just get 
grouped into subgroups of size three or do they get grouped as runs?

This works:

#(1 1 1 2 2 2 3 3 3 4 4 4) groupByRuns:  [ :ea | ea ] -> #(#(1 1 1) (2 2 2) (3 
3 3) #(4 4 4)) 

> On Jun 3, 2020, at 1:53 PM, Stéphane Ducasse  
> wrote:
> 
> Hi guys 
> 
> do you know if we have around a method doing the following?
> 
> #(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) 
> 
> it could also be another one
> 
> #(1 1 1 2 2 2 3 3 3 4 4 4) . 4 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) 
> 
> S
> 
> 
> Stéphane Ducasse
> http://stephane.ducasse.free.fr  / 
> http://www.pharo.org  
> 03 59 35 87 52
> Assistant: Aurore Dalle 
> FAX 03 59 57 78 50
> TEL 03 59 35 86 16
> S. Ducasse - Inria
> 40, avenue Halley, 
> Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
> Villeneuve d'Ascq 59650
> France
> 

--- End Message ---

[Pharo-dev] #(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4))

[Stéphane Ducasse]

Hi guys 

do you know if we have around a method doing the following?

#(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) 

it could also be another one

#(1 1 1 2 2 2 3 3 3 4 4 4) . 4 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) 

S


Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org 
03 59 35 87 52
Assistant: Aurore Dalle 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France

[Pharo-dev] [Pharo 9.0] Build #331: Rules checking Tests should be in package SUnit-Rules

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #331 was: FAILURE.

The Pull Request #6304 was integrated: "Rules checking Tests should be in 
package SUnit-Rules"
Pull request url: https://github.com/pharo-project/pharo/pull/6304

Issue Url: https://github.com/pharo-project/pharo/issues/6303
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo9.0/331/

[Pharo-dev] [Pharo 9.0] Build #330: Deprecated Slot

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #330 was: SUCCESS.

The Pull Request #6475 was integrated: "Deprecated Slot"
Pull request url: https://github.com/pharo-project/pharo/pull/6475

Issue Url: https://github.com/pharo-project/pharo/issues/DeprecatedSlot
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo9.0/330/

[Pharo-dev] [Pharo 8.0] Build #1138: 6420-Backport-5482-to-Pharo8

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #1138 was: SUCCESS.

The Pull Request #6427 was integrated: "6420-Backport-5482-to-Pharo8"
Pull request url: https://github.com/pharo-project/pharo/pull/6427

Issue Url: https://github.com/pharo-project/pharo/issues/6420
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/1138/

[Pharo-dev] [Pharo 9.0] Build #329: Fixes changes file flushing issue

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #329 was: FAILURE.

The Pull Request #6468 was integrated: "Fixes changes file flushing issue"
Pull request url: https://github.com/pharo-project/pharo/pull/6468

Issue Url: https://github.com/pharo-project/pharo/issues/6063
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo9.0/329/

[Pharo-dev] [Pharo 9.0] Build #328: Fix #6472

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #328 was: FAILURE.

The Pull Request #6473 was integrated: "Fix #6472"
Pull request url: https://github.com/pharo-project/pharo/pull/6473

Issue Url: https://github.com/pharo-project/pharo/issues/fix/6472
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo9.0/328/

Re: [Pharo-dev] [Pharo-users] About strange email related to smalltalkhub read-only on squeak-dev

[Norbert Hartl]

Stef,

that is a second problem. The main problem to me is solving the crypto stuff 
once and for all. And then I would like to know why people like Ron say things 
like this.

But yes, shouldn't go without explanation/reaction!

Norbert


> Am 03.06.2020 um 00:13 schrieb Stéphane Ducasse :
> 
> What I do not like is that people say " group but they keep kicking me out of 
> their mailing list ” when this is absolutely not true!
> 
> We can discuss and can argue even violently but we do not lie. 
> 
> S. 
> 
> 
> 
>> On 31 May 2020, at 19:38, Bruce O'Neel > > wrote:
>> 
>> 
>> Hi,
>> 
>> So addressing only the crypto software issue and with the caveat that I am 
>> also not a lawyer but I have had to deal with certain aspects of this in the 
>> past
>> 
>> Crypto software is one of those bizarre dual use items in terms of arms 
>> imports and exports.  While we as geeks just think of this is software or 
>> mathematics and might be confused as to why governments care, governments do 
>> care deeply about this.  And their way of expressing how much they care 
>> about this issue is by passing laws and prosecuting folks.
>> 
>> One of the easiest ways to get in trouble is for one to make the software 
>> available to residents and/or citizens of certain countries as well as 
>> available to people on a long list kept by different governments.  We can 
>> have a long debate about the morality of this concept but those who make the 
>> laws have decided that is the law.  And often these laws are crafted such 
>> that the executive can change important details on short notice and that 
>> puts the risk of prosecution at the whims of different world leaders.  
>> 
>> The license that the software is released under is not important.   
>> 
>> What Ron is stating is that squeak source supplied some additional 
>> protections to prevent accidentally making the software available to folks 
>> who the US feels should not have access.
>> 
>> If you have moved the software to another hosting provider without the 
>> permission or knowledge of the author, and therefore the owner of the 
>> software, you have put that person at additional risk.  In addition you and 
>> the hosting provider are taking on additional risk.
>> 
>> If it was moved to GitHub I strongly recommend reviewing their policies on 
>> trade controls and what risks you assume.
>> 
>> https://help.github.com/en/github/site-policy/github-and-trade-controls 
>> 
>> 
>> Finally I would strongly recommend talking to a competent legal advisor who 
>> is deeply familiar with the details of these laws.  They are complex and 
>> highly variable between different parts of the world.
>> 
>> I know this seems like a lot of trouble and wasted time but you can spend a 
>> giant amount of time and money defending oneself from arms trafficking 
>> charges.
>> 
>> cheers
>> 
>> bruce
>> 
>> 30 May 2020 14:43 Stéphane Ducasse > > wrote:
>> Hi all
>> 
>> This is the week-end and we worked super well yesterday during the sprint. 
>> Lot of good enhancements - Thanks a lot to all the participants. 
>> I not really happy to be forced to do it on a sunny saturday but I’m doing 
>> it to clarify points.
>> 
>> Esteban sent me this text that was posted on Squeak-Dev (I personally do not 
>> read squeak related forums because 
>> I have not the time and my focus is Pharo, its consortium, my team, my 
>> research and my family). 
>> 
>> We have to react because 
>> - We do not really at ***all** understand this email
>> - We did not kicked anybody from our mailing-list from ages - so ron is 
>> lying. In the past we even had discussion with ron - so we do not 
>> really understand. May be we got problem to log on our mailing-lists. 
>> We have no idea because we are working and not looking at such things.   
>> - When we migrated smalltalkhub to readonly we payed attention to make sure 
>> that private projects stay private.
>> We did not migrated smalltalkhub for fun. We MUST do it or it will be done 
>> by our infrastructure!
>> - Now the cryptography packages are MIT and they are public anyway. So again 
>> we do not understand anything. 
>> 
>> We do not get why Ron contacted us because we announced the migration 
>> publicly way in advance and we will keep 
>> the Smalltalkhub frozen repo for at least next 5 years. 
>> 
>> I feel really sorry to hear such kind of email because we do not want to 
>> fight with anybody. 
>> Our goal is to make sure that people can work with Pharo and expand their 
>> business and knowledge. 
>> We are working hard to make sure that people can invent their future with 
>> Pharo and people that know us personally 
>> know that we are not lying.
>> 
>> S
>> 
>> 
>> 
>>> Hi all,
>>> 
>>> I've tried to work with the Pharo group but they keep kicking me out of 
>>> their mailing list.  I've already