Bug 2354131

Summary:	python-towncrier FTBFS due to missing tox configuration
Product:	[Fedora] Fedora	Reporter:	Miro Hrončok <mhroncok>
Component:	python-towncrier	Assignee:	Jonathan Wright <jonathan>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	eclipseo, fti-bugs, jonathan, python-packagers-sig
Target Milestone:	---	Flags:	mhroncok: needinfo? (jonathan)
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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, 2339435, 2371891, 2371977

Description Miro Hrončok 2025-03-21 16:34:12 UTC

Hello.

python-towncrier 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 Miro Hrončok 2025-03-28 12:42:04 UTC

Hello. If you need help fixing this, please let me know. If you plan to fix this yourself, please respond. Thanks.

Comment 2 Miro Hrončok 2025-04-18 09:37:34 UTC

Hello. If you need help fixing this, please let me know. If you plan to fix this yourself, please respond. Thanks.

Comment 3 Fedora Admin user for bugzilla script actions 2025-05-17 06:18:58 UTC

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 4 Fedora Admin user for bugzilla script actions 2025-06-07 02:20:27 UTC

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 5 Karolina Surma 2025-06-11 16:05:22 UTC

*** Bug 2372171 has been marked as a duplicate of this bug. ***

Comment 6 Fedora Fails To Install 2025-06-20 19:51:59 UTC

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/

This package fails to install and maintainers are advised to take one of the following actions:

 - Fix this bug and close this bugzilla once the update makes it to the repository.
   (The same script that posted this comment will eventually close this bugzilla
   when the fixed package reaches the repository, so you don't have to worry about it.)

or

 - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet.

or

 - Orphan the package if you no longer plan to maintain it.


If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue.
This package may be orphaned in 7+ weeks.
This is the first reminder (step 3) from the policy.

Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.