RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Maria Jose Esteve]

Hi

Yishay, I've already removed the ExternsJS related projects from the main 
branch and commented out all the references I've seen in the build and config 
files (I haven't removed them so I don't redo the work in the future).
I have detached the ExternsJS project to the "feature/ExternsJS" branch in the 
current state so I can continue working on it. (Alina, for you)
Then I did a build of the SDK with maven:
mvn clean install -DskipTests -P option-with-sass-compile,option-with-swf 
-Drat.skip=true

And also a build with ant:
ant all -Dbuild.noprompt=true -Drelease.target=true -Dskip-tests=true

Everything seems to work (I've compiled a couple of my projects fine).

As I said in the previous post, my work was in another branch 
"feature/ExternsJS_InspireTree" I got stuck with the pom creation for the maven 
compilation (in the main branch only the ant build was configured, I think I 
remember).

I hope I didn't forget anything.

Thx.

Hiedra

-Mensaje original-
De: Yishay Weiss  
Enviado el: miércoles, 9 de marzo de 2022 16:33
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

No need to apologize, we've all been there. These configurations are tricky.

Let me know when you've reverted it and I'll start a new release. No rush as I 
won't have time to do it tonight anyway.

From: Maria Jose Esteve<mailto:mjest...@iest.com>
Sent: Wednesday, March 9, 2022 5:16 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Yes. At the time, I created a branch but I don't remember why Alina uploaded 
her copy.
I'm going to try to remove it. I hope to do it correctly because I remember 
that we "wasted Harb's time" with the configuration and unit tests (sorry Harb).

I'm sorry, could you do it tonight?

Hiedra

-Mensaje original-----
De: Yishay Weiss  Enviado el: miércoles, 9 de marzo de 
2022 15:52
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Probably. Maria, maybe you should remove the project and put it in a branch 
until it is configured properly?


From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Wednesday, March 9, 2022 4:34 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Does this warrant another RC? (My gut says yes.)

> On Mar 9, 2022, at 4:23 PM, Maria Jose Esteve  wrote:
>
> Maybe it is because the ExternJS project is half-configured. I have replied 
> in the other thread.
>
> Hiedra
>
> -Mensaje original-----
> De: Harbs 
> Enviado el: miércoles, 9 de marzo de 2022 14:59
> Para: Apache Royale Development 
> Asunto: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>
> Any clues why this file shows up?
>
> B 
> /Users/harbs/Desktop/release_test/apache-royale-0.9.9-bin-js-swf/royale-asjs/frameworks/js/libs/ExternsJSJS.swc
>
> AFAIK, there's shouldn't be binaries in the release artifacts.
>
>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com wrote:
>>
>> This is the discussion thread.
>>
>> Thanks,
>> Yishay Weiss
>

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Yishay Weiss]

No need to apologize, we’ve all been there. These configurations are tricky.

Let me know when you’ve reverted it and I’ll start a new release. No rush as I 
won’t have time to do it tonight anyway.

From: Maria Jose Esteve<mailto:mjest...@iest.com>
Sent: Wednesday, March 9, 2022 5:16 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Yes. At the time, I created a branch but I don't remember why Alina uploaded 
her copy.
I'm going to try to remove it. I hope to do it correctly because I remember 
that we "wasted Harb's time" with the configuration and unit tests (sorry Harb).

I'm sorry, could you do it tonight?

Hiedra

-Mensaje original-
De: Yishay Weiss 
Enviado el: miércoles, 9 de marzo de 2022 15:52
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Probably. Maria, maybe you should remove the project and put it in a branch 
until it is configured properly?


From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Wednesday, March 9, 2022 4:34 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Does this warrant another RC? (My gut says yes.)

> On Mar 9, 2022, at 4:23 PM, Maria Jose Esteve  wrote:
>
> Maybe it is because the ExternJS project is half-configured. I have replied 
> in the other thread.
>
> Hiedra
>
> -Mensaje original-
> De: Harbs 
> Enviado el: miércoles, 9 de marzo de 2022 14:59
> Para: Apache Royale Development 
> Asunto: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>
> Any clues why this file shows up?
>
> B 
> /Users/harbs/Desktop/release_test/apache-royale-0.9.9-bin-js-swf/royale-asjs/frameworks/js/libs/ExternsJSJS.swc
>
> AFAIK, there's shouldn't be binaries in the release artifacts.
>
>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com wrote:
>>
>> This is the discussion thread.
>>
>> Thanks,
>> Yishay Weiss
>

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Yishay Weiss]

