Re: [ITP] python36-wx 4.0.7.post2

2020-06-18 Thread Hamish McIntyre-Bhatty via Cygwin-apps
On 18/06/2020 15:08, Jon Turney wrote:
> Done.
>
> Perhaps 'python-wx' should be renamed to 'python2-wx', at some point
> in the future, to make it clear what it contains?

Thanks. Packages are uploaded now.

Yes, I agree, but I'm not sure how to handle that transition smoothly.

Hamish



0x87B761FE07F548D6.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Re: [ITP] python36-wx 4.0.7.post2

2020-06-18 Thread Jon Turney

On 18/06/2020 12:31, Hamish McIntyre-Bhatty via Cygwin-apps wrote:

sure.

https://cygwin.com/packaging/key.html#sshkey


SSH key is already all set-up (I took maintainership of python-wx before).

Can't upload my test packages yet though because they aren't in the
package list.


Done.

Perhaps 'python-wx' should be renamed to 'python2-wx', at some point in 
the future, to make it clear what it contains?


Re: [ITP] python36-wx 4.0.7.post2

2020-06-18 Thread Hamish McIntyre-Bhatty via Cygwin-apps
> sure.
>
> https://cygwin.com/packaging/key.html#sshkey

SSH key is already all set-up (I took maintainership of python-wx before).

Can't upload my test packages yet though because they aren't in the
package list.

Hamish



0x87B761FE07F548D6.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Re: [ITP] python36-wx 4.0.7.post2

2020-06-18 Thread Marco Atzeri via Cygwin-apps

On 18.06.2020 10:20, Hamish McIntyre-Bhatty via Cygwin-apps wrote:

On 17/06/2020 22:23, Hamish McIntyre-Bhatty via Cygwin-apps wrote:

On 17/06/2020 20:24, Marco Atzeri via Cygwin-apps wrote:

On 17.06.2020 10:41, Hamish McIntyre-Bhatty via Cygwin-apps wrote:

On 15/06/2020 19:26, Achim Gratz wrote:

Hamish McIntyre-Bhatty via Cygwin-apps writes:

Turns out just running "rebaseall" worked for me. I don't get any
fork-related warnings/errors any more.

No it doesn't, it's a mere coincidence that it worked in your case.
You
shouldn't manually run rebaseall on Cygwin at all in fact, setup
perpetual postinstall actions take care of maintaing the rebase map.
If you ever have reason to believe that the rebase map needs a complete
rebuild, run "rebase-trigger full" and then run setup again.

Fitting newly built DLL into the rebase map is correctly done by an
ephemeral rebase like the script Marco has shown you does.

Good to know and thanks for the script Marco, seems to work well for me.

The only patch Fedora seems to be using is one to disable the bundled
SIP for building (which I think we need), so I believe this is now
finished. Do I need to rebuild against the new version of Python that
came out a few days ago for cygwin?

Hamish


If still work NO. If don't, we need to understand why as they should be
binary compatible.


Still works with the build from before, just double-checked.

Am I good to go now?

Hamish



sure.

https://cygwin.com/packaging/key.html#sshkey


Re: [ITP] python36-wx 4.0.7.post2

2020-06-18 Thread Hamish McIntyre-Bhatty via Cygwin-apps
On 17/06/2020 22:23, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 17/06/2020 20:24, Marco Atzeri via Cygwin-apps wrote:
>> On 17.06.2020 10:41, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>> On 15/06/2020 19:26, Achim Gratz wrote:
 Hamish McIntyre-Bhatty via Cygwin-apps writes:
> Turns out just running "rebaseall" worked for me. I don't get any
> fork-related warnings/errors any more.
 No it doesn't, it's a mere coincidence that it worked in your case. 
 You
 shouldn't manually run rebaseall on Cygwin at all in fact, setup
 perpetual postinstall actions take care of maintaing the rebase map.
 If you ever have reason to believe that the rebase map needs a complete
 rebuild, run "rebase-trigger full" and then run setup again.

 Fitting newly built DLL into the rebase map is correctly done by an
 ephemeral rebase like the script Marco has shown you does.
>>> Good to know and thanks for the script Marco, seems to work well for me.
>>>
>>> The only patch Fedora seems to be using is one to disable the bundled
>>> SIP for building (which I think we need), so I believe this is now
>>> finished. Do I need to rebuild against the new version of Python that
>>> came out a few days ago for cygwin?
>>>
>>> Hamish
>>>
>> If still work NO. If don't, we need to understand why as they should be
>> binary compatible.

Still works with the build from before, just double-checked.

Am I good to go now?

Hamish



0x87B761FE07F548D6.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature