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 the missing dep. Weslowly progress to do that as well, but 
your help is crucial here.


Hello Pythonistas.

A week has passed and many of the bugzillas received a first automatic 
reminder. I realize that one week might have been too soon for many of them.


If you got a needinfo from me today and thought "What the hell, Miro, I cannot 
do anything, this is waiting for another package to build first", I feel you 
and I am sorry for the spam. Just set the bugzilla to ASSIGNED to acknowledge 
you know about the situation and no more automated reminders like this will 
bother you. I recommend having a look at the dependency that blocks you and 
offering help to move things forward.


OTOH If you are blocked on another package not building, the reminder might get 
things moving: Some of the "Fails to build from source with Python 3.10" 
bugzillas are open with no response for many months and there was no policy to 
escalate them until we merged the side tag.



Anyway,
sorry for the noise and thanks for you help so far!

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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 the missing dep. Weslowly progress to do that as well, but 
your help is crucial here.


Hello Pythonistas.

A week has passed and many of the bugzillas received a first automatic 
reminder. I realize that one week might have been too soon for many of them.


If you got a needinfo from me today and thought "What the hell, Miro, I cannot 
do anything, this is waiting for another package to build first", I feel you 
and I am sorry for the spam. Just set the bugzilla to ASSIGNED to acknowledge 
you know about the situation and no more automated reminders like this will 
bother you. I recommend having a look at the dependency that blocks you and 
offering help to move things forward.


OTOH If you are blocked on another package not building, the reminder might get 
things moving: Some of the "Fails to build from source with Python 3.10" 
bugzillas are open with no response for many months and there was no policy to 
escalate them until we merged the side tag.



Anyway,
sorry for the noise and thanks for you help so far!

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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
tag to 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.

https://fedoraproject.org/wiki/Changes/Python3.10



For some reason, `mock -r fedora-rawhide-x86_64 install python3` is
still pulling in python3-3.9.5-2.fc35.x86_64

This makes testing any fix rather difficult, as it will pass locally and
then fail when doing a Koji (scratch) build.

e.g. https://src.fedoraproject.org/rpms/python-typeguard/pull-request/2


For future reference, `mock --enablerepo=local` does the trick.


Yes, as written in the original email:


## How to run things locally?

You can use mock. Make sure to:

 1. Clear all caches first: $ mock -r fedora-rawhide-x86_64--scrub=all
 2. Use the Koji repo: $ mock -r fedora-rawhide-x86_64 --enablerepo=local ...




--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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 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 having
> > > too many failures.
> > > 
> > > https://fedoraproject.org/wiki/Changes/Python3.10
> > > 
> > 
> > For some reason, `mock -r fedora-rawhide-x86_64 install python3` is
> > still pulling in python3-3.9.5-2.fc35.x86_64
> > 
> > This makes testing any fix rather difficult, as it will pass locally and
> > then fail when doing a Koji (scratch) build.
> > 
> > e.g. https://src.fedoraproject.org/rpms/python-typeguard/pull-request/2
> > 
> For future reference, `mock --enablerepo=local` does the trick.

This is because rawhide composes are (still) broken. 
:(

Hopefully things will get fixed up soon...

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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 succeeding. We always aim for
> > some compromise between having the side tag open for too long and having
> > too many failures.
> > 
> > https://fedoraproject.org/wiki/Changes/Python3.10
> > 
> 
> For some reason, `mock -r fedora-rawhide-x86_64 install python3` is
> still pulling in python3-3.9.5-2.fc35.x86_64
> 
> This makes testing any fix rather difficult, as it will pass locally and
> then fail when doing a Koji (scratch) build.
> 
> e.g. https://src.fedoraproject.org/rpms/python-typeguard/pull-request/2
> 
For future reference, `mock --enablerepo=local` does the trick.

Best regards,

-- 
Michel Alexandre Salim
profile: https://keyoxide.org/mic...@michel-slm.name


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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 and having
> too many failures.
> 
> https://fedoraproject.org/wiki/Changes/Python3.10
> 

For some reason, `mock -r fedora-rawhide-x86_64 install python3` is
still pulling in python3-3.9.5-2.fc35.x86_64

This makes testing any fix rather difficult, as it will pass locally and
then fail when doing a Koji (scratch) build.

e.g. https://src.fedoraproject.org/rpms/python-typeguard/pull-request/2

Best regards,

-- 
Michel Alexandre Salim
profile: https://keyoxide.org/mic...@michel-slm.name


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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 conflicts with python3 < 
3.10.0~b2-3.fc35 provided by python3-3.9.5-2.fc35.i686
   - package python3-devel-3.10.0~b2-3.fc35.x86_64 conflicts with python3 < 
3.10.0~b2-3.fc35 provided by python3-3.9.5-2.fc35.x86_64

   - cannot install the best candidate for the job
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use 
not only best candidate packages)


