March 2022 - Epel-packagers-sig - Fedora mailing-lists

[Bug 2044963] New: F36FailsToInstall: postorius
by bugzilla＠redhat.com 07 Mar '23

07 Mar '23

https://bugzilla.redhat.com/show_bug.cgi?id=2044963 Bug ID: 2044963 Summary: F36FailsToInstall: postorius Product: Fedora Version: rawhide Status: NEW Component: python-postorius Assignee: michel(a)michel-slm.name Reporter: mhroncok(a)redhat.com CC: epel-packagers-sig(a)lists.fedoraproject.org, infra-sig(a)lists.fedoraproject.org, michel(a)michel-slm.name, ngompa13(a)gmail.com, python-sig(a)lists.fedoraproject.org Blocks: 1992487 (F36FailsToInstall,RAWHIDEFailsToInstall) Target Milestone: --- Classification: Fedora Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok(a)redhat.com) Your package (python-postorius) Fails To Install in Fedora 36: can't install postorius: - nothing provides (python3.10dist(django) < 3.3~~ with python3.10dist(django) >= 2.2) needed by postorius-1.3.6-1.fc36.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. 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=1992487 [Bug 1992487] Fedora 36 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=2044963

1 16

[Bug 2063475] New: python-libtmux-0.11.0b2 is available
by bugzilla＠redhat.com 20 Feb '23

20 Feb '23

https://bugzilla.redhat.com/show_bug.cgi?id=2063475 Bug ID: 2063475 Summary: python-libtmux-0.11.0b2 is available Product: Fedora Version: rawhide Status: NEW Component: python-libtmux Keywords: FutureFeature, Triaged Assignee: mail(a)fabian-affolter.ch Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dcavalca(a)fb.com, epel-packagers-sig(a)lists.fedoraproject.org, mail(a)fabian-affolter.ch Target Milestone: --- Classification: Fedora Latest upstream release: 0.11.0b2 Current version/release in rawhide: 0.10.3-1.fc37 URL: https://pypi.python.org/pypi/libtmux 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://fedoraproject.org/wiki/Upstream_release_monitoring 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/13040/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2063475

1 7

[Bug 2069264] New: [abrt] notmuch: notmuch_tags_valid(): notmuch killed by SIGSEGV
by bugzilla＠redhat.com 02 Jan '23

02 Jan '23

https://bugzilla.redhat.com/show_bug.cgi?id=2069264 Bug ID: 2069264 Summary: [abrt] notmuch: notmuch_tags_valid(): notmuch killed by SIGSEGV Product: Fedora Version: 35 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:984ab0912b2464ac1bdc7a4ed0314cd31128b91d;VAR IANT_ID=xfce; Component: notmuch Assignee: mjg(a)fedoraproject.org Reporter: jhutar(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, lewk(a)openmailbox.org, mjg(a)fedoraproject.org, rbean(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Some email have to be causing that :-/ neomutt is failing because of that as well when I have virtual-mailboxes configuerd. Command I have used in this case was: notmuch search "tag:zsdidaktis OR from:@zsdidaktis.cz" Version-Release number of selected component: notmuch-0.35-2.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-2.scope cmdline: notmuch search $'tag:zsdidaktis OR from:@zsdidaktis.cz' crash_function: notmuch_tags_valid executable: /usr/bin/notmuch journald_cursor: s=2b2e17a38b1e4b81b5a9d1b5dc73c207;i=4a10;b=b9117c89319c46bfb4da24d1af361aae;m=36b1505a0a;t=5db48d2887322;x=3e305f1fd4ce2258 kernel: 5.16.15-201.fc35.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 notmuch_tags_valid at lib/tags.c:51 #1 _thread_add_message at lib/thread.cc:254 #2 _notmuch_thread_create at lib/thread.cc:631 #3 notmuch_threads_get at lib/query.cc:671 #4 do_search_threads at /usr/src/debug/notmuch-0.35-2.fc35.x86_64/notmuch-search.c:150 #5 notmuch_search_command at /usr/src/debug/notmuch-0.35-2.fc35.x86_64/notmuch-search.c:845 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2069264

1 10

