In this copr repo, I have updated pytest to 7.0.1: https://copr.fedorainfracloud.org/coprs/churchyard/pytest-7/ Based on this PR: https://src.fedoraproject.org/rpms/pytest/pull-request/25 I'd like to update pytest to 7 in Fedora 37, but python-pytest-toolbox 0.4-10 fails to build. https://copr.fedorainfracloud.org/coprs/churchyard/pytest-7/package/python-pytest-toolbox/ ________________________ ERROR collecting test session _________________________ /usr/lib/python3.10/site-packages/pluggy/_hooks.py:265: in __call__ return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult) /usr/lib/python3.10/site-packages/pluggy/_manager.py:80: in _hookexec return self._inner_hookexec(hook_name, methods, kwargs, firstresult) /usr/lib/python3.10/site-packages/pytest_isort.py:52: in pytest_collect_file return IsortItem.from_parent(parent, fspath=path) /usr/lib/python3.10/site-packages/_pytest/nodes.py:633: in from_parent return super().from_parent(parent=parent, fspath=fspath, path=path, **kw) /usr/lib/python3.10/site-packages/_pytest/nodes.py:264: in from_parent return cls._create(parent=parent, **kw) /usr/lib/python3.10/site-packages/_pytest/nodes.py:140: in _create return super().__call__(*k, **kw) /usr/lib/python3.10/site-packages/pytest_isort.py:160: in __init__ super(IsortItem, self).__init__(name=path, parent=parent, **kwargs) /usr/lib/python3.10/site-packages/_pytest/nodes.py:686: in __init__ self._check_item_and_collector_diamond_inheritance() /usr/lib/python3.10/site-packages/_pytest/nodes.py:708: in _check_item_and_collector_diamond_inheritance warnings.warn( E pytest.PytestWarning: IsortItem is an Item subclass and should not be a collector, however its bases File are collectors. E Please split the Collectors and the Item into separate node types. E Pytest Doc example: https://docs.pytest.org/en/latest/example/nonpython.html E example pull request on a plugin: https://github.com/asmeurer/pytest-flakes/pull/40/ There are several packages affected by this update, so I'd very much appreciate it if you could fix this failure. Please, check if your upstream hasn't already fixed it and backport the fix if possible. Report this failure to your upstream otherwise. If you need specific help, let me know. Thanks!
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37.
Upstream is no longer maintaining this module. Now retired.
Could you please also retire it in f38? Just merging this https://src.fedoraproject.org/rpms/python-pytest-toolbox/pull-request/2 should do it.
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.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.