Bug#964550: clang-10: Version handling/naming for RC releases

Sylvestre Ledru sylvestre at debian.org
Thu Jul 9 10:17:30 BST 2020

Le 09/07/2020 à 11:01, Sedat Dilek a écrit :
> On Wed, Jul 8, 2020 at 5:32 PM Sylvestre Ledru <sylvestre at debian.org> wrote:
>>> As pointed out by Sylvestre in [3] he is trying to keep packages in the Debian repositories
>>> in balance with <apt.llvm.org>.
>>> As I am interested in having the best packages in Debian I am reporting here not upstream.
>> As I said in the llvm bt, it is very unlikely to happen. This isn't a big deal and it doesn't break any tool :)
> Can you enlighten me what you mean by "balance"?
> And the correlation with the version naming/handling you have chosen?

It is tricky because of the situation between:
* apt.llvm.org with three branches
* stable packages (ex: 10.0)
* rc packages (ex: 10.0.1 rc4)
* snapshot from the VCS (ex: 11~++20200701093119+ffee8040534-1~exp1)

And you can have llvm-toolchain-9 from Debian official, -10 for apt.llvm.org and -11 from Debian experimental.

I need to make sure that the expected behavior is what users are getting
and that the upgrade path still works (upgrading from version x-1 to x).
Changing this is always a lot of work as it requires synchronized uploads/updating scripts
(not mentioning the potential regressions)

Anyway, I am not sure to see what your point beside consistency in Debian (note that, AFAIK? there isn't any policy).
I have been using that patterns since the svn => git upstream migration (it was similar with git).
And at the end, Debian Stable only ships with clear versions like 10.0.1-12.


More information about the Pkg-llvm-team mailing list