Bug 2448259 - qt5-doctools: rebuild against libclang 21
Summary: qt5-doctools: rebuild against libclang 21
Keywords:
Status: ON_QA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: qt5-qttools
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-16 22:01 UTC by Carl George 🤠
Modified: 2026-04-01 01:22 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:
than: mirror+


Attachments (Terms of Use)

Description Carl George 🤠 2026-03-16 22:01:24 UTC
Description of problem:
The current version of qt5-doctools in EPEL 10.2 and 10.2 was built against libclang 20.  libclang has been updated to 21 in CentOS 10, which is also expected to land in RHEL 10.2 soon.  To avoid installation and upgrade problems, qt5-doctools needs to be rebuilt.


Version-Release number of selected component (if applicable):
qt5-doctools-5.15.18-1.el10_2


How reproducible:
always


Steps to Reproduce:
1. dnf install qt5-doctools
2. dnf upgrade


Actual results:
Error: 
 Problem 1: package qt5-doctools-5.15.18-1.el10_2.x86_64 from @System requires libclang.so.20.1()(64bit), but none of the providers can be installed
  - package qt5-doctools-5.15.18-1.el10_2.x86_64 from @System requires libclang.so.20.1(LLVM_13)(64bit), but none of the providers can be installed
  - cannot install both clang-libs-21.1.8-1.el10.x86_64 from appstream and clang-libs-21.1.6-1.el10.x86_64 from @System
  - cannot install both clang-libs-21.1.8-1.el10.x86_64 from appstream and clang-libs-20.1.2-1.el10.x86_64 from appstream
  - cannot install both clang-libs-21.1.8-1.el10.x86_64 from appstream and clang-libs-20.1.4-1.el10.x86_64 from appstream
  - cannot install both clang-libs-21.1.8-1.el10.x86_64 from appstream and clang-libs-20.1.8-1.el10.x86_64 from appstream
  - cannot install both clang-libs-21.1.8-1.el10.x86_64 from appstream and clang-libs-21.1.6-1.el10.x86_64 from appstream
  - cannot install the best update candidate for package qt5-doctools-5.15.18-1.el10_2.x86_64
  - cannot install the best update candidate for package clang-libs-21.1.6-1.el10.x86_64
 Problem 2: problem with installed package qt5-doctools-5.15.18-1.el10_2.x86_64
  - package qt5-doctools-5.15.18-1.el10_2.x86_64 from @System requires libclang.so.20.1()(64bit), but none of the providers can be installed
  - package qt5-doctools-5.15.18-1.el10_2.x86_64 from @System requires libclang.so.20.1(LLVM_13)(64bit), but none of the providers can be installed
  - package qt5-doctools-5.15.18-1.el10_2.x86_64 from epel requires libclang.so.20.1()(64bit), but none of the providers can be installed
  - package qt5-doctools-5.15.18-1.el10_2.x86_64 from epel requires libclang.so.20.1(LLVM_13)(64bit), but none of the providers can be installed
  - package clang-libs-21.1.6-1.el10.x86_64 from @System requires clang-resource-filesystem(x86-64) = 21.1.6-1.el10, but none of the providers can be installed
  - package clang-libs-21.1.6-1.el10.x86_64 from appstream requires clang-resource-filesystem(x86-64) = 21.1.6-1.el10, but none of the providers can be installed
  - package clang-libs-20.1.2-1.el10.x86_64 from appstream requires clang-resource-filesystem(x86-64) = 20.1.2-1.el10, but none of the providers can be installed
  - package clang-libs-20.1.4-1.el10.x86_64 from appstream requires clang-resource-filesystem(x86-64) = 20.1.4-1.el10, but none of the providers can be installed
  - package clang-libs-20.1.8-1.el10.x86_64 from appstream requires clang-resource-filesystem(x86-64) = 20.1.8-1.el10, but none of the providers can be installed
  - cannot install both clang-resource-filesystem-21.1.8-1.el10.x86_64 from appstream and clang-resource-filesystem-21.1.6-1.el10.x86_64 from @System
  - cannot install both clang-resource-filesystem-21.1.8-1.el10.x86_64 from appstream and clang-resource-filesystem-20.1.2-1.el10.x86_64 from appstream
  - cannot install both clang-resource-filesystem-21.1.8-1.el10.x86_64 from appstream and clang-resource-filesystem-20.1.4-1.el10.x86_64 from appstream
  - cannot install both clang-resource-filesystem-21.1.8-1.el10.x86_64 from appstream and clang-resource-filesystem-20.1.8-1.el10.x86_64 from appstream
  - cannot install both clang-resource-filesystem-21.1.8-1.el10.x86_64 from appstream and clang-resource-filesystem-21.1.6-1.el10.x86_64 from appstream
  - cannot install the best update candidate for package clang-resource-filesystem-21.1.6-1.el10.x86_64


Expected results:
successful upgrade

Comment 1 Than Ngo 2026-03-17 10:01:38 UTC
I will work on it. Thanks for the info!

Comment 2 Carl George 🤠 2026-03-19 15:51:09 UTC
> in EPEL 10.2 and 10.2

This was a typo, and should have been EPEL 10.2 and 10.3.  Sorry for any confusion due to that.

Comment 3 Fedora Update System 2026-03-31 17:50:58 UTC
FEDORA-EPEL-2026-c203d6e8e4 (qt5-qttools-5.15.18-2.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-c203d6e8e4

Comment 4 Fedora Update System 2026-03-31 17:51:18 UTC
FEDORA-EPEL-2026-81f9a4affb (qt5-qttools-5.15.18-2.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-81f9a4affb

Comment 5 Fedora Update System 2026-04-01 01:15:54 UTC
FEDORA-EPEL-2026-c203d6e8e4 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-c203d6e8e4

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

Comment 6 Fedora Update System 2026-04-01 01:22:59 UTC
FEDORA-EPEL-2026-81f9a4affb has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-81f9a4affb

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


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