Source: singularity-container Severity: serious -------- Forwarded Message -------- Subject: Re: Should singularity-container make it to next release? Resent-Date: Wed, 25 Jan 2023 19:25:56 +0000 (UTC) Resent-From: [email protected] Date: Wed, 25 Jan 2023 20:14:41 +0100 From: Moritz Muehlenhoff <[email protected]>To: Andreas Tille <[email protected]>, Nilesh Patra <[email protected]>, [email protected], [email protected], David Trudgian <[email protected]>, [email protected], Debian Security Team <[email protected]>
On Sat, Jan 21, 2023 at 08:34:40PM +0100, Salvatore Bonaccorso wrote:
So in my understanding of the above the situation around singularity-container, which lead for buster to https://bugs.debian.org/917867 and keeping it out of the stable release, did not really change in the aspect of beeing able to patch vulnerabilities to the stable branch once upstream versions moved on, is this correct interpretation? In context from #917867, it was even in stretch at first, but needed to be removed after stretch was released in a point release. If this is correct, then we probably should not include singularity-container in bookworm, better than possibly need to remove it after bookworm release in a point release.
Agreed.
Cheers,
Moritz
OpenPGP_signature
Description: OpenPGP digital signature