Below is the output for the methods I used to search for it, so I think we’re 
good.

C:\dev\flexjs\royale-asjs>gpg --keyserver https://pgp.mit.edu/ --search-keys 
F4CE36E979325A6221706DB0E86EF353F54FE093
gpg: data source: https://pgp.mit.edu:443
(1) Yishay Weiss 
  4096 bit RSA key E86EF353F54FE093, created: 2021-04-02, expires: 
2026-04-02
Keys 1-1 of 1 for "F4CE36E979325A6221706DB0E86EF353F54FE093".  Enter number(s), 
N)ext, or Q)uit > q
gpg: error searching keyserver: Operation cancelled
gpg: keyserver search failed: Operation cancelled

C:\dev\flexjs\royale-asjs>gpg --keyserver https://pgp.mit.edu/ --search-keys 
yish...@apache.org
gpg: data source: https://pgp.mit.edu:443
(1) Yishay Weiss 
  4096 bit RSA key E86EF353F54FE093, created: 2021-04-02, expires: 
2026-04-02

From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Wednesday, March 9, 2022 5:07 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

I searched using yish...@apache.org and I still get nothing.

Dunno...

> On Mar 9, 2022, at 4:53 PM, Yishay Weiss  wrote:
>
> It’s published. It’s the same key that was used for the previous release. I 
> think you just searched with the wrong email.
>
> From: Harbs<mailto:harbs.li...@gmail.com>
> Sent: Wednesday, March 9, 2022 3:54 PM
> To: Apache Royale Development<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>
> I imported your key manually, and that worked, but you really should publish 
> it. Manual imports shouldn’t be necessary.
>
>> On Mar 9, 2022, at 3:33 PM, Yishay Weiss  wrote:
>>
>> If you look here [1], then you need to import the last one (one after 
>> yours). You can search the fingerprint [2].
>>
>> [1] https://dist.apache.org/repos/dist/release/royale/KEYS
>>
>> [2] F4CE36E979325A6221706DB0E86EF353F54FE093
>>
>> From: Yishay Weiss<mailto:yishayj...@hotmail.com>
>> Sent: Wednesday, March 9, 2022 3:18 PM
>> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>> Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>>
>> My mistake, it was created on 2021-04-02, so I couldn’t have been published 
>> on April 13, 2020.
>>
>> How did you determine that it was the most current published key?
>>
>>
>>
>> From: Harbs<mailto:harbs.li...@gmail.com>
>> Sent: Wednesday, March 9, 2022 3:07 PM
>> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>>
>> Well, I don’t know why the gpg check is failing for me. I’ll wait until 
>> someone else checks the release. If it works for others, I’ll assume it’s a 
>> problem locally for me and see if I can fix it...
>>
>>> On Mar 9, 2022, at 1:13 PM, Yishay Weiss  wrote:
>>>
>>> No, that’s the one
>>>
>>> From: Harbs<mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>
>>> Sent: Wednesday, March 9, 2022 12:48 PM
>>> To: Apache Royale Development<mailto:dev@royale.apache.org 
>>> <mailto:dev@royale.apache.org>>
>>> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>>>
>>> I seem to have your key from April 13, 2020. That seems to be the most 
>>> current published key.
>>>
>>> Did you use a newer one?
>>>
>>>> On Mar 9, 2022, at 12:43 PM, Harbs  wrote:
>>>>
>>>> I got an error here:
>>>>
>>>> check-sigs:
>>>>
>>>> gpg_check:
>>>> gpg: Signature made Tue Mar  8 08:59:15 2022 IST
>>>> gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
>>>> gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
>>>> gpg: Total number processed: 1
>>>> gpg:   w/o user IDs: 1
>>>> gpg: Can't check signature: No public key
>>>>
>>>> Did you not publish your key, or do I need to import it?
>>>>
>>>>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com 
>>>>> <mailto:apacheroyal...@gmail.com> <mailto:apacheroyal...@gmail.com 
>>>>> <mailto:apacheroyal...@gmail.com>> wrote:
>>>>>
>>>>> This is the discussion thread.
>>>>>
>>>>> Thanks,
>>>>> Yishay Weiss
>>
>

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Maria Jose Esteve]

