Bug#947165: transition: llvm-defaults to 9

2020-01-12 Thread Paul Gevers
Control: tags -1 confirmed

Hi,

On 03-01-2020 07:56, Paul Gevers wrote:
> We currently have a bit much transitions going on (and some backslash
> from a piuparts bug), so I'd like to get a bit of those transitions off
> the table before starting this one.
> 
> I'll let you know, probably in a week or so.

Please go ahead.

Paul



Bug#947165: transition: llvm-defaults to 9

2020-01-02 Thread Paul Gevers
Control: tags -1 - moreinfo

Hi,

> They build-depend on llvm/clang, not sure whether they are actually part 
> of the transition.

I worked a bit on the tracker page and I think it has a better view of
what is involved (basically limiting "Affected" to the -dev packages
from llvm-defaults).

We currently have a bit much transitions going on (and some backslash
from a piuparts bug), so I'd like to get a bit of those transitions off
the table before starting this one.

I'll let you know, probably in a week or so.

Paul



Bug#947165: transition: llvm-defaults to 9

2020-01-01 Thread Adrian Bunk
On Fri, Dec 27, 2019 at 10:43:11AM +0100, Paul Gevers wrote:
>...
> > Besides rustc, it should not have an impact on rust.
> 
> But rustc is having issues migrating, so this is something I am worried
> about.

rustc hardcodes the llvm version (and already uses 9),
so rustc is not part of this transition.

> Also, do you understand why rust-bindgen and rust-clang-sys are
> mentioned in the tracker? I looked *briefly* but didn't spot the
> connection yet.
>...

They build-depend on llvm/clang, not sure whether they are actually part 
of the transition.

According to dak they are leaf packages in bullseye,
so potential rust related issues with this transition
could be handled with removal hints.

> Paul

cu
Adrian



Bug#947165: transition: llvm-defaults to 9

2019-12-27 Thread Paul Gevers
Hi Sylvestre,

On 27-12-2019 10:46, Sylvestre Ledru wrote:
>> But rustc is having issues migrating, so this is something I am worried
>> about. Also, do you understand why rust-bindgen and rust-clang-sys are
>> mentioned in the tracker? I looked *briefly* but didn't spot the
>> connection yet.
> 
> They depends on llvm/clang packages. A rebuild should fix them.

But rebuilding isn't enough, they need to migrate to testing.
rust-bindgen hasn't migrated since 2019-10-23, it's currently blocked by
rustc (but that can't have been the problem in the beginning). rustc
isn't migrating since 2019-11-28, although it might just make it
tomorrow, if not blocked by e.g. *rust-clang-sys*. rust-clang-sys needs
a fix for a failing autopkgtest, otherwise it won't migrate (already in
that state for 30 days). Packages like rust-glob haven't migrated for
163 days, so it seems to me the whole rust stack is interwoven and it
needs more coordination by the rust maintainers to get it moving to testing.

A bit of elaboration on how this is all supposed to work might help us
understanding the situation such that we can help if needed.

Paul



Bug#947165: transition: llvm-defaults to 9

2019-12-27 Thread Sylvestre Ledru



Le 27/12/2019 à 10:43, Paul Gevers a écrit :



What happens if rebuilt packages don't migrate to testing? I'm
seeing rust package in the picture

Besides rustc, it should not have an impact on rust.

But rustc is having issues migrating, so this is something I am worried
about. Also, do you understand why rust-bindgen and rust-clang-sys are
mentioned in the tracker? I looked *briefly* but didn't spot the
connection yet.


They depends on llvm/clang packages. A rebuild should fix them.

Build-Depends: [...]  libclang-dev , llvm, clang

Build-Depends: [...] clang




https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916837

How is the support for -6.0? Could be serious in my book.


yeah. I bump the deps, not this one.

Doing it now :)

About 7:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947438

S



Bug#947165: transition: llvm-defaults to 9

2019-12-27 Thread Paul Gevers
Hi Sylvestre,

On 26-12-2019 22:18, Sylvestre Ledru wrote:
>> Just to get it clear, this is only switching the default from 8 to 9,
>> right?

> And rebuild packages to depend on -9.

Sure; for those that don't hard-code the version.

>> What happens if rebuilt packages don't migrate to testing? I'm
>> seeing rust package in the picture

> Besides rustc, it should not have an impact on rust.

But rustc is having issues migrating, so this is something I am worried
about. Also, do you understand why rust-bindgen and rust-clang-sys are
mentioned in the tracker? I looked *briefly* but didn't spot the
connection yet.

> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916837

How is the support for -6.0? Could be serious in my book.

Paul



Bug#947165: transition: llvm-defaults to 9

2019-12-26 Thread Sylvestre Ledru



Le 26/12/2019 à 21:40, Paul Gevers a écrit :

Control: tags -1 moreinfo

Hi Sylvestre,

On 22-12-2019 11:57, Sylvestre Ledru wrote:

LLVM 9.0.1 has just been released. I am not planning to spend significant time 
on the -8 branch.
It is therefor time to move to the version 9

Just to get it clear, this is only switching the default from 8 to 9,
right?

And rebuild packages to depend on -9.

What happens if rebuilt packages don't migrate to testing? I'm
seeing rust package in the picture

Besides rustc, it should not have an impact on rust.

and it seems to me that those need
some coordination that I am currently not seeing in order to migrate.

Side question, will you be taking care of *removing* some branches from
unstable/testing as well? It seems to me that we are have a bit too many
currently: llvm-toolchain-6.0, llvm-toolchain-7, llvm-toolchain-8 and
llvm-toolchain-9 are the ones I know about.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916837

Good point for -7, I forgot to fill it :)

Thanks

S



Bug#947165: transition: llvm-defaults to 9

2019-12-26 Thread Paul Gevers
Control: tags -1 moreinfo

Hi Sylvestre,

On 22-12-2019 11:57, Sylvestre Ledru wrote:
> LLVM 9.0.1 has just been released. I am not planning to spend significant 
> time on the -8 branch.
> It is therefor time to move to the version 9

Just to get it clear, this is only switching the default from 8 to 9,
right? What happens if rebuilt packages don't migrate to testing? I'm
seeing rust package in the picture and it seems to me that those need
some coordination that I am currently not seeing in order to migrate.

Side question, will you be taking care of *removing* some branches from
unstable/testing as well? It seems to me that we are have a bit too many
currently: llvm-toolchain-6.0, llvm-toolchain-7, llvm-toolchain-8 and
llvm-toolchain-9 are the ones I know about.

Paul



Bug#947165: transition: llvm-defaults to 9

2019-12-22 Thread Sylvestre Ledru

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hello,

LLVM 9.0.1 has just been released. I am not planning to spend significant time 
on the -8 branch.
It is therefor time to move to the version 9

Thanks,
Sylvestre

Ben file:

title = "llvm-defaults";

Affected: .depends ~ /(clang|llvm)1?-?[3456789]/
Good: .depends ~ /(clang|llvm)1?-?[9]/
Bad: .depends ~ /(clang|llvm)1?-?[345678]/