So I get that python3-xarray has not yet been rebuild.
I'll add that pyproj dependency to bugzilla in a moment.

But what about this conflict between i686 and x86_64 python3-devel versions? 
That should not happen I think with a mock rebuild command like this:


mock -r fedora-rawhide-x86_64 --enablerepo=local --rebuild 
pyproj-3.1.0-1.fc34.src.rpm


Any idea what to do to solve that?


The conflict between i686 and x86_64 is just dnf resolver desperately trying to 
resolve somehow. When python3-xarray is rebuilt, you will not get that error.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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 conflicts with python3 < 
3.10.0~b2-3.fc35 provided by python3-3.9.5-2.fc35.i686
   - package python3-devel-3.10.0~b2-3.fc35.x86_64 conflicts with python3 < 
3.10.0~b2-3.fc35 provided by python3-3.9.5-2.fc35.x86_64

   - cannot install the best candidate for the job
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use 
not only best candidate packages)


So I get that python3-xarray has not yet been rebuild.
I'll add that pyproj dependency to bugzilla in a moment.

But what about this conflict between i686 and x86_64 python3-devel versions? 
That should not happen I think with a mock rebuild command like this:


mock -r fedora-rawhide-x86_64 --enablerepo=local --rebuild 
pyproj-3.1.0-1.fc34.src.rpm


Any idea what to do to solve that?


The conflict between i686 and x86_64 is just dnf resolver desperately trying to 
resolve somehow. When python3-xarray is rebuilt, you will not get that error.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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 provided by python3-3.9.5-2.fc35.i686
  - package python3-devel-3.10.0~b2-3.fc35.x86_64 conflicts with 
python3 < 3.10.0~b2-3.fc35 provided by python3-3.9.5-2.fc35.x86_64

  - cannot install the best candidate for the job
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' 
to use not only best candidate packages)


So I get that python3-xarray has not yet been rebuild.
I'll add that pyproj dependency to bugzilla in a moment.

But what about this conflict between i686 and x86_64 python3-devel 
versions? That should not happen I think with a mock rebuild command 
like this:


mock -r fedora-rawhide-x86_64 --enablerepo=local --rebuild 
pyproj-3.1.0-1.fc34.src.rpm


Any idea what to do to solve that?

Jos

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.


https://fedoraproject.org/wiki/Changes/Python3.10 



The packages, when not rebuilt, are not installable in rawhide, hence 
fixing them should be our top priority. If you need help with 
Python-related issues, we (the Python Maintenance team at Red Hat) are 
happy to help. Unfortunately, several packages fail to build for 
Python-unrelated reasons.


Most of the packages only fail to build because their dependencies were 
not yet rebuilt. 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 the missing dep. Weslowly progress to do that as well, but 
your help is crucial here.


If your package fails because there isanon-dependency problem, you might 
have already received a bugzilla from us in the past. If the build 
failure is related to changes in Python 3.10, it should contain some 
hints about the problem.


# What to do?

General advice: If you are aware of the problem and working towards 
fixing it, set your bugzilla to ASSIGNED to avoid further automated 
reminders.


If blocked by dependencies, do not close the bugzillas as NOTABUG or 
DUPLICATE just because it is "not a problem in your package". The 
automation will file new ones anyway.


## My package fails to build because it has test failures in %check

Please, try to resolve the failures. If you are confident that the 
package works fine, but the tests are wrong, skip some failing tests, 
ideally with a link to an upstream issue. Do not disable (e.g. comment 
out) all tests just to unblock the rebuild of your package, it usually 
only hides the problem.


## My package fails to build because it has broken build dependencies

