Bug 2114557

Summary: python-nose2: FTBFS in Fedora rawhide/f37
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: python-nose2Assignee: Ben Beasley <code>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: code
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: python-nose2-0.12.0-1.fc37 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-12 17:39:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 2045102, 2107826, 2117176    
Description Flags
state.log none

Description Fedora Release Engineering 2022-08-02 19:42:23 UTC
python-nose2 failed to build from source in Fedora rawhide/f37


For details on the mass rebuild see:

Please fix python-nose2 at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
python-nose2 will be orphaned. Before branching of Fedora 38,
python-nose2 will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:

Comment 1 Fedora Release Engineering 2022-08-02 19:42:26 UTC
Created attachment 1903084 [details]

file build.log too big, will only attach last 32768 bytes

Comment 2 Fedora Release Engineering 2022-08-02 19:42:28 UTC
Created attachment 1903085 [details]

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2022-08-02 19:42:29 UTC
Created attachment 1903086 [details]

Comment 4 Tomáš Hrnčiar 2022-08-09 10:44:37 UTC
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 37.
Action is required from you.

PYC magic number has changed in Python 3.11.0b4, and all packages with Python
bytecode need to be
rebuilt. Most of them were rebuilt during the Fedora 37 mass rebuild, but since
package is FTBFS, we were hoping you could fix it and rebuild it manually, or
it will cause subtle issues when used.

Tracking bugzilla for all affected packages:

If you can fix your package to build, perform a build in koji, and if
necessary, create
an update in bodhi. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this
Bugzilla report.

Note that Fedora 37 is about to be branched very soon.
If you fix this after branching, make sure to rebuild the package in both
Rawhide (Fedora 38) and Fedora 37.


Following the policy for FTBFS packages [1], your package will be orphaned if
this bug remains in a NEW state for more than 8 weeks (not sooner than

A week before the mass branching of Fedora 38 according to the
schedule [2],
any packages not successfully rebuilt, at least on Fedora 36 will
retired regardless of the status of this bug.


Comment 5 Ben Cotton 2022-08-09 13:35:26 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 6 Fedora Update System 2022-08-25 15:00:15 UTC
FEDORA-2022-9e5617e5a6 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9e5617e5a6

Comment 7 Fedora Update System 2022-08-26 10:32:59 UTC
FEDORA-2022-9e5617e5a6 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-9e5617e5a6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9e5617e5a6

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

Comment 8 Fedora Update System 2022-09-12 17:39:35 UTC
FEDORA-2022-9e5617e5a6 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.