Re: Moving from python2 to python3

2020-12-29 Thread Achim Gratz
Marco Atzeri via Cygwin-apps writes: > On 29.12.2020 21:57, Achim Gratz wrote: >> Marco Atzeri via Cygwin-apps writes: >>> Removed now, and new versions are up as test for >>> python36, 37, 38 and pip >> That's not what I'm seeing at the moment. Package python3 wants to >> update to 3.8.6-1 and py

Re: Moving from python2 to python3

2020-12-29 Thread Marco Atzeri via Cygwin-apps
On 29.12.2020 21:57, Achim Gratz wrote: Marco Atzeri via Cygwin-apps writes: Removed now, and new versions are up as test for python36, 37, 38 and pip That's not what I'm seeing at the moment. Package python3 wants to update to 3.8.6-1 and python38 tries to install 3.8.3-1, that doesn't sound

Re: Moving from python2 to python3

2020-12-29 Thread Achim Gratz
Marco Atzeri via Cygwin-apps writes: > Removed now, and new versions are up as test for > python36, 37, 38 and pip That's not what I'm seeing at the moment. Package python3 wants to update to 3.8.6-1 and python38 tries to install 3.8.3-1, that doesn't sound right. I'm not sure I am seeing the la

Re: Moving from python2 to python3

2020-12-29 Thread Marco Atzeri via Cygwin-apps
On 29.12.2020 18:02, Marco Atzeri wrote: On 29.12.2020 17:42, Achim Gratz wrote: Marco Atzeri via Cygwin-apps writes: You'd better fix that error first. I can agree AFAICS this is still the current package version.  You might want top move it to test whilem you build the new packages, then

Re: Moving from python2 to python3

2020-12-29 Thread Marco Atzeri via Cygwin-apps
On 29.12.2020 17:42, Achim Gratz wrote: Marco Atzeri via Cygwin-apps writes: You'd better fix that error first. I can agree AFAICS this is still the current package version. You might want top move it to test whilem you build the new packages, then replace that version with the new release

Re: Moving from python2 to python3

2020-12-29 Thread Achim Gratz
Marco Atzeri via Cygwin-apps writes: >> You'd better fix that error first. > > I can agree AFAICS this is still the current package version. You might want top move it to test whilem you build the new packages, then replace that version with the new release later on. Regards, Achim. -- +<[Q+ M

Re: Moving from python2 to python3

2020-12-29 Thread Marco Atzeri via Cygwin-apps
On 29.12.2020 16:04, Ken Brown via Cygwin-apps wrote: On 12/29/2020 7:04 AM, Achim Gratz wrote: Marco Atzeri via Cygwin-apps writes: all python packages have been updated. /usr/bin/python /usr/bin/python3 both point now to python3.8 as default using alternatives. You broke the CI: An i

Re: Moving from python2 to python3

2020-12-29 Thread Ken Brown via Cygwin-apps
On 12/29/2020 7:04 AM, Achim Gratz wrote: Marco Atzeri via Cygwin-apps writes: all python packages have been updated. /usr/bin/python /usr/bin/python3 both point now to python3.8 as default using alternatives. You broke the CI: Traceback (most recent call last): File "./scallywag", line

Re: [ITA] pcre, mingw64-i686-pcre, mingw64-x86_64-pcre

2020-12-29 Thread Marco Atzeri via Cygwin-apps
On 29.12.2020 13:12, Achim Gratz wrote: For pcre: Clean the 8.44 patch stack up using the current Fedora patches, remove the submodule and instead pull in the patches directly so that scallywag has a chance of building the package eventually. I've built all packages locally. THere is one te

Re: Moving from python2 to python3

2020-12-29 Thread Marco Atzeri via Cygwin-apps
On 29.12.2020 13:04, Achim Gratz wrote: Marco Atzeri via Cygwin-apps writes: all python packages have been updated. /usr/bin/python /usr/bin/python3 both point now to python3.8 as default using alternatives. You broke the CI: self.connect() File "/usr/lib/python3.8/http/client.py

[ITA] pcre, mingw64-i686-pcre, mingw64-x86_64-pcre

2020-12-29 Thread Achim Gratz
For pcre: Clean the 8.44 patch stack up using the current Fedora patches, remove the submodule and instead pull in the patches directly so that scallywag has a chance of building the package eventually. Pull in the MingW packages as they are using the same source (even though scallywag will balk

Re: Moving from python2 to python3

2020-12-29 Thread Achim Gratz
Marco Atzeri via Cygwin-apps writes: > all python packages have been updated. > > /usr/bin/python > /usr/bin/python3 > > both point now to python3.8 as default using alternatives. You broke the CI: Traceback (most recent call last): File "./scallywag", line 69, in response = urllib.request

appveyor problem

2020-12-29 Thread Lemures Lemniscati via Cygwin-apps
Hi, I was testing openjpeg2.cyport on appveyor to reduce size of artifacts because it made very big builddir.tar.xz. But CI began to fail suddenly. Are there any limitation on AppVeyor CI? I'm sorry if it is the cause of failures that I've treated very big files, repeatedly. Lem -- このEメールはアバ

Re: Moving from python2 to python3

2020-12-29 Thread Marco Atzeri via Cygwin-apps
On 04.12.2020 22:04, Marco Atzeri wrote: On 28.11.2020 19:11, Ken Brown via Cygwin-apps wrote: probably I will release a test version of all python-2.18 python-3.6 python-3.7 python-3.8 before going in full Regards Marco all python packages have been updated. /usr/bin/python /usr/bin/pyt