Yes. At the time, I created a branch but I don't remember why Alina uploaded 
her copy.
I'm going to try to remove it. I hope to do it correctly because I remember 
that we "wasted Harb's time" with the configuration and unit tests (sorry Harb).

I'm sorry, could you do it tonight?

Hiedra

-Mensaje original-
De: Yishay Weiss  
Enviado el: miércoles, 9 de marzo de 2022 15:52
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Probably. Maria, maybe you should remove the project and put it in a branch 
until it is configured properly?


From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Wednesday, March 9, 2022 4:34 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Does this warrant another RC? (My gut says yes.)

> On Mar 9, 2022, at 4:23 PM, Maria Jose Esteve  wrote:
>
> Maybe it is because the ExternJS project is half-configured. I have replied 
> in the other thread.
>
> Hiedra
>
> -Mensaje original-
> De: Harbs 
> Enviado el: miércoles, 9 de marzo de 2022 14:59
> Para: Apache Royale Development 
> Asunto: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>
> Any clues why this file shows up?
>
> B 
> /Users/harbs/Desktop/release_test/apache-royale-0.9.9-bin-js-swf/royale-asjs/frameworks/js/libs/ExternsJSJS.swc
>
> AFAIK, there's shouldn't be binaries in the release artifacts.
>
>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com wrote:
>>
>> This is the discussion thread.
>>
>> Thanks,
>> Yishay Weiss
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Harbs]

I searched using yish...@apache.org and I still get nothing.

Dunno...

> On Mar 9, 2022, at 4:53 PM, Yishay Weiss  wrote:
> 
> It’s published. It’s the same key that was used for the previous release. I 
> think you just searched with the wrong email.
> 
> From: Harbs<mailto:harbs.li...@gmail.com>
> Sent: Wednesday, March 9, 2022 3:54 PM
> To: Apache Royale Development<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
> 
> I imported your key manually, and that worked, but you really should publish 
> it. Manual imports shouldn’t be necessary.
> 
>> On Mar 9, 2022, at 3:33 PM, Yishay Weiss  wrote:
>> 
>> If you look here [1], then you need to import the last one (one after 
>> yours). You can search the fingerprint [2].
>> 
>> [1] https://dist.apache.org/repos/dist/release/royale/KEYS
>> 
>> [2] F4CE36E979325A6221706DB0E86EF353F54FE093
>> 
>> From: Yishay Weiss<mailto:yishayj...@hotmail.com>
>> Sent: Wednesday, March 9, 2022 3:18 PM
>> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>> Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>> 
>> My mistake, it was created on 2021-04-02, so I couldn’t have been published 
>> on April 13, 2020.
>> 
>> How did you determine that it was the most current published key?
>> 
>> 
>> 
>> From: Harbs<mailto:harbs.li...@gmail.com>
>> Sent: Wednesday, March 9, 2022 3:07 PM
>> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>> 
>> Well, I don’t know why the gpg check is failing for me. I’ll wait until 
>> someone else checks the release. If it works for others, I’ll assume it’s a 
>> problem locally for me and see if I can fix it...
>> 
>>> On Mar 9, 2022, at 1:13 PM, Yishay Weiss  wrote:
>>> 
>>> No, that’s the one
>>> 
>>> From: Harbs<mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>
>>> Sent: Wednesday, March 9, 2022 12:48 PM
>>> To: Apache Royale Development<mailto:dev@royale.apache.org 
>>> <mailto:dev@royale.apache.org>>
>>> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>>> 
>>> I seem to have your key from April 13, 2020. That seems to be the most 
>>> current published key.
>>> 
>>> Did you use a newer one?
>>> 
>>>> On Mar 9, 2022, at 12:43 PM, Harbs  wrote:
>>>> 
>>>> I got an error here:
>>>> 
>>>> check-sigs:
>>>> 
>>>> gpg_check:
>>>> gpg: Signature made Tue Mar  8 08:59:15 2022 IST
>>>> gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
>>>> gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
>>>> gpg: Total number processed: 1
>>>> gpg:   w/o user IDs: 1
>>>> gpg: Can't check signature: No public key
>>>> 
>>>> Did you not publish your key, or do I need to import it?
>>>> 
>>>>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com 
>>>>> <mailto:apacheroyal...@gmail.com> <mailto:apacheroyal...@gmail.com 
>>>>> <mailto:apacheroyal...@gmail.com>> wrote:
>>>>> 
>>>>> This is the discussion thread.
>>>>> 
>>>>> Thanks,
>>>>> Yishay Weiss
>> 
> 

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Yishay Weiss]

