https://bugzilla.redhat.com/show_bug.cgi?id=2337166
Bug ID: 2337166
Summary: python-hypothesis-6.123.15 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: python-hypothesis
Keywords: FutureFeature, Triaged
Assignee: mhroncok(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: davide(a)cavalca.name,
epel-packagers-sig(a)lists.fedoraproject.org,
igor.raits(a)gmail.com, kkeithle(a)redhat.com,
mhroncok(a)redhat.com, michel(a)michel-slm.name,
pingou(a)pingoured.fr,
python-packagers-sig(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Releases retrieved: 6.123.14, 6.123.15
Upstream release that is considered latest: 6.123.15
Current version/release in rawhide: 6.123.0-1.fc42
URL: https://hypothesis.works/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_M…
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from Anitya:
https://release-monitoring.org/project/7372/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-hypothesis
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2337166
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2316503
Bug ID: 2316503
Summary: Please branch and build lirc for EPEL 10
Product: Fedora EPEL
Version: epel10
Status: NEW
Component: lirc
Assignee: hobbes1069(a)gmail.com
Reporter: xavier(a)bachelot.org
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
hobbes1069(a)gmail.com, leamas.alec(a)gmail.com,
sean(a)mess.org
Blocks: 2303880 (EPEL10Tracker)
Target Milestone: ---
Classification: Fedora
Hi,
Could you please branch and build lirc for EPEL 10 ?
It is needed to build another package.
Regards,
Xavier
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2303880
[Bug 2303880] EPEL 10 Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2316503
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2291978
Bug ID: 2291978
Summary: F41FailsToInstall: python3-xarray
Product: Fedora
Version: rawhide
Status: NEW
Component: python-xarray
Assignee: quantum.analyst(a)gmail.com
Reporter: fti-bugs(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
jonathan(a)almalinux.org,
python-packagers-sig(a)lists.fedoraproject.org,
quantum.analyst(a)gmail.com
Blocks: 2260877 (F41FailsToInstall,RAWHIDEFailsToInstall)
Target Milestone: ---
Classification: Fedora
Hello,
Please note that this comment was generated automatically by
https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at
https://pagure.io/releng/
Your package (python-xarray) Fails To Install in Fedora 41:
can't install python3-xarray:
- nothing provides python(abi) = 3.12 needed by
python3-xarray-2023.8.0-1.fc40.noarch
- nothing provides python3.12dist(numpy) >= 1.21 needed by
python3-xarray-2023.8.0-1.fc40.noarch
- nothing provides python3.12dist(packaging) >= 21.3 needed by
python3-xarray-2023.8.0-1.fc40.noarch
- nothing provides python3.12dist(pandas) >= 1.4 needed by
python3-xarray-2023.8.0-1.fc40.noarch
If you know about this problem and are planning on fixing it, please
acknowledge so by setting the bug status to ASSIGNED. If you don't have time to
maintain this package, consider orphaning it, so maintainers of dependent
packages realize the problem.
If you don't react accordingly to the policy for FTBFS/FTI bugs
(https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails…)
your package may be orphaned in 8+ weeks.
P.S. The data was generated solely from koji buildroot, so it might be newer
than the latest compose or the content on mirrors. To reproduce, use the
koji/local repo only, e.g. in mock:
$ mock -r fedora-41-x86_64 --config-opts mirrored=False install
python3-xarray
P.P.S. If this bug has been reported in the middle of upgrading multiple
dependent packages, please consider using side tags:
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-d…
Thanks!
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2260877
[Bug 2260877] Fedora 41 Fails To install Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2291978
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2327977
Bug ID: 2327977
Summary: python-tenacity fails to build with Python 3.14:
RuntimeError: There is no current event loop in thread
'MainThread'.
Product: Fedora
Version: rawhide
Status: NEW
Component: python-tenacity
Assignee: aekoroglu(a)linux.intel.com
Reporter: ksurma(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: aekoroglu(a)linux.intel.com, daltonminer(a)gmail.com,
davide(a)cavalca.name,
epel-packagers-sig(a)lists.fedoraproject.org,
ksurma(a)redhat.com, mhroncok(a)redhat.com,
michel(a)michel-slm.name, mrunge(a)redhat.com,
ngompa13(a)gmail.com
Blocks: 2322407 (PYTHON3.14)
Target Milestone: ---
Classification: Fedora
python-tenacity fails to build with Python 3.14.0a2.
________________________ TestContextManager.test_sleeps
________________________
a = (<tests.test_asyncio.TestContextManager testMethod=test_sleeps>,), kw = {}
@wraps(callable_)
def wrapper(*a, **kw):
> loop = asyncio.get_event_loop()
tests/test_asyncio.py:34:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <asyncio.unix_events._UnixDefaultEventLoopPolicy object at
0x7f38d5e1b0e0>
def get_event_loop(self):
"""Get the event loop for the current context.
Returns an instance of EventLoop or raises an exception.
"""
if self._local._loop is None:
> raise RuntimeError('There is no current event loop in thread %r.'
% threading.current_thread().name)
E RuntimeError: There is no current event loop in thread
'MainThread'.
/usr/lib64/python3.14/asyncio/events.py:681: RuntimeError
=========================== short test summary info
============================
FAILED
tests/test_asyncio.py::TestAsync::test_attempt_number_is_correct_for_interleaved_coroutines
FAILED tests/test_asyncio.py::TestAsync::test_iscoroutinefunction -
RuntimeEr...
FAILED tests/test_asyncio.py::TestAsync::test_retry - RuntimeError: There is
...
FAILED tests/test_asyncio.py::TestAsync::test_retry_using_async_retying -
Run...
FAILED tests/test_asyncio.py::TestAsync::test_stop_after_attempt -
RuntimeErr...
FAILED tests/test_asyncio.py::TestContextManager::test_async_retying_iterator
FAILED tests/test_asyncio.py::TestContextManager::test_do_max_attempts -
Runt...
FAILED tests/test_asyncio.py::TestContextManager::test_reraise -
RuntimeError...
FAILED tests/test_asyncio.py::TestContextManager::test_retry_with_result -
Ru...
FAILED tests/test_asyncio.py::TestContextManager::test_sleeps -
RuntimeError:...
================= 10 failed, 98 passed, 1 deselected in 2.42s
==================
According to https://docs.python.org/dev/whatsnew/3.14.html#id3
Removed implicit creation of event loop by asyncio.get_event_loop(). It now
raises a RuntimeError if there is no current event loop. (Contributed by Kumar
Aditya in gh-126353.)
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-r…
For all our attempts to build python-tenacity with Python 3.14, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-…
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.14:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/
Let us know here if you have any questions.
Python 3.14 is planned to be included in Fedora 43.
To make that update smoother, we're building Fedora packages with all
pre-releases of Python 3.14.
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=2322407
[Bug 2322407] Python 3.14
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2327977
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2322718
Bug ID: 2322718
Summary: python-aiosmtpd fails to build with Python 3.14:
ImportError: cannot import name 'ByteString' from
'typing'
Product: Fedora
Version: rawhide
Status: NEW
Component: python-aiosmtpd
Assignee: aurelien(a)bompard.org
Reporter: ksurma(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: aurelien(a)bompard.org,
epel-packagers-sig(a)lists.fedoraproject.org,
ksurma(a)redhat.com, mhroncok(a)redhat.com,
michel(a)michel-slm.name, psimovec(a)redhat.com
Blocks: 2322407 (PYTHON3.14)
Target Milestone: ---
Classification: Fedora
python-aiosmtpd fails to build with Python 3.14.0a1.
_______________________ ERROR collecting aiosmtpd/tests
________________________
/usr/lib64/python3.14/importlib/__init__.py:88: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
<frozen importlib._bootstrap>:1386: in _gcd_import
???
<frozen importlib._bootstrap>:1359: in _find_and_load
???
<frozen importlib._bootstrap>:1330: in _find_and_load_unlocked
???
<frozen importlib._bootstrap>:935: in _load_unlocked
???
/usr/lib/python3.14/site-packages/_pytest/assertion/rewrite.py:184: in
exec_module
exec(co, module.__dict__)
aiosmtpd/tests/conftest.py:18: in <module>
from aiosmtpd.controller import Controller
aiosmtpd/controller.py:32: in <module>
from aiosmtpd.smtp import SMTP
aiosmtpd/smtp.py:38: in <module>
from aiosmtpd.proxy_protocol import ProxyData, get_proxy
aiosmtpd/proxy_protocol.py:12: in <module>
from typing import Any, ByteString, Dict, Optional, Tuple, Union
E ImportError: cannot import name 'ByteString' from 'typing'
(/usr/lib64/python3.14/typing.py)
According to https://docs.python.org/dev/whatsnew/3.14.html#typing
ByteString has been removed from both typing and collections.abc modules.
It had previously raised a DeprecationWarning since Python 3.12.
https://docs.python.org/3.14/whatsnew/3.14.html
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-r…
For all our attempts to build python-aiosmtpd with Python 3.14, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-…
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.14:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/
Let us know here if you have any questions.
Python 3.14 is planned to be included in Fedora 43.
To make that update smoother, we're building Fedora packages with all
pre-releases of Python 3.14.
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=2322407
[Bug 2322407] Python 3.14
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2322718
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2327981
Bug ID: 2327981
Summary: python-txaio fails to build with Python 3.14:
RuntimeError: There is no current event loop in thread
'MainThread'.
Product: Fedora
Version: rawhide
Status: NEW
Component: python-txaio
Assignee: jujens(a)jujens.eu
Reporter: ksurma(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
jujens(a)jujens.eu, ksurma(a)redhat.com,
mail(a)fabian-affolter.ch, mhroncok(a)redhat.com
Blocks: 2322407 (PYTHON3.14)
Target Milestone: ---
Classification: Fedora
python-txaio fails to build with Python 3.14.0a2.
___________________________ test_is_called[asyncio]
____________________________
framework = <module 'txaio.aio' from
'/builddir/build/BUILD/python-txaio-23.1.1-build/BUILDROOT/usr/lib/python3.14/site-packages/txaio/aio.py'>
def test_is_called(framework):
> f = txaio.create_future_success(None)
test/test_is_future.py:58:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
../BUILDROOT/usr/lib/python3.14/site-packages/txaio/aio.py:387: in
create_future_success
return self.create_future(result=result)
../BUILDROOT/usr/lib/python3.14/site-packages/txaio/aio.py:366: in
create_future
f = self._loop.create_future()
../BUILDROOT/usr/lib/python3.14/site-packages/txaio/aio.py:323: in _loop
return asyncio.get_event_loop()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <asyncio.unix_events._UnixDefaultEventLoopPolicy object at
0x7f0c9d0d9a90>
def get_event_loop(self):
"""Get the event loop for the current context.
Returns an instance of EventLoop or raises an exception.
"""
if self._local._loop is None:
> raise RuntimeError('There is no current event loop in thread %r.'
% threading.current_thread().name)
E RuntimeError: There is no current event loop in thread
'MainThread'.
/usr/lib64/python3.14/asyncio/events.py:681: RuntimeError
=========================== short test summary info
============================
FAILED test/test_as_future.py::test_as_future_immediate[asyncio] -
RuntimeErr...
FAILED test/test_as_future.py::test_as_future_immediate_none[asyncio] -
Runti...
FAILED test/test_as_future.py::test_as_future_exception[asyncio] -
RuntimeErr...
FAILED test/test_as_future.py::test_as_future_recursive[asyncio] -
RuntimeErr...
FAILED test/test_call_later.py::test_create_future_explicit_loop[asyncio] -
R...
FAILED
test/test_call_later.py::test_create_future_success_explicit_loop[asyncio]
FAILED
test/test_call_later.py::test_create_future_failure_explicit_loop[asyncio]
FAILED test/test_callback.py::test_default_resolve[asyncio] - RuntimeError:
T...
FAILED test/test_callback.py::test_callback[asyncio] - RuntimeError: There
is...
FAILED test/test_callback.py::test_immediate_result[asyncio] - RuntimeError:
...
FAILED test/test_cancel.py::test_cancel[asyncio] - RuntimeError: There is no
...
FAILED test/test_create.py::test_create_result[asyncio] - RuntimeError:
There...
FAILED test/test_create.py::test_create_error[asyncio] - RuntimeError: There
...
FAILED test/test_errback.py::test_errback[asyncio] - RuntimeError: There is
n...
FAILED test/test_errback.py::test_errback_without_except[asyncio] -
RuntimeEr...
FAILED test/test_errback.py::test_errback_plain_exception[asyncio] -
RuntimeE...
FAILED test/test_errback.py::test_errback_cancel_exception[asyncio] -
Runtime...
FAILED test/test_errback.py::test_errback_illegal_args[asyncio] -
RuntimeErro...
FAILED test/test_errback.py::test_errback_reject_no_args[asyncio] -
RuntimeEr...
FAILED test/test_errback.py::test_immediate_failure[asyncio] - RuntimeError:
...
FAILED test/test_gather.py::test_gather_two[asyncio] - RuntimeError: There
is...
FAILED test/test_gather.py::test_gather_no_consume[asyncio] - RuntimeError:
T...
FAILED test/test_is_future.py::test_is_future_generic[asyncio] -
RuntimeError...
FAILED test/test_is_future.py::test_is_called[asyncio] - RuntimeError: There
...
================== 24 failed, 24 passed, 70 skipped in 0.43s
===================
According to https://docs.python.org/dev/whatsnew/3.14.html#id3
Removed implicit creation of event loop by asyncio.get_event_loop(). It now
raises a RuntimeError if there is no current event loop. (Contributed by Kumar
Aditya in gh-126353.)
https://docs.python.org/3.14/whatsnew/3.14.html
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-r…
For all our attempts to build python-txaio with Python 3.14, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-…
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.14:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/
Let us know here if you have any questions.
Python 3.14 is planned to be included in Fedora 43.
To make that update smoother, we're building Fedora packages with all
pre-releases of Python 3.14.
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=2322407
[Bug 2322407] Python 3.14
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2327981
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…