Am 11.11.19 um 14:34 schrieb Felix Miata:
This seems to be a regular happening whenever a major libLLVM version change occurs, happened 5>6, 6>7, 7>8 IIRC. Shouldn't the old be removed by the zypper dup that provides the new?
There are three issues here: * Packages that build against the unversioned metapackages llvm-devel, clang-devel etc. start linking with the new version only when they are rebuilt. The version update of the metapackage itself doesn't trigger a rebuild, probably because it doesn't contain actual libraries. That's currently not the case though, all packages have been rebuilt. * Some packages need older versions of libLLVM. One example is the Glasgow Haskell compiler ghc, which is still using llvm6. Then there are ldc, a D compiler, and beignet, an OpenCL implementation, that use llvm7. Currently there seems to be no package using llvm8, but I can't remove it before llvm6 & llvm7. (Because one of these mentioned packages might update to llvm8.) You can see the build dependencies of llvm versions with osc whatdependson openSUSE:Factory llvm<n> standard x86_64 and runtime dependencies of libLLVM.so with zypper search --requires 'libLLVM.so.<n>()(64bit)' That doesn't show ghc-compiler though, which needs the llvm executables. (Probably llc.) * I think zypper is conservative about removing libraries. You need at least "solver.cleandepsOnRemove = true" in /etc/zyp/zypp.conf. I'm not sure whether that's enough though. Best regards, Aaron -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org