[Bug 2059360] New: yarnpkg for fedora 35 installs binary '/usr/bin/%{fc_name}'
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=2059360 Bug ID: 2059360 Summary: yarnpkg for fedora 35 installs binary '/usr/bin/%{fc_name}' Product: Fedora Version: 35 Status: NEW Component: yarnpkg Assignee: zsvetlik(a)redhat.com Reporter: martin.kuehl(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, ngompa13(a)gmail.com, zsvetlik(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: the current yarnpkg rpm installs a binary at the path '/usr/bin/%{fc_name}' this is also visible at: https://packages.fedoraproject.org/pkgs/yarnpkg/yarnpkg/fedora-35.html#files Version-Release number of selected component (if applicable): yarnpkg-1.22.10-3.fc35 How reproducible: always Steps to Reproduce: 1. dnf repoquery --list yarnpkg | grep /usr/bin or look at https://packages.fedoraproject.org/pkgs/yarnpkg/yarnpkg/fedora-35.html#files Actual results: /usr/bin/%{fc_name} /usr/bin/yarn /usr/bin/yarnpkg Expected results: judging by the package for fedora 36: /usr/bin/nodejs-yarn /usr/bin/yarn /usr/bin/yarnpkg Additional info: if i remember correctly that's rpm spec template syntax so there might be some stray escaping or something? it's also apparently fixed for f36 so backporting that package would be just fine. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059360

1 3

[Bug 2067022] New: ImageMagick: heap-buffer-overflow in PushShortPixel of quantum-private.h
by bugzilla＠redhat.com 07 Oct '22

07 Oct '22

https://bugzilla.redhat.com/show_bug.cgi?id=2067022 Bug ID: 2067022 Summary: ImageMagick: heap-buffer-overflow in PushShortPixel of quantum-private.h Product: Security Response Hardware: All OS: Linux Status: NEW Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: trathi(a)redhat.com CC: blaise(a)gmail.com, dcavalca(a)fb.com, epel-packagers-sig(a)lists.fedoraproject.org, fedora(a)famillecollet.com, jhorak(a)redhat.com, luya_tfz(a)thefinalzone.net, michel(a)michel-slm.name, ngompa13(a)gmail.com, pampelmuse(a)gmx.at, sergio(a)serjux.com, troy(a)troycurtisjr.com Target Milestone: --- Classification: Other A heap-buffer-overflow flaw was found in PushShortPixel function of quantum-private.h References: https://github.com/ImageMagick/ImageMagick/issues/4974 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2067022

1 10

[Bug 2069709] New: python-stack-data fails to build with Python 3.11: executing.executing.NotOneValueFound: Expected one value, found 0
by bugzilla＠redhat.com 22 Jun '22

22 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=2069709 Bug ID: 2069709 Summary: python-stack-data fails to build with Python 3.11: executing.executing.NotOneValueFound: Expected one value, found 0 Product: Fedora Version: rawhide Status: NEW Component: python-stack-data Assignee: lbalhar(a)redhat.com Reporter: thrnciar(a)redhat.com CC: epel-packagers-sig(a)lists.fedoraproject.org, lbalhar(a)redhat.com, mhroncok(a)redhat.com, michel(a)michel-slm.name, thrnciar(a)redhat.com Blocks: 2016048 (PYTHON3.11) Target Milestone: --- Classification: Fedora python-stack-data fails to build with Python 3.11.0a6. =================================== FAILURES =================================== _________________________________ test_example _________________________________ def test_example(): from .samples.example import bar > result = bar() tests/test_core.py:573: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ tests/samples/example.py:27: in bar exec("result = foo()", globals(), names) <string>:1: in <module> ??? tests/samples/example.py:20: in foo result = print_stack( tests/samples/example.py:35: in print_stack for frame_info in list(FrameInfo.stack_data(frame, options))[-3:]: /usr/lib/python3.11/site-packages/typeguard/__init__.py:897: in __next__ return self.send(None) /usr/lib/python3.11/site-packages/typeguard/__init__.py:915: in send value = self.__wrapped.send(obj) stack_data/core.py:565: in stack_data yield from collapse_repeated( stack_data/utils.py:84: in collapse_repeated yield from map(mapper, original_group) stack_data/core.py:555: in mapper return cls(f, options) /usr/lib/python3.11/site-packages/typeguard/__init__.py:1033: in wrapper retval = func(*args, **kwargs) stack_data/core.py:520: in __init__ self.executing = Source.executing(frame_or_tb) /usr/lib/python3.11/site-packages/executing/executing.py:335: in executing node = find_node(lasti) /usr/lib/python3.11/site-packages/executing/executing.py:321: in find_node return only( _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ it = <generator object Source.executing.<locals>.find_node.<locals>.<genexpr> at 0x7f8a614b36a0> def only(it): if hasattr(it, '__len__'): if len(it) != 1: raise NotOneValueFound('Expected one value, found %s' % len(it)) # noinspection PyTypeChecker return list(it)[0] lst = tuple(islice(it, 2)) if len(lst) == 0: > raise NotOneValueFound('Expected one value, found 0') E executing.executing.NotOneValueFound: Expected one value, found 0 /usr/lib/python3.11/site-packages/executing/executing.py:164: NotOneValueFound ____________________________ test_pygments_example _____________________________ def test_pygments_example(): from .samples.pygments_example import bar > result = bar() tests/test_core.py:618: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ tests/samples/pygments_example.py:17: in bar @deco tests/samples/pygments_example.py:26: in deco f.result = print_stack() tests/samples/pygments_example.py:43: in print_stack for frame_info in list(FrameInfo.stack_data(frame, options))[-2:]: /usr/lib/python3.11/site-packages/typeguard/__init__.py:897: in __next__ return self.send(None) /usr/lib/python3.11/site-packages/typeguard/__init__.py:915: in send value = self.__wrapped.send(obj) stack_data/core.py:565: in stack_data yield from collapse_repeated( stack_data/utils.py:84: in collapse_repeated yield from map(mapper, original_group) stack_data/core.py:555: in mapper return cls(f, options) /usr/lib/python3.11/site-packages/typeguard/__init__.py:1033: in wrapper retval = func(*args, **kwargs) stack_data/core.py:520: in __init__ self.executing = Source.executing(frame_or_tb) /usr/lib/python3.11/site-packages/executing/executing.py:354: in executing opname(index - 2) == "PRECALL_FUNCTION" _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ i = 44 def opname(i): > return bc_list[i // 2].opname E IndexError: list index out of range /usr/lib/python3.11/site-packages/executing/executing.py:346: IndexError _________________________________ test_example _________________________________ n = 0 def foo(n=5): if n > 0: return foo(n - 1) x = 1 lst = ( [ x, ] + [] + [] + [] + [] + [] ) try: > return int(str(lst)) E ValueError: invalid literal for int() with base 10: '[1]' tests/samples/formatter_example.py:21: ValueError During handling of the above exception, another exception occurred: n = 0 def foo(n=5): if n > 0: return foo(n - 1) x = 1 lst = ( [ x, ] + [] + [] + [] + [] + [] ) try: return int(str(lst)) except: try: > return 1 / 0 E ZeroDivisionError: division by zero tests/samples/formatter_example.py:24: ZeroDivisionError The above exception was the direct cause of the following exception: capsys = <_pytest.capture.CaptureFixture object at 0x7f8a618fc490> def test_example(capsys): from .samples.formatter_example import bar, print_stack1, format_stack1, format_frame, f_string @contextmanager def check_example(name): yield stderr = capsys.readouterr().err compare_to_file(stderr, name) with check_example("variables"): try: > bar() tests/test_formatter.py:40: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ def bar(): > exec("foo()") tests/samples/formatter_example.py:30: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > ??? <string>:1: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ n = 5 def foo(n=5): if n > 0: > return foo(n - 1) tests/samples/formatter_example.py:8: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ n = 4 def foo(n=5): if n > 0: > return foo(n - 1) tests/samples/formatter_example.py:8: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ n = 3 def foo(n=5): if n > 0: > return foo(n - 1) tests/samples/formatter_example.py:8: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ n = 2 def foo(n=5): if n > 0: > return foo(n - 1) tests/samples/formatter_example.py:8: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ n = 1 def foo(n=5): if n > 0: > return foo(n - 1) tests/samples/formatter_example.py:8: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ n = 0 def foo(n=5): if n > 0: return foo(n - 1) x = 1 lst = ( [ x, ] + [] + [] + [] + [] + [] ) try: return int(str(lst)) except: try: return 1 / 0 except Exception as e: > raise TypeError from e E TypeError tests/samples/formatter_example.py:26: TypeError During handling of the above exception, another exception occurred: capsys = <_pytest.capture.CaptureFixture object at 0x7f8a618fc490> def test_example(capsys): from .samples.formatter_example import bar, print_stack1, format_stack1, format_frame, f_string @contextmanager def check_example(name): yield stderr = capsys.readouterr().err compare_to_file(stderr, name) with check_example("variables"): try: bar() except Exception: > MyFormatter(show_variables=True).print_exception() tests/test_formatter.py:42: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ stack_data/formatting.py:72: in print_exception self.print_lines(self.format_exception(e), file=file) stack_data/formatting.py:83: in print_lines for line in lines: /usr/lib/python3.11/site-packages/typeguard/__init__.py:897: in __next__ return self.send(None) /usr/lib/python3.11/site-packages/typeguard/__init__.py:915: in send value = self.__wrapped.send(obj) stack_data/formatting.py:100: in format_exception yield from self.format_stack(e.__traceback__) /usr/lib/python3.11/site-packages/typeguard/__init__.py:897: in __next__ return self.send(None) /usr/lib/python3.11/site-packages/typeguard/__init__.py:915: in send value = self.__wrapped.send(obj) stack_data/formatting.py:107: in format_stack yield from self.format_stack_data( /usr/lib/python3.11/site-packages/typeguard/__init__.py:897: in __next__ return self.send(None) /usr/lib/python3.11/site-packages/typeguard/__init__.py:915: in send value = self.__wrapped.send(obj) stack_data/formatting.py:118: in format_stack_data for item in stack: /usr/lib/python3.11/site-packages/typeguard/__init__.py:897: in __next__ return self.send(None) /usr/lib/python3.11/site-packages/typeguard/__init__.py:915: in send value = self.__wrapped.send(obj) stack_data/core.py:565: in stack_data yield from collapse_repeated( stack_data/utils.py:84: in collapse_repeated yield from map(mapper, original_group) stack_data/core.py:555: in mapper return cls(f, options) /usr/lib/python3.11/site-packages/typeguard/__init__.py:1033: in wrapper retval = func(*args, **kwargs) stack_data/core.py:520: in __init__ self.executing = Source.executing(frame_or_tb) /usr/lib/python3.11/site-packages/executing/executing.py:335: in executing node = find_node(lasti) /usr/lib/python3.11/site-packages/executing/executing.py:321: in find_node return only( _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ it = <generator object Source.executing.<locals>.find_node.<locals>.<genexpr> at 0x7f8a5ef609a0> def only(it): if hasattr(it, '__len__'): if len(it) != 1: raise NotOneValueFound('Expected one value, found %s' % len(it)) # noinspection PyTypeChecker return list(it)[0] lst = tuple(islice(it, 2)) if len(lst) == 0: > raise NotOneValueFound('Expected one value, found 0') E executing.executing.NotOneValueFound: Expected one value, found 0 /usr/lib/python3.11/site-packages/executing/executing.py:164: NotOneValueFound ----------------------------- Captured stderr call ----------------------------- Traceback (most recent call last): File "formatter_example.py", line 21, in foo 9 | x = 1 10 | lst = ( 11 | [ 12 | x, (...) 18 | + [] 19 | ) 20 | try: --> 21 | return int(str(lst)) ^^^^^^^^^^^^^ 22 | except: [ x, ] = [1] [ x, ] + [] = [1] [ x, ] + [] + [] = [1] [ x, ] + [] + [] + [] = [1] [ x, ] + [] + [] + [] + [] = [1] [ x, ] + [] + [] + [] + [] + [] = [1] lst = [1] n = 0 n - 1 = -1 n > 0 = False str(lst) = '[1]' x = 1 ValueError: invalid literal for int() with base 10: '[1]' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "formatter_example.py", line 24, in foo 21 | return int(str(lst)) 22 | except: 23 | try: --> 24 | return 1 / 0 ^^^^^ 25 | except Exception as e: [ x, ] = [1] [ x, ] + [] = [1] [ x, ] + [] + [] = [1] [ x, ] + [] + [] + [] = [1] [ x, ] + [] + [] + [] + [] = [1] [ x, ] + [] + [] + [] + [] + [] = [1] lst = [1] n = 0 n - 1 = -1 n > 0 = False str(lst) = '[1]' x = 1 ZeroDivisionError: division by zero The above exception was the direct cause of the following exception: Traceback (most recent call last): File "formatter_example.py", line 30, in bar 29 | def bar(): --> 30 | exec("foo()") ^^^^^^^^^^^^^ =============================== warnings summary =============================== ../../../../usr/lib64/python3.11/site-packages/pyximport/pyximport.py:51 /usr/lib64/python3.11/site-packages/pyximport/pyximport.py:51: DeprecationWarning: the imp module is deprecated in favour of importlib and slated for removal in Python 3.12; see the module's documentation for alternative uses import imp -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html =========================== short test summary info ============================ FAILED tests/test_core.py::test_example - executing.executing.NotOneValueFoun... FAILED tests/test_core.py::test_pygments_example - IndexError: list index out... FAILED tests/test_formatter.py::test_example - executing.executing.NotOneValu... =================== 3 failed, 13 passed, 1 warning in 3.03s ==================== ERROR: InvocationError for command /usr/bin/pytest (exited with code 1) ___________________________________ summary ____________________________________ ERROR: py311: commands failed https://docs.python.org/3.11/whatsnew/3.11.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.11/fedora-r… For all our attempts to build python-stack-data with Python 3.11, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/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.11: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/ Let us know here if you have any questions. Python 3.11 is planned to be included in Fedora 37. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.11. 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=2016048 [Bug 2016048] Python 3.11 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2069709

1 9

[Bug 2068421] New: python-executing fails to build with Python 3.11: InvocationError: self.get_executing(inspect.currentframe().f_back)
by bugzilla＠redhat.com 22 Jun '22

22 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=2068421 Bug ID: 2068421 Summary: python-executing fails to build with Python 3.11: InvocationError: self.get_executing(inspect.currentframe().f_back) Product: Fedora Version: rawhide Status: NEW Component: python-executing Assignee: rominf(a)aiven.io Reporter: thrnciar(a)redhat.com CC: epel-packagers-sig(a)lists.fedoraproject.org, lbalhar(a)redhat.com, mhroncok(a)redhat.com, paul.wouters(a)aiven.io, rominf(a)aiven.io, thrnciar(a)redhat.com Blocks: 2016048 (PYTHON3.11) Target Milestone: --- Link ID: Github alexmojaki/executing/pull/31 Classification: Fedora python-executing fails to build with Python 3.11.0a6. + /usr/bin/python3 -m tox --current-env -q --recreate -e py311 Traceback (most recent call last): File "/builddir/build/BUILDROOT/python-executing-0.8.2-2.fc37.x86_64/usr/lib/python3.11/site-packages/executing/executing.py", line 317, in executing args = executing_cache[key] ~~~~~~~~~~~~~~~^^^^^ KeyError: (<code object <module> at 0x7fb5361790d0, file "/builddir/build/BUILD/executing-0.8.2/tests/test_main.py", line 1>, 140416273322192, 552) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/builddir/build/BUILD/executing-0.8.2/tests/test_main.py", line 682, in <module> assert tester([1, 2, 3]) == [1, 2, 3] ^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/executing-0.8.2/tests/utils.py", line 40, in __call__ ex = self.get_executing(inspect.currentframe().f_back) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/executing-0.8.2/tests/utils.py", line 28, in get_executing return Source.executing(frame) ^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILDROOT/python-executing-0.8.2-2.fc37.x86_64/usr/lib/python3.11/site-packages/executing/executing.py", line 372, in executing args = find(source=cls.for_frame(frame), retry_cache=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILDROOT/python-executing-0.8.2-2.fc37.x86_64/usr/lib/python3.11/site-packages/executing/executing.py", line 349, in find node_finder = NodeFinder(frame, stmts, tree, lasti) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILDROOT/python-executing-0.8.2-2.fc37.x86_64/usr/lib/python3.11/site-packages/executing/executing.py", line 626, in __init__ raise RuntimeError(op_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ RuntimeError: CALL ERROR: InvocationError for command /builddir/build/BUILD/executing-0.8.2/.tox/py311/bin/python tests/test_main.py (exited with code 1) ___________________________________ summary ____________________________________ ERROR: py311: commands failed error: Bad exit status from /var/tmp/rpm-tmp.m2JoFZ (%check) Bad exit status from /var/tmp/rpm-tmp.m2JoFZ (%check) Upstream has WIP PR for Python 3.11 suport. The PyFrameObject structure member has been moved to the internal C API headers. While the documentation notes that the PyFrameObject fields are subject to change at any time, they have been stable for a long time and were used in several popular extensions. In Python 3.11, the frame struct was reorganized to allow performance optimizations. Some fields were removed entirely, as they were details of the old implementation. PyFrameObject fields: f_back: use PyFrame_GetBack(). f_blockstack: removed. f_builtins: use PyObject_GetAttrString((PyObject*)frame, "f_builtins"). f_code: use PyFrame_GetCode(). f_gen: removed. f_globals: use PyObject_GetAttrString((PyObject*)frame, "f_globals"). f_iblock: removed. f_lasti: use PyObject_GetAttrString((PyObject*)frame, "f_lasti"). Code using f_lasti with PyCode_Addr2Line() must use PyFrame_GetLineNumber() instead. f_lineno: use PyFrame_GetLineNumber() f_locals: use PyObject_GetAttrString((PyObject*)frame, "f_locals"). f_stackdepth: removed. f_state: no public API (renamed to f_frame.f_state). f_trace: no public API. f_trace_lines: use PyObject_GetAttrString((PyObject*)frame, "f_trace_lines") (it also be modified). f_trace_opcodes: use PyObject_GetAttrString((PyObject*)frame, "f_trace_opcodes") (it also be modified). f_localsplus: no public API (renamed to f_frame.localsplus). f_valuestack: removed. The Python frame object is now created lazily. A side effect is that the f_back member must not be accessed directly, since its value is now also computed lazily. The PyFrame_GetBack() function must be called instead. https://docs.python.org/3.11/whatsnew/3.11.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.11/fedora-r… For all our attempts to build python-executing with Python 3.11, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/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.11: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/ Let us know here if you have any questions. Python 3.11 is planned to be included in Fedora 37. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.11. 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=2016048 [Bug 2016048] Python 3.11 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2068421

1 5

[Bug 2067098] New: ImageMagick: heap-buffer-overflow in PushShortPixel of quantum-private.h [fedora-all]
by bugzilla＠redhat.com 29 May '22

29 May '22

https://bugzilla.redhat.com/show_bug.cgi?id=2067098 Bug ID: 2067098 Summary: ImageMagick: heap-buffer-overflow in PushShortPixel of quantum-private.h [fedora-all] Product: Fedora Version: 35 Status: NEW Component: ImageMagick Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: luya_tfz(a)thefinalzone.net Reporter: trathi(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: blaise(a)gmail.com, dcavalca(a)fb.com, epel-packagers-sig(a)lists.fedoraproject.org, fedora(a)famillecollet.com, luya_tfz(a)thefinalzone.net, michel(a)michel-slm.name, ngompa13(a)gmail.com, pampelmuse(a)gmx.at, sergio(a)serjux.com, troy(a)troycurtisjr.com Target Milestone: --- Classification: Fedora This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2067098

1 4

[Bug 2064538] New: ImageMagick: heap-use-after-free in RelinquishDCMInfo of dcm.c
by bugzilla＠redhat.com 29 May '22

29 May '22

https://bugzilla.redhat.com/show_bug.cgi?id=2064538 Bug ID: 2064538 Summary: ImageMagick: heap-use-after-free in RelinquishDCMInfo of dcm.c Product: Security Response Hardware: All OS: Linux Status: NEW Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: trathi(a)redhat.com CC: blaise(a)gmail.com, dcavalca(a)fb.com, epel-packagers-sig(a)lists.fedoraproject.org, fedora(a)famillecollet.com, jhorak(a)redhat.com, luya_tfz(a)thefinalzone.net, michel(a)michel-slm.name, ngompa13(a)gmail.com, pampelmuse(a)gmx.at, sergio(a)serjux.com, troy(a)troycurtisjr.com Target Milestone: --- Classification: Other A heap-use-after-free vulnerability was found in ImageMagick's RelinquishDCMInfo function of dcm.c. References: https://github.com/ImageMagick/ImageMagick/issues/4947 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2064538

1 10

[Bug 2066640] New: ImageMagick: heap-use-after-free in RelinquishDCMInfo of dcm.c [fedora-all]
by bugzilla＠redhat.com 29 May '22

29 May '22

https://bugzilla.redhat.com/show_bug.cgi?id=2066640 Bug ID: 2066640 Summary: ImageMagick: heap-use-after-free in RelinquishDCMInfo of dcm.c [fedora-all] Product: Fedora Version: 35 Status: NEW Component: ImageMagick Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: luya_tfz(a)thefinalzone.net Reporter: trathi(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: blaise(a)gmail.com, dcavalca(a)fb.com, epel-packagers-sig(a)lists.fedoraproject.org, fedora(a)famillecollet.com, luya_tfz(a)thefinalzone.net, michel(a)michel-slm.name, ngompa13(a)gmail.com, pampelmuse(a)gmx.at, sergio(a)serjux.com, troy(a)troycurtisjr.com Target Milestone: --- Classification: Fedora This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2066640

1 4

2025

2024

2023

2022

2021

Epel-packagers-sig March 2022