A few libraries from the bundled LLVM in swift-lang are exposed in rpm requires and provides by the package. This causes a conflict with the "real" package that provides the same, for example: $ dnf repoquery --quiet --whatprovides 'libLTO.so.17()(64bit)' llvm17-libs-0:17.0.6-9.fc41.x86_64 swift-lang-0:6.0.1-1.fc41.x86_64 There's also liblldb, which conflicts on F39: $ dnf repoquery --quiet --whatprovides 'liblldb.so.17()(64bit)' lldb-0:17.0.1-1.fc39.x86_64 lldb-0:17.0.6-1.fc39.x86_64 swift-lang-0:6.0.1-1.fc39.x86_64 Those bundled libraries in /usr/libexec/swift/6.0.1/lib/ are not even added to the ldconfig path AFAICS, so they really ought to be filtered entirely, per: https://docs.fedoraproject.org/en-US/packaging-guidelines/AutoProvidesAndRequiresFiltering/
I added the two lines below and I think they're right, if there's a way to validate this I'd like to know: %global __provides_exclude_from ^(%{_libexecdir}/%{name}/%{package_version}/lib/.*\\.so.*|%{_libexecdir}/%{name}/%{package_version}/lib64/.*\\.so.*)$ %global __requires_exclude_from ^(%{_libexecdir}/%{name}/%{package_version}/lib/.*\\.so.*|%{_libexecdir}/%{name}/%{package_version}/lib64/.*\\.so.*)$
If you do a local mock build, you can check "rpm -q --provides -p your-file.rpm", and likewise for "--requires". Or in a koji build, you can see it in the rpm info page, like this one: https://koji.fedoraproject.org/koji/rpminfo?rpmID=40168277 I don't think that works for scratch builds, but you could still download the rpms and query them yourself.
FEDORA-2024-0ce53e51ac (swift-lang-6.0.2-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2024-0ce53e51ac
FEDORA-2024-0ce53e51ac (swift-lang-6.0.2-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-24096895a4 (swift-lang-6.0.2-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-24096895a4
FEDORA-2024-4ef3e23eb6 (swift-lang-6.0.2-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-4ef3e23eb6
FEDORA-EPEL-2024-72ca3236a7 (swift-lang-6.0.2-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-72ca3236a7
FEDORA-2024-4ef3e23eb6 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-4ef3e23eb6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-4ef3e23eb6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-24096895a4 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-24096895a4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-24096895a4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-72ca3236a7 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-72ca3236a7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-4ef3e23eb6 (swift-lang-6.0.2-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-24096895a4 (swift-lang-6.0.2-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2024-72ca3236a7 (swift-lang-6.0.2-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.