Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-15 Thread Miro Hrončok
On 08. 06. 21 15:58, Tomas Hrnciar wrote: Chances are, you already got an automated F35FailsToInstall bugzilla from Miro, that your package fails to install. It would be really helpful if you could find the missing dependency and mark the bugzilla for your package dependingon the bugzilla for

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-15 Thread Miro Hrončok
On 08. 06. 21 15:58, Tomas Hrnciar wrote: Chances are, you already got an automated F35FailsToInstall bugzilla from Miro, that your package fails to install. It would be really helpful if you could find the missing dependency and mark the bugzilla for your package dependingon the bugzilla for

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-09 Thread Miro Hrončok
On 09. 06. 21 2:44, Michel Alexandre Salim via devel wrote: On Tue, Jun 08, 2021 at 05:38:27PM -0700, Michel Alexandre Salim via devel wrote: Hi, On Tue, Jun 08, 2021 at 03:58:04PM +0200, Tomas Hrnciar wrote: Hello. As you might already know, we have recently merged in the Python 3.10 side

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Kevin Fenzi
On Tue, Jun 08, 2021 at 05:44:20PM -0700, Michel Alexandre Salim via devel wrote: > On Tue, Jun 08, 2021 at 05:38:27PM -0700, Michel Alexandre Salim via devel > wrote: > > Hi, > > > > On Tue, Jun 08, 2021 at 03:58:04PM +0200, Tomas Hrnciar wrote: > > > Hello. > > > > > > As you might already

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Michel Alexandre Salim via devel
On Tue, Jun 08, 2021 at 05:38:27PM -0700, Michel Alexandre Salim via devel wrote: > Hi, > > On Tue, Jun 08, 2021 at 03:58:04PM +0200, Tomas Hrnciar wrote: > > Hello. > > > > As you might already know, we have recently merged in the Python 3.10 side > > tag to Rawhide, despite several builds not

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Michel Alexandre Salim via devel
Hi, On Tue, Jun 08, 2021 at 03:58:04PM +0200, Tomas Hrnciar wrote: > Hello. > > As you might already know, we have recently merged in the Python 3.10 side > tag to Rawhide, despite several builds not succeeding. We always aim for > some compromise between having the side tag open for too long

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Miro Hrončok
On 08. 06. 21 21:52, Jos de Kloe wrote: I am seeing this error when trying to build locally using mock: Error:  Problem: package python3-xarray-0.17.0-1.fc35.noarch requires python(abi) = 3.9, but none of the providers can be installed   - package python3-devel-3.10.0~b2-3.fc35.x86_64

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Miro Hrončok
On 08. 06. 21 21:52, Jos de Kloe wrote: I am seeing this error when trying to build locally using mock: Error:  Problem: package python3-xarray-0.17.0-1.fc35.noarch requires python(abi) = 3.9, but none of the providers can be installed   - package python3-devel-3.10.0~b2-3.fc35.x86_64

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Jos de Kloe
I am seeing this error when trying to build locally using mock: Error: Problem: package python3-xarray-0.17.0-1.fc35.noarch requires python(abi) = 3.9, but none of the providers can be installed - package python3-devel-3.10.0~b2-3.fc35.x86_64 conflicts with python3 < 3.10.0~b2-3.fc35

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Jos de Kloe
I am seeing this error when trying to build locally using mock: Error: Problem: package python3-xarray-0.17.0-1.fc35.noarch requires python(abi) = 3.9, but none of the providers can be installed - package python3-devel-3.10.0~b2-3.fc35.x86_64 conflicts with python3 < 3.10.0~b2-3.fc35

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Ankur Sinha
On Tue, Jun 08, 2021 15:58:04 +0200, Tomas Hrnciar wrote: > ankursinha MUSIC python-SALib python-brian2 python-dipy python-duecredit > python-fastavro python-fsleyes-props python-fslpy python-hdfs python-klusta > python-matrix-nio python-nilearn python-nitime python-nixio python-pingouin >

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Miro Hrončok
On 08. 06. 21 19:19, Antonio T. sagitter wrote: I need help for PETSC, please. https://bugzilla.redhat.com/show_bug.cgi?id=1959088 I took a look and reported https://bugs.python.org/issue44351 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Miro Hrončok
On 08. 06. 21 19:19, Antonio T. sagitter wrote: I need help for PETSC, please. https://bugzilla.redhat.com/show_bug.cgi?id=1959088 I took a look and reported https://bugs.python.org/issue44351 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Antonio T. sagitter
On 6/8/21 3:58 PM, Tomas Hrnciar wrote: Hello. As you might already know, we have recently merged in the Python 3.10side tagto Rawhide, despite several builds not succeeding.We always aim for some compromise between having the side tag open for too long and having too many failures.

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Antonio T. sagitter
On 6/8/21 3:58 PM, Tomas Hrnciar wrote: Hello. As you might already know, we have recently merged in the Python 3.10side tagto Rawhide, despite several builds not succeeding.We always aim for some compromise between having the side tag open for too long and having too many failures.

Re: Packages that failed to build with Python 3.10 (and what to do)

2021-06-08 Thread Michel Alexandre Salim via devel
On Tue, Jun 08, 2021 at 03:58:04PM +0200, Tomas Hrnciar wrote: > Hello. > > As you might already know, we have recently merged in the Python 3.10 side > tag to Rawhide, despite several builds not succeeding. We always aim for > some compromise between having the side tag open for too long and