Your message dated Sat, 5 Oct 2024 09:51:48 +0200
with message-id <[email protected]>
and subject line Re: Bug#1081194: LLVM 19: lowering severity, and please remove 
your removal hint
has caused the Debian Bug report #1081194,
regarding llvm-toolchain-19: block migration to testing: too many 
llvm-toolchain versions in testing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1081194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081194
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: llvm-toolchain-18
Version: 1:18.1.3-1
Severity: serious
X-Debbugs-Cc: [email protected], [email protected]

Currently we we have llvm-toolchain-{14,15,16,17} in testing whereas RC
bugs in the verious versions of llvm-toolchain do not get addressed:

#1067005 in llvm-toolchain-18
#1068185 and #1057586 in llvm-toolchain-16
#1036596 and #1068840 in llvm-toolchain-14

Seeing that some of the bugs are unaddressed for a long time, that many
versions of llvm-toolchain in the archive seem to be to much to handle
for the maintainers. As there is also no progress in removing old
versions from the archive, I propose to not let any new versions of
llvm-toolchain-X migrate to trixie until the number of versions is
reduced to a maintainable number.

Please do not downgrade or close this bug report before contacting the
release team.

Cheers
-- 
Sebastian Ramacher

--- End Message ---
--- Begin Message ---
On 2024-10-05 08:04:48 +0200, Sylvestre Ledru wrote:
> 
> Le 04/10/2024 à 23:52, Sebastian Ramacher a écrit :
> > On 2024-09-15 21:05:46 +0200, Sylvestre Ledru wrote:
> > > Hello,
> > > 
> > > Le 15/09/2024 à 20:11, Sebastian Ramacher a écrit :
> > > > To move forward in this regard, we would like to ask the LLVM
> > > > maintainers to provide us with a plan for trixie. Which llvm-toolchain
> > > > versions are you planning to release with? Which llvm-toolchain version
> > > > should be the default version (llvm-defaults is currently pointing to
> > > > 16). If we are aware of your plans, we can help with getting reverse
> > > > dependencies to migrate or in the worst case removed from testing.
> > > I would like to upgrade llvm-defaults to 19 when it 19.1.0 is released 
> > > (in a
> > > few weeks)
> > Okay, let's do that then. But …
> > 
> > > And starts to fill bugs when it is done
> > … have these bugs been filed?
> 
> Sorry, by "it", i meant uploaded!

This was a little to fast with llvm-toolchain-19 not being in testing
yet. With filing bugs I also meant bugs for failures from a test rebuild
with 19 as default. Sorry for being inprecise.

It's too late now. I will wait until llvm-toolchan-19 migrated to
testing and then will schedule binNMUs.

But let's continue this discussion in the other bug.

> I filled a lot of bugs to move away from 17 already
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081250
> 
> > Also, please file a transition bug against
> > release.debian.org to track this change.
> 
> Done and uploaded!
> 
> Could you please remove the block on 1081194 to make sure llvm-toolchain--19
> can moves to testing?

I meant to close the bug with my last mail. Doing it now.

Cheers
-- 
Sebastian Ramacher

--- End Message ---

Reply via email to