Bug 2101853

Summary: F37FailsToInstall: koji-containerbuild
Product: [Fedora] Fedora Reporter: Miro Hrončok <mhroncok>
Component: koji-containerbuildAssignee: Clement Verna <clems.verna>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: admiller, clems.verna, code, infra-sig, kevin, vrutkovs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: koji-containerbuild-1.0.1-1.fc37 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-07 01:35:11 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: 2045109    

Description Miro Hrončok 2022-06-28 14:44:50 UTC

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

Your package (koji-containerbuild) Fails To Install in Fedora 37:

can't install koji-containerbuild:
  - nothing provides python3.11dist(jsonschema) = 3.2 needed by koji-containerbuild-0.16.0-2.fc37.noarch
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.

If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.

P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock:

    $ mock -r fedora-37-x86_64 --disablerepo='*' --enablerepo=local install koji-containerbuild

P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages


Comment 1 Ben Beasley 2022-06-28 15:49:23 UTC
The exactly-versioned upstream dependency on jsonschema 3.2.0[1] can probably be loosened. Typical use of jsonschema is not affected by changes from 3.x to 4.x.

[1] https://github.com/containerbuildsystem/koji-containerbuild/blob/1e6864e9d48706364e03e844f8a8e4aacb2ba314/requirements.txt#L1

Comment 2 Kevin Fenzi 2022-06-29 23:38:45 UTC
Filed an upstream issue on this: https://github.com/containerbuildsystem/koji-containerbuild/issues/242

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

Comment 4 Miro Hrončok 2022-10-14 10:59:56 UTC

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

All subpackages of a package against which this bug was filled are now installable or removed from Fedora 38.

Thanks for taking care of it!

Comment 5 Fedora Update System 2022-11-28 20:50:02 UTC
FEDORA-2022-08e60d4026 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-08e60d4026

Comment 6 Fedora Update System 2022-11-29 02:31:32 UTC
FEDORA-2022-08e60d4026 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-08e60d4026`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-08e60d4026

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

Comment 7 Fedora Update System 2022-12-07 01:35:11 UTC
FEDORA-2022-08e60d4026 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.