Description
When a user pulls the debian or ubuntu "qualification" packages from apt.llvm.org, they are currently getting an unreleased version number: 20.1.7 (as of writing 20.1.6 is the current release).
Presumably this is due to pulling from the 20.x branch rather than the llvmorg-20.1.6 label.
For this issue I see two possible solutions:
-
Update the CI system to build from the label, necessitating either a manual step to update labels when releases are tagged or some fancy scripting work trying to match patterns on available labels to determine if a suitable on is now available.
-
Beef up the documentation on apt.llvm.org to make it clear that the "qualification" packages track the git branch, not release labels. If this is also the case for "stable" do that as well. It should be obvious that this is how development works, as there are no release labels for that to attempt to use.
This has had some discussion in this discourse thread
I believe this issue should have the packaging label, but I don't seem to be able to apply it.