It’s published. It’s the same key that was used for the previous release. I 
think you just searched with the wrong email.

From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Wednesday, March 9, 2022 3:54 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

I imported your key manually, and that worked, but you really should publish 
it. Manual imports shouldn’t be necessary.

> On Mar 9, 2022, at 3:33 PM, Yishay Weiss  wrote:
>
> If you look here [1], then you need to import the last one (one after yours). 
> You can search the fingerprint [2].
>
> [1] https://dist.apache.org/repos/dist/release/royale/KEYS
>
> [2] F4CE36E979325A6221706DB0E86EF353F54FE093
>
> From: Yishay Weiss<mailto:yishayj...@hotmail.com>
> Sent: Wednesday, March 9, 2022 3:18 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>
> My mistake, it was created on 2021-04-02, so I couldn’t have been published 
> on April 13, 2020.
>
> How did you determine that it was the most current published key?
>
>
>
> From: Harbs<mailto:harbs.li...@gmail.com>
> Sent: Wednesday, March 9, 2022 3:07 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>
> Well, I don’t know why the gpg check is failing for me. I’ll wait until 
> someone else checks the release. If it works for others, I’ll assume it’s a 
> problem locally for me and see if I can fix it...
>
>> On Mar 9, 2022, at 1:13 PM, Yishay Weiss  wrote:
>>
>> No, that’s the one
>>
>> From: Harbs<mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>
>> Sent: Wednesday, March 9, 2022 12:48 PM
>> To: Apache Royale Development<mailto:dev@royale.apache.org 
>> <mailto:dev@royale.apache.org>>
>> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>>
>> I seem to have your key from April 13, 2020. That seems to be the most 
>> current published key.
>>
>> Did you use a newer one?
>>
>>> On Mar 9, 2022, at 12:43 PM, Harbs  wrote:
>>>
>>> I got an error here:
>>>
>>> check-sigs:
>>>
>>> gpg_check:
>>> gpg: Signature made Tue Mar  8 08:59:15 2022 IST
>>> gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
>>> gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
>>> gpg: Total number processed: 1
>>> gpg:   w/o user IDs: 1
>>> gpg: Can't check signature: No public key
>>>
>>> Did you not publish your key, or do I need to import it?
>>>
>>>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com 
>>>> <mailto:apacheroyal...@gmail.com> <mailto:apacheroyal...@gmail.com 
>>>> <mailto:apacheroyal...@gmail.com>> wrote:
>>>>
>>>> This is the discussion thread.
>>>>
>>>> Thanks,
>>>> Yishay Weiss
>

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Yishay Weiss]

Probably. Maria, maybe you should remove the project and put it in a branch 
until it is configured properly?


From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Wednesday, March 9, 2022 4:34 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Does this warrant another RC? (My gut says yes.)

> On Mar 9, 2022, at 4:23 PM, Maria Jose Esteve  wrote:
>
> Maybe it is because the ExternJS project is half-configured. I have replied 
> in the other thread.
>
> Hiedra
>
> -Mensaje original-
> De: Harbs 
> Enviado el: miércoles, 9 de marzo de 2022 14:59
> Para: Apache Royale Development 
> Asunto: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>
> Any clues why this file shows up?
>
> B 
> /Users/harbs/Desktop/release_test/apache-royale-0.9.9-bin-js-swf/royale-asjs/frameworks/js/libs/ExternsJSJS.swc
>
> AFAIK, there’s shouldn’t be binaries in the release artifacts.
>
>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com wrote:
>>
>> This is the discussion thread.
>>
>> Thanks,
>> Yishay Weiss
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Harbs]

