Bug 2292916

Summary:	Requesting rename of the package to python-python-multipart
Product:	[Fedora] Fedora	Reporter:	Charalampos Stratakis <cstratak>
Component:	python-multipart	Assignee:	Miro Hrončok <mhroncok>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	carl, mhroncok, python-packagers-sig
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	python-multipart-0.2.5-1.fc41	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-18 18:32:26 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:	2292930
Bug Blocks:	2244836, 2290560, 2291495, 2292013, 2292225

Description Charalampos Stratakis 2024-06-18 15:51:54 UTC

Hello,

The python-multipart upstream project[0] is packaged as python-multipart in Fedora. However we'll need to package  different project named multipart[1] as a dependency of the buildbot software (python-treq) requires it to build with Python 3.13.

This is a problem currently as both packages share the name. The ideal situation from an RPM point of view would be to package the upstream python-multipart as python-python-multipart (essentially a rename that will create a new package) and switch the current python-multipart RPM to the upstream multipart project and adding Conflict tags for the two packages.

[0] https://github.com/Kludex/python-multipart
[1] https://github.com/defnull/multipart

Reproducible: Always

Comment 1 Miro Hrončok 2024-06-18 15:59:37 UTC

Opened https://src.fedoraproject.org/rpms/python-multipart/pull-request/3 to repurpuse the package.

Comment 2 Miro Hrončok 2024-06-18 16:06:00 UTC

And opened https://src.fedoraproject.org/rpms/python-multipart/pull-request/4 to rename this package (to be imported into the new distgit).

Comment 3 Miro Hrončok 2024-06-18 17:00:36 UTC

I tested the upgrade path via https://copr.fedorainfracloud.org/coprs/churchyard/multipart/builds/

When I have a dependent package installed:

# dnf upgrade
Installing dependencies:
 python3-python-multipart         noarch     0.0.9-1.fc41   copr:copr.fedorainfracloud.org:churchyard:multipart  217.9 KiB
   replacing python3-multipart    noarch     0.0.9-3.fc41   rawhide                                              217.9 KiB

When I don't have a dependent package installed:

# dnf upgrade
Upgrading:
 python3-multipart                noarch     0.2.5-1.fc41   copr:copr.fedorainfracloud.org:churchyard:multipart   44.1 KiB
   replacing python3-multipart    noarch     0.0.9-3.fc41   rawhide                                              217.9 KiB

Works kinda as expected. Does not block the upgrade path either way.

Comment 4 Fedora Update System 2024-06-18 18:28:47 UTC

FEDORA-2024-e0b451e1b0 (python-multipart-0.2.5-1.fc41 and python-python-multipart-0.0.9-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-e0b451e1b0

Comment 5 Fedora Update System 2024-06-18 18:32:26 UTC

FEDORA-2024-e0b451e1b0 (python-multipart-0.2.5-1.fc41 and python-python-multipart-0.0.9-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 2024-08-14 12:55:23 UTC

FEDORA-EPEL-2024-c266816b44 (python-python-multipart-0.0.9-7.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-c266816b44

Comment 7 Fedora Update System 2024-08-14 14:52:26 UTC

FEDORA-EPEL-2024-c266816b44 (python-python-multipart-0.0.9-7.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.