Please try to track the missing build dependencies in Bugzilla. If 
possible, help the maintainers of your dependencies to get them rebuilt. 
When in need of escalation, ask us for provenpackager help (ideally with 
pull requests to be merged). Once possible, rebuild your package (no 
need to bump the release, we already did that). When you do, the 
bugzilla will eventually get automatically closed, but you can do that 
manually as well.


## My package was rebuilt with Python 3.10 but it has broken runtime 
dependencies


Please try to track the missing runtime dependencies in Bugzilla. If 
possible, help the maintainers of your dependencies to get them rebuilt. 
When in need of escalation, ask us for provenpackager help (ideally with 
pull requests to be merged). When the dependencies are rebuilt, your 
package will install successfully once again and the bugzilla will 
eventually get automatically closed, but you can do that manually as well.


## My package failed to build but installs just fine

Some packages that only require libpython3.9.so.1.0 will successfully 
pull in the python3.9 package as a dependency and hence they don't have 
installation issues. They need to be rebuilt with Python 3.10 anyway, we 
don't want Fedora users to pull in two Python versions unless they need 
them for development purposes.


## How to run things locally?

You can use mock. Make sure to:

  1. Clear all caches first: $ mock -r fedora-rawhide-x86_64--scrub=all
  2. Use the Koji repo: $ mock -r fedora-rawhide-x86_64 
--enablerepo=local ...


## Where to get help

Reply to this thread or find us (thrnciar, mhroncok) on #fedora-python 
IRC channel (libera.chat).


---

Let usknow if you have other questions.

Maintainers by package:
5minute  pmoravco
APLpy    sergiopr

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 provided by python3-3.9.5-2.fc35.i686
  - package python3-devel-3.10.0~b2-3.fc35.x86_64 conflicts with 
python3 < 3.10.0~b2-3.fc35 provided by python3-3.9.5-2.fc35.x86_64

  - cannot install the best candidate for the job
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' 
to use not only best candidate packages)


So I get that python3-xarray has not yet been rebuild.
I'll add that pyproj dependency to bugzilla in a moment.

But what about this conflict between i686 and x86_64 python3-devel 
versions? That should not happen I think with a mock rebuild command 
like this:


mock -r fedora-rawhide-x86_64 --enablerepo=local --rebuild 
pyproj-3.1.0-1.fc34.src.rpm


Any idea what to do to solve that?

Jos

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.


https://fedoraproject.org/wiki/Changes/Python3.10 



The packages, when not rebuilt, are not installable in rawhide, hence 
fixing them should be our top priority. If you need help with 
Python-related issues, we (the Python Maintenance team at Red Hat) are 
happy to help. Unfortunately, several packages fail to build for 
Python-unrelated reasons.


Most of the packages only fail to build because their dependencies were 
not yet rebuilt. 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 the missing dep. Weslowly progress to do that as well, but 
your help is crucial here.


If your package fails because there isanon-dependency problem, you might 
have already received a bugzilla from us in the past. If the build 
failure is related to changes in Python 3.10, it should contain some 
hints about the problem.


# What to do?

General advice: If you are aware of the problem and working towards 
fixing it, set your bugzilla to ASSIGNED to avoid further automated 
reminders.


If blocked by dependencies, do not close the bugzillas as NOTABUG or 
DUPLICATE just because it is "not a problem in your package". The 
automation will file new ones anyway.


## My package fails to build because it has test failures in %check

Please, try to resolve the failures. If you are confident that the 
package works fine, but the tests are wrong, skip some failing tests, 
ideally with a link to an upstream issue. Do not disable (e.g. comment 
out) all tests just to unblock the rebuild of your package, it usually 
only hides the problem.


## My package fails to build because it has broken build dependencies

Please try to track the missing build dependencies in Bugzilla. If 
possible, help the maintainers of your dependencies to get them rebuilt. 
When in need of escalation, ask us for provenpackager help (ideally with 
pull requests to be merged). Once possible, rebuild your package (no 
need to bump the release, we already did that). When you do, the 
bugzilla will eventually get automatically closed, but you can do that 
manually as well.


## My package was rebuilt with Python 3.10 but it has broken runtime 
dependencies