Does this warrant another RC? (My gut says yes.)

> On Mar 9, 2022, at 4:23 PM, Maria Jose Esteve  wrote:
> 
> Maybe it is because the ExternJS project is half-configured. I have replied 
> in the other thread.
> 
> Hiedra
> 
> -Mensaje original-
> De: Harbs  
> Enviado el: miércoles, 9 de marzo de 2022 14:59
> Para: Apache Royale Development 
> Asunto: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
> 
> Any clues why this file shows up?
> 
> B 
> /Users/harbs/Desktop/release_test/apache-royale-0.9.9-bin-js-swf/royale-asjs/frameworks/js/libs/ExternsJSJS.swc
> 
> AFAIK, there’s shouldn’t be binaries in the release artifacts.
> 
>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com wrote:
>> 
>> This is the discussion thread.
>> 
>> Thanks,
>> Yishay Weiss
> 

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Maria Jose Esteve]

Maybe it is because the ExternJS project is half-configured. I have replied in 
the other thread.

Hiedra

-Mensaje original-
De: Harbs  
Enviado el: miércoles, 9 de marzo de 2022 14:59
Para: Apache Royale Development 
Asunto: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Any clues why this file shows up?

B 
/Users/harbs/Desktop/release_test/apache-royale-0.9.9-bin-js-swf/royale-asjs/frameworks/js/libs/ExternsJSJS.swc

AFAIK, there’s shouldn’t be binaries in the release artifacts.

> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com wrote:
> 
> This is the discussion thread.
> 
> Thanks,
> Yishay Weiss

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Yishay Weiss]

Try yish...@apache.org


From: Harbs 
Sent: Wednesday, March 9, 2022 3:49:22 PM
To: dev@royale.apache.org 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

gpg2 --keyserver https://pgp.mit.edu/ --search-keys yishayj...@hotmail.com

> On Mar 9, 2022, at 3:18 PM, Yishay Weiss  wrote:
>
> My mistake, it was created on 2021-04-02, so I couldn’t have been published 
> on April 13, 2020.
>
> How did you determine that it was the most current published key?
>
>
>
> From: Harbs<mailto:harbs.li...@gmail.com>
> Sent: Wednesday, March 9, 2022 3:07 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>
> Well, I don’t know why the gpg check is failing for me. I’ll wait until 
> someone else checks the release. If it works for others, I’ll assume it’s a 
> problem locally for me and see if I can fix it...
>
>> On Mar 9, 2022, at 1:13 PM, Yishay Weiss  wrote:
>>
>> No, that’s the one
>>
>> From: Harbs<mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>
>> Sent: Wednesday, March 9, 2022 12:48 PM
>> To: Apache Royale Development<mailto:dev@royale.apache.org 
>> <mailto:dev@royale.apache.org>>
>> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>>
>> I seem to have your key from April 13, 2020. That seems to be the most 
>> current published key.
>>
>> Did you use a newer one?
>>
>>> On Mar 9, 2022, at 12:43 PM, Harbs  wrote:
>>>
>>> I got an error here:
>>>
>>> check-sigs:
>>>
>>> gpg_check:
>>> gpg: Signature made Tue Mar  8 08:59:15 2022 IST
>>> gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
>>> gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
>>> gpg: Total number processed: 1
>>> gpg:   w/o user IDs: 1
>>> gpg: Can't check signature: No public key
>>>
>>> Did you not publish your key, or do I need to import it?
>>>
>>>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com 
>>>> <mailto:apacheroyal...@gmail.com> <mailto:apacheroyal...@gmail.com 
>>>> <mailto:apacheroyal...@gmail.com>> wrote:
>>>>
>>>> This is the discussion thread.
>>>>
>>>> Thanks,
>>>> Yishay Weiss
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Harbs]

