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
Bug 1927624 - kig: FTBFS in Fedora rawhide
Summary: kig: FTBFS in Fedora rawhide
Alias: None
Product: Fedora
Classification: Fedora
Component: kf5-ktexteditor
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Daniel Vrátil
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-02-11 07:34 UTC by Tomáš Hrnčiar
Modified: 2021-02-11 15:12 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-02-11 14:36:47 UTC
Type: Bug

Attachments (Terms of Use)

Description Tomáš Hrnčiar 2021-02-11 07:34:21 UTC
Description of problem:
Package kig fails to build from source in Fedora rawhide.

Version-Release number of selected component (if applicable):

Steps to Reproduce:
koji build --scratch f34 kig-20.12.2-1.fc34.src.rpm

Additional info:
This package is tracked by Koschei. See:

CMake Error at /usr/share/cmake/Modules/CMakeFindDependencyMacro.cmake:47 (find_package):
  By not providing "FindKF5SyntaxHighlighting.cmake" in CMAKE_MODULE_PATH
  this project has asked CMake to find a package configuration file provided
  by "KF5SyntaxHighlighting", but CMake did not find one.
  Could not find a package configuration file provided by
  "KF5SyntaxHighlighting" (requested version 5.79.0) with any of the
  following names:
  Add the installation prefix of "KF5SyntaxHighlighting" to CMAKE_PREFIX_PATH
  or set "KF5SyntaxHighlighting_DIR" to a directory containing one of the
  above files.  If "KF5SyntaxHighlighting" provides a separate development
  package or SDK, be sure it has been installed.
Call Stack (most recent call first):
  /usr/lib64/cmake/KF5TextEditor/KF5TextEditorConfig.cmake:40 (find_dependency)
  CMakeLists.txt:20 (find_package)
-- Configuring incomplete, errors occurred!

Comment 1 Kevin Kofler 2021-02-11 12:41:51 UTC
Is it really helpful to immediately file FTBFS bugs for transient Koschei errors? Kig built fine in the mass rebuild less than 2 weeks ago. It started failing in Koschei only yesterday. And the reason clearly looks to me like KF5 being broken in Rawhide, nothing that can be done in Kig.

I get many Koschei build failures for my packages, which are usually caused by other packages and typically get fixed within a week. It would be extremely annoying to have to close FTBFS bugs for each of them.

Comment 2 Kevin Kofler 2021-02-11 12:43:54 UTC
> Kig built fine in the mass rebuild less than 2 weeks ago.

Correction: Kig build fine in the mass rebuild 2 weeks and a few hours ago AND had a successful manual build (for a version update) less than 2 weeks ago.

Comment 3 Rex Dieter 2021-02-11 14:22:44 UTC
I'll take a look

Comment 4 Rex Dieter 2021-02-11 14:31:40 UTC

Call Stack (most recent call first):
  /usr/lib64/cmake/KF5TextEditor/KF5TextEditorConfig.cmake:40 (find_dependency)
  CMakeLists.txt:20 (find_package)

Looks like kf5-ktexteditor grew a new dependency, will fix there.

Comment 6 Miro Hrončok 2021-02-11 14:59:57 UTC
> Is it really helpful to immediately file FTBFS bugs for transient Koschei errors?

We needed to check if the package builds with Python 3.10.0a5 and it didn't. The next step was to check if it is Python 3.10.0a5 related or not. According to koschei, it was not, so we filed this bugzilla to get it fixed, so we could try again. I'm glad that you would fix it even without the bugzilla, unfortunately majority of the packagers would not.

If you'd like, we can exclude kig from our Python 3.10 testing and reports.

Comment 7 Kevin Kofler 2021-02-11 15:05:49 UTC
I don't think it's necessary to add an exclusion, because the build is already fixed.

Comment 8 Miro Hrončok 2021-02-11 15:12:31 UTC
I've meant to stop us opening a new bugzilla next time when/if it fails.

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