[Bug] - `clang19-resource-filesystem` conflicts with `clang-resource-filesystem`

[phongn]

Describe the bug When attempting to install both clang19 and clang (15), I see package conflicts between clang19-resource-filesystem and clang-resource-filesystem.

This behavior does not occur when installing both clang and clang18 or installing both clang18 and clang19.

To Reproduce

dnf install clang clang19

Expected behavior The expected behavior is that all the packages included with for clang and clang19 install without problem.

Screenshots

bash-5.2# dnf install clang clang19
Last metadata expiration check: 0:06:00 ago on Tue Oct 28 20:41:08 2025.
Error:
 Problem: conflicting requests
  - package clang-15.0.6-3.amzn2023.0.2.aarch64 from amazonlinux requires clang-libs(aarch-64) = 15.0.6-3.amzn2023.0.2, but none of the providers can be installed
  - package clang-15.0.7-3.amzn2023.0.1.aarch64 from amazonlinux requires clang-libs(aarch-64) = 15.0.7-3.amzn2023.0.1, but none of the providers can be installed
  - package clang-15.0.7-3.amzn2023.0.2.aarch64 from amazonlinux requires clang-libs(aarch-64) = 15.0.7-3.amzn2023.0.2, but none of the providers can be installed
  - package clang-15.0.7-3.amzn2023.0.3.aarch64 from amazonlinux requires clang-libs(aarch-64) = 15.0.7-3.amzn2023.0.3, but none of the providers can be installed
  - package clang-15.0.7-3.amzn2023.0.4.aarch64 from amazonlinux requires clang-libs(aarch-64) = 15.0.7-3.amzn2023.0.4, but none of the providers can be installed
  - package clang-libs-15.0.6-3.amzn2023.0.2.aarch64 from amazonlinux requires clang-resource-filesystem(aarch-64) = 15.0.6, but none of the providers can be installed
  - package clang-libs-15.0.7-3.amzn2023.0.1.aarch64 from amazonlinux requires clang-resource-filesystem(aarch-64) = 15.0.7, but none of the providers can be installed
  - package clang-libs-15.0.7-3.amzn2023.0.2.aarch64 from amazonlinux requires clang-resource-filesystem(aarch-64) = 15.0.7, but none of the providers can be installed
  - package clang-libs-15.0.7-3.amzn2023.0.3.aarch64 from amazonlinux requires clang-resource-filesystem(aarch-64) = 15.0.7, but none of the providers can be installed
  - package clang-libs-15.0.7-3.amzn2023.0.4.aarch64 from amazonlinux requires clang-resource-filesystem(aarch-64) = 15.0.7, but none of the providers can be installed
  - package clang19-resource-filesystem-19.1.7-13.amzn2023.0.1.aarch64 from amazonlinux conflicts with clang-resource-filesystem < 19.99 provided by clang-resource-filesystem-15.0.6-3.amzn2023.0.2.aarch64 from amazonlinux
  - package clang19-resource-filesystem-19.1.7-13.amzn2023.0.1.aarch64 from amazonlinux conflicts with clang-resource-filesystem < 19.99 provided by clang-resource-filesystem-15.0.7-3.amzn2023.0.1.aarch64 from amazonlinux
  - package clang19-resource-filesystem-19.1.7-13.amzn2023.0.1.aarch64 from amazonlinux conflicts with clang-resource-filesystem < 19.99 provided by clang-resource-filesystem-15.0.7-3.amzn2023.0.2.aarch64 from amazonlinux
  - package clang19-resource-filesystem-19.1.7-13.amzn2023.0.1.aarch64 from amazonlinux conflicts with clang-resource-filesystem < 19.99 provided by clang-resource-filesystem-15.0.7-3.amzn2023.0.3.aarch64 from amazonlinux
  - package clang19-resource-filesystem-19.1.7-13.amzn2023.0.1.aarch64 from amazonlinux conflicts with clang-resource-filesystem < 19.99 provided by clang-resource-filesystem-15.0.7-3.amzn2023.0.4.aarch64 from amazonlinux
  - package clang19-libs-19.1.7-13.amzn2023.0.1.aarch64 from amazonlinux requires clang19-resource-filesystem(aarch-64) = 19.1.7-13.amzn2023.0.1, but none of the providers can be installed
  - package clang19-19.1.7-13.amzn2023.0.1.aarch64 from amazonlinux requires libclang-cpp.so.19.1()(64bit), but none of the providers can be installed
  - package clang19-19.1.7-13.amzn2023.0.1.aarch64 from amazonlinux requires libclang-cpp.so.19.1(LLVM_19.1)(64bit), but none of the providers can be installed
  - package clang19-19.1.7-13.amzn2023.0.1.aarch64 from amazonlinux requires clang19-libs(aarch-64) = 19.1.7-13.amzn2023.0.1, but none of the providers can be installed
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)

Test Environment (please complete the following information):

• OS Release: Amazon Linux release 2023.9.20251020 (Amazon Linux)
• Container: public.ecr.aws/amazonlinux/amazonlinux:2023
• Container Runtime: Rancher Desktop 1.20.0 on macOS 15.7.1
• Container Architectures: aarch64, x86_64
• Container run command: docker run --platform=linux/arm64 --pull=always -i -t -v public.ecr.aws/amazonlinux/amazonlinux:2023 /bin/bash (and also --platform=linux/amd64

[ozbenh]

Looks like a bogus conflict statement, probably due to how it adds an RPM macro, that was missed while namespacing. The contents of the 2 packages don't actually conflict as far as I can tell... we'll fix this