Any clues why this file shows up?

B 
/Users/harbs/Desktop/release_test/apache-royale-0.9.9-bin-js-swf/royale-asjs/frameworks/js/libs/ExternsJSJS.swc

AFAIK, there’s shouldn’t be binaries in the release artifacts.

> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com wrote:
> 
> This is the discussion thread.
> 
> Thanks,
> Yishay Weiss

Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Harbs]

I imported your key manually, and that worked, but you really should publish 
it. Manual imports shouldn’t be necessary.

> On Mar 9, 2022, at 3:33 PM, Yishay Weiss  wrote:
> 
> If you look here [1], then you need to import the last one (one after yours). 
> You can search the fingerprint [2].
> 
> [1] https://dist.apache.org/repos/dist/release/royale/KEYS
> 
> [2] F4CE36E979325A6221706DB0E86EF353F54FE093
> 
> From: Yishay Weiss<mailto:yishayj...@hotmail.com>
> Sent: Wednesday, March 9, 2022 3:18 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
> 
> My mistake, it was created on 2021-04-02, so I couldn’t have been published 
> on April 13, 2020.
> 
> How did you determine that it was the most current published key?
> 
> 
> 
> From: Harbs<mailto:harbs.li...@gmail.com>
> Sent: Wednesday, March 9, 2022 3:07 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
> 
> Well, I don’t know why the gpg check is failing for me. I’ll wait until 
> someone else checks the release. If it works for others, I’ll assume it’s a 
> problem locally for me and see if I can fix it...
> 
>> On Mar 9, 2022, at 1:13 PM, Yishay Weiss  wrote:
>> 
>> No, that’s the one
>> 
>> From: Harbs<mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>
>> Sent: Wednesday, March 9, 2022 12:48 PM
>> To: Apache Royale Development<mailto:dev@royale.apache.org 
>> <mailto:dev@royale.apache.org>>
>> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>> 
>> I seem to have your key from April 13, 2020. That seems to be the most 
>> current published key.
>> 
>> Did you use a newer one?
>> 
>>> On Mar 9, 2022, at 12:43 PM, Harbs  wrote:
>>> 
>>> I got an error here:
>>> 
>>> check-sigs:
>>> 
>>> gpg_check:
>>> gpg: Signature made Tue Mar  8 08:59:15 2022 IST
>>> gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
>>> gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
>>> gpg: Total number processed: 1
>>> gpg:   w/o user IDs: 1
>>> gpg: Can't check signature: No public key
>>> 
>>> Did you not publish your key, or do I need to import it?
>>> 
>>>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com 
>>>> <mailto:apacheroyal...@gmail.com> <mailto:apacheroyal...@gmail.com 
>>>> <mailto:apacheroyal...@gmail.com>> wrote:
>>>> 
>>>> This is the discussion thread.
>>>> 
>>>> Thanks,
>>>> Yishay Weiss
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Harbs]

gpg2 --keyserver https://pgp.mit.edu/ --search-keys yishayj...@hotmail.com

> On Mar 9, 2022, at 3:18 PM, Yishay Weiss  wrote:
> 
> My mistake, it was created on 2021-04-02, so I couldn’t have been published 
> on April 13, 2020.
> 
> How did you determine that it was the most current published key?
> 
> 
> 
> From: Harbs<mailto:harbs.li...@gmail.com>
> Sent: Wednesday, March 9, 2022 3:07 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
> 
> Well, I don’t know why the gpg check is failing for me. I’ll wait until 
> someone else checks the release. If it works for others, I’ll assume it’s a 
> problem locally for me and see if I can fix it...
> 
>> On Mar 9, 2022, at 1:13 PM, Yishay Weiss  wrote:
>> 
>> No, that’s the one
>> 
>> From: Harbs<mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>
>> Sent: Wednesday, March 9, 2022 12:48 PM
>> To: Apache Royale Development<mailto:dev@royale.apache.org 
>> <mailto:dev@royale.apache.org>>
>> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>> 
>> I seem to have your key from April 13, 2020. That seems to be the most 
>> current published key.
>> 
>> Did you use a newer one?
>> 
>>> On Mar 9, 2022, at 12:43 PM, Harbs  wrote:
>>> 
>>> I got an error here:
>>> 
>>> check-sigs:
>>> 
>>> gpg_check:
>>> gpg: Signature made Tue Mar  8 08:59:15 2022 IST
>>> gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
>>> gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
>>> gpg: Total number processed: 1
>>> gpg:   w/o user IDs: 1
>>> gpg: Can't check signature: No public key
>>> 
>>> Did you not publish your key, or do I need to import it?
>>> 
>>>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com 
>>>> <mailto:apacheroyal...@gmail.com> <mailto:apacheroyal...@gmail.com 
>>>> <mailto:apacheroyal...@gmail.com>> wrote:
>>>> 
>>>> This is the discussion thread.
>>>> 
>>>> Thanks,
>>>> Yishay Weiss
> 

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Yishay Weiss]

