Bug 30818 - mingw32(64)-python3 packages cannot be installed due to unsatisfied python3.10-devel.
Summary: mingw32(64)-python3 packages cannot be installed due to unsatisfied python3.1...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Python Stack Maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-06 11:11 CEST by Aurelian R
Modified: 2022-09-06 22:27 CEST (History)
1 user (show)

See Also:
Source RPM: migw-python3, python3
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Aurelian R 2022-09-06 11:11:41 CEST 
Latest version of mingw-python3 packages introduced a hard dependency on python3.10-devel package which is missing, but most likely not named that way(libpython3.10-devel?). 

How reproducible:
Always

Steps to Reproduce:

$ urpmi mingw32-python3 --test
A requested package cannot be installed:
mingw32-python3-3.10.6-1.mga9.noarch (due to unsatisfied python3.10-devel)
Continue installation anyway? (Y/n) n
Comment 1 Aurelian R 2022-09-06 14:26:09 CEST 
By replacing in mingw-python3's spec file the 2 occurrences of line

"Requires:      python%{py_ver}-devel" 
with

"Requires:      python3-devel"

worked out just fine.

Regards.
Comment 2 Marja Van Waes 2022-09-06 18:52:13 CEST 
(In reply to Aurelian R from comment #1)
> By replacing in mingw-python3's spec file the 2 occurrences of line
> 
> "Requires:      python%{py_ver}-devel" 
> with
> 
> "Requires:      python3-devel"
> 
> worked out just fine.
> 
> Regards.

Thanks for the report and for figuring that out.

Assigning to the python stack maintainers.

Assignee: bugsquad => python
CC: (none) => marja11

Comment 3 Aurelian R 2022-09-06 22:27:20 CEST 
python3-3.10.6-2.mga9 providing python3-devel fixed the issue.
Great, this was a short-lived bug.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.