Bug 1921552 - Missing debuginfo package for python3.9 on Fedora 33
Summary: Missing debuginfo package for python3.9 on Fedora 33
Keywords:
Status: CLOSED DUPLICATE of bug 1912116
Alias: None
Product: Fedora
Classification: Fedora
Component: python3.9
Version: 33
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-28 07:17 UTC by Orange Kao
Modified: 2021-01-28 07:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-28 07:30:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Orange Kao 2021-01-28 07:17:17 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.96 Safari/537.36
Build Identifier: 

In Fedora 33 @updates-debuginfo repo, debugsource package is available for python3.9, but debuginfo is missing

Reproducible: Always

== Steps to Reproduce ==
1. sudo dnf update
2. sudo dnf debuginfo-install python3

== Actual Results ==
python3.9-debugsource is available, but python3.9-debuginfo is not

$ sudo dnf list installed python3
Installed Packages
python3.x86_64      3.9.1-2.fc33       @updates

$ sudo dnf list installed python3.9*
Installed Packages
python3.9-debugsource.x86_64    3.9.1-2.fc33   @updates-debuginfo

== Expected Results ==
Both python3.9-debugsource and python3.9-debuginfo should be available

== Additional info ==
Browsing the Fedora updates-debuginfo repo indicates
* On f32, debuginfo for python 3.9 do exist
* On f33, debuginfo for python3 3.5~3.8 do exist, but not 3.9

On my f33 machine, building from source python3.9-3.9.1-2.fc33.src.rpm can generate python3.9-debuginfo-3.9.1-2.fc33.x86_64.rpm . But I don't know where is the build log of Fedora official build.

Comment 1 Miro Hrončok 2021-01-28 07:30:39 UTC

*** This bug has been marked as a duplicate of bug 1912116 ***


Note You need to log in before you can comment on or make changes to this bug.