If you look here [1], then you need to import the last one (one after yours). 
You can search the fingerprint [2].

[1] https://dist.apache.org/repos/dist/release/royale/KEYS

[2] F4CE36E979325A6221706DB0E86EF353F54FE093

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Wednesday, March 9, 2022 3:18 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

My mistake, it was created on 2021-04-02, so I couldn’t have been published on 
April 13, 2020.

How did you determine that it was the most current published key?



From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Wednesday, March 9, 2022 3:07 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Well, I don’t know why the gpg check is failing for me. I’ll wait until someone 
else checks the release. If it works for others, I’ll assume it’s a problem 
locally for me and see if I can fix it...

> On Mar 9, 2022, at 1:13 PM, Yishay Weiss  wrote:
>
> No, that’s the one
>
> From: Harbs<mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>
> Sent: Wednesday, March 9, 2022 12:48 PM
> To: Apache Royale Development<mailto:dev@royale.apache.org 
> <mailto:dev@royale.apache.org>>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>
> I seem to have your key from April 13, 2020. That seems to be the most 
> current published key.
>
> Did you use a newer one?
>
>> On Mar 9, 2022, at 12:43 PM, Harbs  wrote:
>>
>> I got an error here:
>>
>> check-sigs:
>>
>> gpg_check:
>> gpg: Signature made Tue Mar  8 08:59:15 2022 IST
>> gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
>> gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
>> gpg: Total number processed: 1
>> gpg:   w/o user IDs: 1
>> gpg: Can't check signature: No public key
>>
>> Did you not publish your key, or do I need to import it?
>>
>>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com 
>>> <mailto:apacheroyal...@gmail.com> <mailto:apacheroyal...@gmail.com 
>>> <mailto:apacheroyal...@gmail.com>> wrote:
>>>
>>> This is the discussion thread.
>>>
>>> Thanks,
>>> Yishay Weiss

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Yishay Weiss]

My mistake, it was created on 2021-04-02, so I couldn’t have been published on 
April 13, 2020.

How did you determine that it was the most current published key?



From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Wednesday, March 9, 2022 3:07 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

Well, I don’t know why the gpg check is failing for me. I’ll wait until someone 
else checks the release. If it works for others, I’ll assume it’s a problem 
locally for me and see if I can fix it...

> On Mar 9, 2022, at 1:13 PM, Yishay Weiss  wrote:
>
> No, that’s the one
>
> From: Harbs<mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>
> Sent: Wednesday, March 9, 2022 12:48 PM
> To: Apache Royale Development<mailto:dev@royale.apache.org 
> <mailto:dev@royale.apache.org>>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
>
> I seem to have your key from April 13, 2020. That seems to be the most 
> current published key.
>
> Did you use a newer one?
>
>> On Mar 9, 2022, at 12:43 PM, Harbs  wrote:
>>
>> I got an error here:
>>
>> check-sigs:
>>
>> gpg_check:
>> gpg: Signature made Tue Mar  8 08:59:15 2022 IST
>> gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
>> gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
>> gpg: Total number processed: 1
>> gpg:   w/o user IDs: 1
>> gpg: Can't check signature: No public key
>>
>> Did you not publish your key, or do I need to import it?
>>
>>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com 
>>> <mailto:apacheroyal...@gmail.com> <mailto:apacheroyal...@gmail.com 
>>> <mailto:apacheroyal...@gmail.com>> wrote:
>>>
>>> This is the discussion thread.
>>>
>>> Thanks,
>>> Yishay Weiss

Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Harbs]

