Hi release team,

Debian testing autoremoval watch <[email protected]> (2026-09-14):
> tasksel 3.90 is marked for autoremoval from testing on 2026-10-12
> 
> It (build-)depends on packages with these RC bugs:
> 1084954: llvm-toolchain-19: llvm-toolchain-*: assembly code seems to depend 
> on build cpu capabilities
>  https://bugs.debian.org/1084954
> 1095866: llvm-19: llvm-toolchain-19: unsoundness/miscompilations on i386
>  https://bugs.debian.org/1095866
> 1124069: llvm-toolchain-19: Don't include in forky
>  https://bugs.debian.org/1124069
> 1124098: spirv-llvm-translator-19: depends on llvm 19
>  https://bugs.debian.org/1124098
> 1133251: liboffload-19: liboffload-19 has an undeclared file conflict on 
> /usr/lib/llvm-19/lib/libomptarget.so.19.1
>  https://bugs.debian.org/1133251
> 1142869: llvm-toolchain-19: FTBFS: fatal error: 'linux/scc.h' file not found
>  https://bugs.debian.org/1142869
> 1145338: spirv-llvm-translator-19: FTBFS: error: line 67: 
> NonSemantic.Shader.DebugInfo.200 DebugTypeBasic: expected operand Flags must 
> be a result id of 32-bit unsigned OpConstant
>  https://bugs.debian.org/1145338
> 1145981: sos: CVE-2026-79655
>  https://bugs.debian.org/1145981
> 1146296: django-oauth-toolkit: FTBFS: E           AttributeError
>  https://bugs.debian.org/1146296

While the previous round 2 months ago was mainly about packages pulled
by desktop tasks (something that one could consider actionable and/or
within our shared perimeter with desktop maintainers), this particular
round is quite different…

The first three bullet points of [1] are definitely not something I'm
going to sign up for, so it'd be nice to have a game plan to keep
tasksel (and blendsel, same story) in testing once we get closer to the
autoremoval date.

  1. 
https://wiki.debian.org/Autoremoval?pow_referer=#What_do_I_do_when_the_release_critical_.28RC.29_bug_is_not_in_my_package.3F

What course of action would you recommend here?


Cheers,
-- 
Cyril Brulebois ([email protected])            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Attachment: signature.asc
Description: PGP signature

Reply via email to