Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1792789 - kitty fails to build in Fedora 32
Summary: kitty fails to build in Fedora 32
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kitty
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Artem
QA Contact: Fedora Extras Quality Assurance
URL: https://koschei.fedoraproject.org/pac...
Whiteboard:
Depends On:
Blocks: F32FTBFS PYTHON39
TreeView+ depends on / blocked
 
Reported: 2020-01-20 00:22 UTC by Miro Hrončok
Modified: 2020-03-05 19:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-05 19:32:17 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
build.log from Koji (deleted)
2020-01-20 00:22 UTC, Miro Hrončok 		no flags Details
root.log from Koji (deleted)
2020-01-20 00:22 UTC, Miro Hrončok 		no flags Details
View All

Description Miro Hrončok 2020-01-20 00:22:17 UTC 
Created attachment 1653750 [details]
build.log from Koji

Description of problem:
Package kitty fails to build from source in Fedora rawhide.

From reading the logs, I wasn't able to figure out what went actually wrong.

Version-Release number of selected component (if applicable):
0.15.0-1.fc32

Steps to Reproduce:
koji build --scratch f32 kitty-0.15.0-1.fc32.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/kitty

This blocks the Python 3.9 rebuild.
Comment 1 Miro Hrončok 2020-01-20 00:22:54 UTC 
Created attachment 1653751 [details]
root.log from Koji
Comment 2 Ben Cotton 2020-02-11 17:33:03 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.
Comment 3 Fedora Release Engineering 2020-02-16 04:31:31 UTC 
Dear Maintainer,

your package has not been built successfully in 32. Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your package
will be orphaned if this bug remains in NEW state more than 8 weeks.

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

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/33/Schedule
Comment 4 Fedora Release Engineering 2020-03-01 04:23:12 UTC 
Dear Maintainer,

your package has not been built successfully in 32. Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your package
will be orphaned if this bug remains in NEW state more than 8 weeks.

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

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/33/Schedule
Comment 5 Than Ngo 2020-03-05 19:32:17 UTC 
it's fixed in kitty-0.16.0-2
Comment 6 Artem 2020-03-05 19:38:24 UTC 
@Than, thank you!
Note You need to log in before you can comment on or make changes to this bug.