Please try to track the missing runtime dependencies in Bugzilla. If 
possible, help the maintainers of your dependencies to get them rebuilt. 
When in need of escalation, ask us for provenpackager help (ideally with 
pull requests to be merged). When the dependencies are rebuilt, your 
package will install successfully once again and the bugzilla will 
eventually get automatically closed, but you can do that manually as well.


## My package failed to build but installs just fine

Some packages that only require libpython3.9.so.1.0 will successfully 
pull in the python3.9 package as a dependency and hence they don't have 
installation issues. They need to be rebuilt with Python 3.10 anyway, we 
don't want Fedora users to pull in two Python versions unless they need 
them for development purposes.


## How to run things locally?

You can use mock. Make sure to:

  1. Clear all caches first: $ mock -r fedora-rawhide-x86_64--scrub=all
  2. Use the Koji repo: $ mock -r fedora-rawhide-x86_64 
--enablerepo=local ...


## Where to get help

Reply to this thread or find us (thrnciar, mhroncok) on #fedora-python 
IRC channel (libera.chat).


---

Let usknow if you have other questions.

Maintainers by package:
5minute  pmoravco
APLpy    sergiopr

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
> python-pybids python-pymatreader python-pypet python-pyphi python-pyriemann
> python-pyscaffold python-sklearn-nature-inspired-algorithms python-trimesh

Woah! :D

I'll start looking into these now. Hopefully they're all simple fixes.

Thanks again for all your work.

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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.


https://fedoraproject.org/wiki/Changes/Python3.10 



The packages, when not rebuilt, are not installable in rawhide, hence 
fixing them should be our top priority. If you need help with 
Python-related issues, we (the Python Maintenance team at Red Hat) are 
happy to help. Unfortunately, several packages fail to build for 
Python-unrelated reasons.


Most of the packages only fail to build because their dependencies were 
not yet rebuilt. 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 the missing dep. Weslowly progress to do that as well, but 
your help is crucial here.


If your package fails because there isanon-dependency problem, you might 
have already received a bugzilla from us in the past. If the build 
failure is related to changes in Python 3.10, it should contain some 
hints about the problem.


# What to do?

General advice: If you are aware of the problem and working towards 
fixing it, set your bugzilla to ASSIGNED to avoid further automated 
reminders.


If blocked by dependencies, do not close the bugzillas as NOTABUG or 
DUPLICATE just because it is "not a problem in your package". The 
automation will file new ones anyway.


## My package fails to build because it has test failures in %check

Please, try to resolve the failures. If you are confident that the 
package works fine, but the tests are wrong, skip some failing tests, 
ideally with a link to an upstream issue. Do not disable (e.g. comment 
out) all tests just to unblock the rebuild of your package, it usually 
only hides the problem.


## My package fails to build because it has broken build dependencies

Please try to track the missing build dependencies in Bugzilla. If 
possible, help the maintainers of your dependencies to get them rebuilt. 
When in need of escalation, ask us for provenpackager help (ideally with 
pull requests to be merged). Once possible, rebuild your package (no 
need to bump the release, we already did that). When you do, the 
bugzilla will eventually get automatically closed, but you can do that 
manually as well.


## My package was rebuilt with Python 3.10 but it has broken runtime 
dependencies


Please try to track the missing runtime dependencies in Bugzilla. If 
possible, help the maintainers of your dependencies to get them rebuilt. 
When in need of escalation, ask us for provenpackager help (ideally with 
pull requests to be merged). When the dependencies are rebuilt, your 
package will install successfully once again and the bugzilla will 
eventually get automatically closed, but you can do that manually as well.


## My package failed to build but installs just fine

Some packages that only require libpython3.9.so.1.0 will successfully 
pull in the python3.9 package as a dependency and hence they don't have 
installation issues. They need to be rebuilt with Python 3.10 anyway, we 
don't want Fedora users to pull in two Python versions unless they need 
them for development purposes.


## How to run things locally?

You can use mock. Make sure to:

  1. Clear all caches first: $ mock -r fedora-rawhide-x86_64--scrub=all
  2. Use the Koji repo: $ mock -r fedora-rawhide-x86_64 
--enablerepo=local ...


## Where to get help

Reply to this thread or find us (thrnciar, mhroncok) on #fedora-python 
IRC channel (libera.chat).


---