Well, I don’t know why the gpg check is failing for me. I’ll wait until someone 
else checks the release. If it works for others, I’ll assume it’s a problem 
locally for me and see if I can fix it...

> On Mar 9, 2022, at 1:13 PM, Yishay Weiss  wrote:
> 
> No, that’s the one
> 
> From: Harbs<mailto:harbs.li...@gmail.com <mailto:harbs.li...@gmail.com>>
> Sent: Wednesday, March 9, 2022 12:48 PM
> To: Apache Royale Development<mailto:dev@royale.apache.org 
> <mailto:dev@royale.apache.org>>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
> 
> I seem to have your key from April 13, 2020. That seems to be the most 
> current published key.
> 
> Did you use a newer one?
> 
>> On Mar 9, 2022, at 12:43 PM, Harbs  wrote:
>> 
>> I got an error here:
>> 
>> check-sigs:
>> 
>> gpg_check:
>> gpg: Signature made Tue Mar  8 08:59:15 2022 IST
>> gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
>> gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
>> gpg: Total number processed: 1
>> gpg:   w/o user IDs: 1
>> gpg: Can't check signature: No public key
>> 
>> Did you not publish your key, or do I need to import it?
>> 
>>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com 
>>> <mailto:apacheroyal...@gmail.com> <mailto:apacheroyal...@gmail.com 
>>> <mailto:apacheroyal...@gmail.com>> wrote:
>>> 
>>> This is the discussion thread.
>>> 
>>> Thanks,
>>> Yishay Weiss

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Yishay Weiss]

No, that’s the one

From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Wednesday, March 9, 2022 12:48 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

I seem to have your key from April 13, 2020. That seems to be the most current 
published key.

Did you use a newer one?

> On Mar 9, 2022, at 12:43 PM, Harbs  wrote:
>
> I got an error here:
>
> check-sigs:
>
> gpg_check:
> gpg: Signature made Tue Mar  8 08:59:15 2022 IST
> gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
> gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
> gpg: Total number processed: 1
> gpg:   w/o user IDs: 1
> gpg: Can't check signature: No public key
>
> Did you not publish your key, or do I need to import it?
>
>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com 
>> <mailto:apacheroyal...@gmail.com> wrote:
>>
>> This is the discussion thread.
>>
>> Thanks,
>> Yishay Weiss
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Harbs]

I seem to have your key from April 13, 2020. That seems to be the most current 
published key.

Did you use a newer one?

> On Mar 9, 2022, at 12:43 PM, Harbs  wrote:
> 
> I got an error here:
> 
> check-sigs:
> 
> gpg_check:
> gpg: Signature made Tue Mar  8 08:59:15 2022 IST
> gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
> gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
> gpg: Total number processed: 1
> gpg:   w/o user IDs: 1
> gpg: Can't check signature: No public key
> 
> Did you not publish your key, or do I need to import it?
> 
>> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com 
>>  wrote:
>> 
>> This is the discussion thread.
>> 
>> Thanks,
>> Yishay Weiss
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[Harbs]

I got an error here:

check-sigs:

gpg_check:
gpg: Signature made Tue Mar  8 08:59:15 2022 IST
gpg:using RSA key F4CE36E979325A6221706DB0E86EF353F54FE093
gpg: key E86EF353F54FE093: new key but contains no user ID - skipped
gpg: Total number processed: 1
gpg:   w/o user IDs: 1
gpg: Can't check signature: No public key

Did you not publish your key, or do I need to import it?

> On Mar 8, 2022, at 10:28 AM, apacheroyal...@gmail.com wrote:
> 
> This is the discussion thread.
> 
> Thanks,
> Yishay Weiss

[DISCUSS] Discuss Release Apache Royale 0.9.9 RC2

[apacheroyaleci]

This is the discussion thread.

Thanks,
Yishay Weiss