https://bugzilla.redhat.com/show_bug.cgi?id=2329842
Bug ID: 2329842
Summary: python-atomicwrites fails to build with sphinx 8.x:
ERROR: Invalid value `None` in
intersphinx_mapping['http://docs.python.org/'].
Product: Fedora
Version: rawhide
Status: NEW
Component: python-atomicwrites
Assignee: michele(a)acksyn.org
Reporter: thrnciar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
fedora(a)me.benboeckel.net, michele(a)acksyn.org,
michel(a)michel-slm.name
Blocks: 2275375
Target Milestone: ---
Classification: Fedora
python-atomicwrites fails to build with sphinx 8.x in Fedora 42 (currently
Rawhide).
The issue detected:
```
ERROR: Invalid value `None` in intersphinx_mapping['http://docs.python.org/'].
Expected a two-element tuple or list.
Configuration error:
Invalid `intersphinx_mapping` configuration (1 error).
make: *** [Makefile:131: man] Error 2
```
The intersphinx_mapping error can be easily fixed by adjusting conf.py.
You can take an inspiration from this PR:
https://github.com/jupyterlab/jupyterlab/pull/14423
Please work with upstream on this issue, I plan to ship sphinx 8 in two weeks.
For the logs from testing build attempts, see:
https://copr.fedorainfracloud.org/coprs/thrnciar/python-sphinx/package/pyth…
You can test you package in mock running:
$ mock -r fedora-rawhide-x86_64
--addrepo=https://download.copr.fedorainfracloud.org/results/thrnciar/python-sphinx/fedora-rawhide-x86_64/
--no-clean your.src.rpm
$ mock -r fedora-rawhide-x86_64
--addrepo=https://download.copr.fedorainfracloud.org/results/thrnciar/python-sphinx/fedora-rawhide-x86_64/
shell
We'd like to include Sphinx 8 in Fedora 42.
Let us know here if you have any questions. Thank you!
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2275375
[Bug 2275375] python-sphinx-8.1.3 is available
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2329842
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=2290513
Bug ID: 2290513
Summary: dahdi-tools-2.11.1-31.fc41 FTBFS: %setup0 does not
expand with rpm-build-4.19.91
Product: Fedora
Version: rawhide
URL: https://ppisar.fedorapeople.org/perl_rebuild/scratch/l
atest/packages/dahdi-tools/build.log
Status: NEW
Component: dahdi-tools
Assignee: jsmith.fedora(a)gmail.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
jsmith.fedora(a)gmail.com
Blocks: 2260875 (F41FTBFS,RAWHIDEFTBFS)
Target Milestone: ---
Classification: Fedora
dahdi-tools-2.11.1-31.fc41 fails to build from sources in Fedora 41:
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.ee9Znl
+ umask 022
+ cd /home/test/fedora/dahdi-tools/dahdi-tools-2.11.1-build
+ %setup0 -q -n dahdi-tools-2.11.1 -a 2
/var/tmp/rpm-tmp.ee9Znl: line 34: fg: no job control
error: Bad exit status from /var/tmp/rpm-tmp.ee9Znl (%prep)
It seems that %setup0 macro does not expand with
rpm-build-4.19.91-7.fc41.x86_64. I believe that rpm intentionally stopped
supporting "macros" with a variadic digit suffix (%path0, %setup0 etc.).
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2260875
[Bug 2260875] Fedora 41 FTBFS Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2290513
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…