https://bugzilla.suse.com/show_bug.cgi?id=1192429 https://bugzilla.suse.com/show_bug.cgi?id=1192429#c11 Richard Biener <rguenther@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(meissner@suse.com | |) --- Comment #11 from Richard Biener <rguenther@suse.com> --- (In reply to Marcus Meissner from comment #10)
i masked the SLE binary conflict now and pushed it into the qa pipeline.
(it has correct conflicts I hope)
llvm5 is in 15-sp2 legacy only, so eol with end of 15-sp2 in a month. llvm7 is actively supported currently, no eol set as there is no newer llvmX in sles yet.
There will not be any newer llvmX in sles (there is pieces of llvm9 and llvm11 but only the parts required by the graphics stack runtime are shipped and supported). The idea is that llvmX (and clangX) will come from PackageHub and thus be not L3 supported (apart from the graphics stack requirements, as said). Is there a way to make llvm7 EOL somehow without providing a (L3) supported replacement? -- You are receiving this mail because: You are on the CC list for the bug.