Comment # 3 on bug 1179155 from
For the install check issues below we can either add SLE specific conflicts
(they will not work with factory based llvm7/9 packages and thus likely Leap)
or update the llvm7 stack to the package setup of Factory (there's shuffling
around of binaries into a new clang-tools package) and do the same for llvm9.
I'd rather not split sources in SP3 so updating llvm7 means updating the
package
setup for SP1+ and llvm9 means updating for SP2+ (but none of the affected
packages are actually shipped on the media there for llvm9 as opposed to
llvm7 which accidentially got fully shipped for SP1).  For llvm5 of :GA there's
still the hard Conflicts: llvm5 in the Factory packages.

That said, we can also simply ignore the issue since clang-tools is not
supposed to be on the SP3 media (but on PackageHub - where the issue
might or might not be a blocker there)

### [install check & file conflicts for x86_64]

found conflict of clang-tools-11.0.0-3.2.x86_64 with clang7-7.0.1-3.13.1.x86_64
  /usr/bin/clang-format-diff
  /usr/bin/clang-tidy-diff
  /usr/bin/git-clang-format
  /usr/bin/run-clang-tidy

found conflict of clang-tools-11.0.0-3.2.x86_64 with llvm7-7.0.1-3.13.1.x86_64
  /usr/bin/hmaptool

found conflict of clang-tools-11.0.0-3.2.x86_64 with llvm9-9.0.1-3.3.1.x86_64
  /usr/bin/hmaptool


You are receiving this mail because: