For the time being, I revert the addition of LLVM10 to Tumbleweed (no snapshot broken yet) So this means I have to resubmit llvm10? I hope licensedigger remembers the

http://bugzilla.opensuse.org/show_bug.cgi?id=1168935 http://bugzilla.opensuse.org/show_bug.cgi?id=1168935#c1 Aaron Puchert changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Aaron Puchert --- That's essentially the same issue as bug 1164454 previously, which is fortunately easy to fix: https://build.opensuse.org/request/show/792561. I should probably have submitted this together with the llvm10 addition. (In reply to Dominique Leuenberger from comment #0) previous request so we don't have to wait for that again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1168935 http://bugzilla.opensuse.org/show_bug.cgi?id=1168935#c3 --- Comment #3 from Aaron Puchert --- (In reply to Dominique Leuenberger from comment #0)

e.g. mozjs68 is unresolvable with: nothing provides clang-tools = 9.0.1 needed by clang9-devel, (got version 10.0.0-1.1) (llvm10 was last built, winning this time inside OBS; for the repo it could be different)

There is another issue here: clang-devel requires clang9-devel, which in turn requires clang-tools = 9.0.1. Now if I remove clang-tools from llvm9, that package is no longer installable. Luckily clang-tools is only a pro-forma requirement, since CMake complains about missing binaries otherwise, but these binaries aren't typically needed for development, only the libraries are. (Which is annoying, and hopefully I get around to fixing that some time.) So we can just drop the versioning requirement, and take any version of clang-tools for clangX-devel. (https://build.opensuse.org/request/show/792576) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1168935 http://bugzilla.opensuse.org/show_bug.cgi?id=1168935#c5 --- Comment #5 from Aaron Puchert --- (In reply to Dominique Leuenberger from comment #4)

(In reply to Aaron Puchert from comment #1)

...

...

For the time being, I revert the addition of LLVM10 to Tumbleweed (no snapshot broken yet) So this means I have to resubmit llvm10? I hope licensedigger remembers the previous request so we don't have to wait for that again.

No need; I actually worked around it a bit more complex, but with less effort for you: build disabled/binaries wiped; just have to remember to enable this again when llvm10 switch is checked in (together with the llvm9 fix, which is now staged)

Thanks, that's good to hear. For the future I'll add a note to llvm's README.packaging that the new version and the changes to the old version should be submitted together to avoid duplicate binaries in the meantime. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1168935 http://bugzilla.opensuse.org/show_bug.cgi?id=1168935#c7 Aaron Puchert changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED Flags|needinfo?(dimstar@opensuse. | |org) | --- Comment #7 from Aaron Puchert --- Builds seem to be on again, and there are no duplicate binaries according to https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashbo.... So I'll close this. -- You are receiving this mail because: You are on the CC list for the bug.