Let usknow if you have other questions.


> ...

petsc sagitter


I need help for PETSC, please.

https://bugzilla.redhat.com/show_bug.cgi?id=1959088

--
---
Antonio Trande
Fedora Project
mailto: sagit...@fedoraproject.org
GPG key: 0x29FBC85D7A51CC2F
GPG key server: https://keys.gnupg.net/


OpenPGP_0x29FBC85D7A51CC2F.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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.


https://fedoraproject.org/wiki/Changes/Python3.10 



The packages, when not rebuilt, are not installable in rawhide, hence 
fixing them should be our top priority. If you need help with 
Python-related issues, we (the Python Maintenance team at Red Hat) are 
happy to help. Unfortunately, several packages fail to build for 
Python-unrelated reasons.


Most of the packages only fail to build because their dependencies were 
not yet rebuilt. 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 the missing dep. Weslowly progress to do that as well, but 
your help is crucial here.


If your package fails because there isanon-dependency problem, you might 
have already received a bugzilla from us in the past. If the build 
failure is related to changes in Python 3.10, it should contain some 
hints about the problem.


# What to do?

General advice: If you are aware of the problem and working towards 
fixing it, set your bugzilla to ASSIGNED to avoid further automated 
reminders.


If blocked by dependencies, do not close the bugzillas as NOTABUG or 
DUPLICATE just because it is "not a problem in your package". The 
automation will file new ones anyway.


## My package fails to build because it has test failures in %check

Please, try to resolve the failures. If you are confident that the 
package works fine, but the tests are wrong, skip some failing tests, 
ideally with a link to an upstream issue. Do not disable (e.g. comment 
out) all tests just to unblock the rebuild of your package, it usually 
only hides the problem.


## My package fails to build because it has broken build dependencies

Please try to track the missing build dependencies in Bugzilla. If 
possible, help the maintainers of your dependencies to get them rebuilt. 
When in need of escalation, ask us for provenpackager help (ideally with 
pull requests to be merged). Once possible, rebuild your package (no 
need to bump the release, we already did that). When you do, the 
bugzilla will eventually get automatically closed, but you can do that 
manually as well.


## My package was rebuilt with Python 3.10 but it has broken runtime 
dependencies


Please try to track the missing runtime dependencies in Bugzilla. If 
possible, help the maintainers of your dependencies to get them rebuilt. 
When in need of escalation, ask us for provenpackager help (ideally with 
pull requests to be merged). When the dependencies are rebuilt, your 
package will install successfully once again and the bugzilla will 
eventually get automatically closed, but you can do that manually as well.


## My package failed to build but installs just fine

Some packages that only require libpython3.9.so.1.0 will successfully 
pull in the python3.9 package as a dependency and hence they don't have 
installation issues. They need to be rebuilt with Python 3.10 anyway, we 
don't want Fedora users to pull in two Python versions unless they need 
them for development purposes.


## How to run things locally?

You can use mock. Make sure to:

  1. Clear all caches first: $ mock -r fedora-rawhide-x86_64--scrub=all
  2. Use the Koji repo: $ mock -r fedora-rawhide-x86_64 
--enablerepo=local ...


## Where to get help

Reply to this thread or find us (thrnciar, mhroncok) on #fedora-python 
IRC channel (libera.chat).


---

Let usknow if you have other questions.


> ...

petsc sagitter


I need help for PETSC, please.

https://bugzilla.redhat.com/show_bug.cgi?id=1959088

--
---
Antonio Trande
Fedora Project
mailto: sagit...@fedoraproject.org
GPG key: 0x29FBC85D7A51CC2F
GPG key server: https://keys.gnupg.net/


OpenPGP_0x29FBC85D7A51CC2F.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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 having
> too many failures.
> 
> https://fedoraproject.org/wiki/Changes/Python3.10
> 
...
> fbthrift dcavalca filbranden salimma
> follydcavalca filbranden salimma
> watchman dcavalca filbranden salimma
> 
These are all related; I'll try to get them fixed. There's a known issue with 
fbthrift's use of Cython that has been affecting rebuilds for the past few 
weeks, so now is as good a time as any.

Best regards,

-- 
Michel Alexandre Salim
profile: https://keyoxide.org/mic...@michel-slm.name


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure