[Bug 2232109] Only three points are shown
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2232109
--- Comment #5 from Aoife Moloney <amoloney(a)redhat.com> ---
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on
2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
'version' of '37'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version'
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora Linux 37 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2232109
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
6 months, 3 weeks
[Bug 2104851] python3-bcrypt has implicit conflict with python3-py-bcrypt
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2104851
--- Comment #11 from Aoife Moloney <amoloney(a)redhat.com> ---
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on
2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
'version' of '37'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version'
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora Linux 37 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2104851
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
6 months, 3 weeks
[Bug 2250850] New: rb_libtorrent fails to build with Python 3.13: error: implicit declaration of function ‘PyEval_InitThreads’
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2250850
Bug ID: 2250850
Summary: rb_libtorrent fails to build with Python 3.13: error:
implicit declaration of function ‘PyEval_InitThreads’
Product: Fedora
Version: rawhide
Status: NEW
Component: rb_libtorrent
Assignee: mike(a)cchtml.com
Reporter: ksurma(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
ksurma(a)redhat.com, me(a)fale.io, mhroncok(a)redhat.com,
mike(a)cchtml.com
Blocks: 2244836 (PYTHON3.13)
Target Milestone: ---
Classification: Fedora
rb_libtorrent fails to build with Python 3.13.0a1.
/builddir/build/BUILD/libtorrent-rasterbar-2.0.9/bindings/python/src/module.cpp:
In function ‘void init_module_libtorrent()’:
/builddir/build/BUILD/libtorrent-rasterbar-2.0.9/bindings/python/src/module.cpp:38:5:
error: ‘PyEval_InitThreads’ was not declared in this scope; did you mean
‘PyEval_SaveThread’?
38 | PyEval_InitThreads();
| ^~~~~~~~~~~~~~~~~~
| PyEval_SaveThread
According to https://docs.python.org/3.13/whatsnew/3.13.html:
Remove PyEval_InitThreads() and PyEval_ThreadsInitialized() functions,
deprecated in Python 3.9.
Since Python 3.7, Py_Initialize() always creates the GIL:
calling PyEval_InitThreads() did nothing and PyEval_ThreadsInitialized() always
returned non-zero.
(Contributed by Victor Stinner in
https://github.com/python/cpython/issues/105182.)
https://docs.python.org/3.13/whatsnew/3.13.html
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora...
For all our attempts to build rb_libtorrent with Python 3.13, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/rb_li...
Testing and mass rebuild of packages is happening in copr.
You can follow these instructions to test locally in mock if your package
builds with Python 3.13:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/
Let us know here if you have any questions.
Python 3.13 is planned to be included in Fedora 41.
To make that update smoother, we're building Fedora packages with all
pre-releases of Python 3.13.
A build failure prevents us from testing all dependent packages (transitive
[Build]Requires),
so if this package is required a lot, it's important for us to get it fixed
soon.
We'd appreciate help from the people who know this package best,
but if you don't want to work on this now, let us know so we can try to work
around it on our side.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2244836
[Bug 2244836] Python 3.13
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2250850
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
6 months, 3 weeks