Bug 2354102

Summary: python-eth-keyfile FTBFS due to missing tox configuration
Product: [Fedora] Fedora Reporter: Miro Hrončok <mhroncok>
Component: python-eth-keyfileAssignee: Peter Lemenkov <lemenkov>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: lemenkov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-eth-keyfile-0.9.1-1.fc41 python-eth-keyfile-0.9.1-1.fc42 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-04-05 01:25:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2322407, 2339432    

Description Miro Hrončok 2025-03-21 16:32:09 UTC
Hello.

python-eth-keyfile fails to build from source becasue it uses one or both of:

 - %pyproject_buildrequires -t/-e (generate dependencies via tox)
 - %tox (run tox)

without tox configuration (e.g. tox.ini or tox section of pyproject.toml/setup.cfg).

This was always supposed to fail, but regressed with tox 4.
Now it fails again.

https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/ZSHSHZKVA4XJQBJD7FMMCALKN4UP5SAJ/
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/N25A2BER3RUHMTBIULQ6AVWRILSL5VGW/

If this package uses tox upstream, make sure to use a source tarball that includes the tox configuration (e.g. an archive from GitHub instead of sdist from PyPI).

If this package does not use tox upstream, you cannot use the tox options.
If your package uses %pyproject_buildrequires -t/-e but does not use %tox, just drop the -t/-e option.
If your package uses %tox, replace the call with a more suitable way for running tests (e.g. %pytest).

Let me know if you need assistance. Thanks.

Comment 1 Fedora Update System 2025-03-27 13:53:42 UTC
FEDORA-2025-4257d57ce7 (python-eth-keyfile-0.9.1-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4257d57ce7

Comment 2 Fedora Update System 2025-03-27 13:53:45 UTC
FEDORA-2025-3f39f9c430 (python-eth-keyfile-0.9.1-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-3f39f9c430

Comment 3 Fedora Update System 2025-03-28 15:26:18 UTC
FEDORA-2025-3f39f9c430 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-3f39f9c430`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-3f39f9c430

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2025-03-28 16:18:15 UTC
FEDORA-2025-4257d57ce7 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-4257d57ce7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4257d57ce7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2025-04-05 01:25:57 UTC
FEDORA-2025-4257d57ce7 (python-eth-keyfile-0.9.1-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2025-04-11 18:21:43 UTC
FEDORA-2025-3f39f9c430 (python-eth-keyfile-0.9.1-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.