Re: Should singularity-container make it to next release?

Path	csiph.com!pasdenom.info!usenet.goja.nl.eu.org!weretis.net!feeder8.news.weretis.net!news.mixmin.net!news2.arglkargh.de!news.karotte.org!fu-berlin.de!bofh.it!news.nic.it!robomod
From	Paul Gevers <elbrus@debian.org>
Newsgroups	linux.debian.devel, linux.debian.security
Subject	Re: Should singularity-container make it to next release?
Date	Thu, 26 Jan 2023 10:00:01 +0100
Message-ID	<FS6gV-1f4y-3@gated-at.bofh.it> (permalink)
References	<FfMsV-dN3y-1@gated-at.bofh.it> <FLXzI-gFnc-17@gated-at.bofh.it> <FM0nT-gHda-7@gated-at.bofh.it> <FQrSy-aOC-25@gated-at.bofh.it> <FRTD3-16Zh-7@gated-at.bofh.it>
X-Original-To	Moritz Muehlenhoff <jmm@inutil.org>, Andreas Tille <tille@debian.org>, Nilesh Patra <nilesh@debian.org>, debian-devel@lists.debian.org, debian-hpc@lists.debian.org, David Trudgian <david.trudgian@sylabs.io>, debian-security@lists.debian.org, Debian Security Team <team@security.debian.org>
X-Mailbox-Line	From debian-devel-request@lists.debian.org Thu Jan 26 08:51:42 2023
Old-Return-Path	<elbrus@debian.org>
X-Amavis-Spam-Status	No, score=-113.579 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, NICE_REPLY_A=-0.089, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, TO_TOO_MANY=1, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no
MIME-Version	1.0
User-Agent	Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0
Content-Language	en-US, nl
Content-Type	multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------pQqslJcK1v60XzVh3GE0nujO"
X-Debian-User	elbrus
X-Mailing-List	<debian-devel@lists.debian.org> archive/latest/354756
List-ID	<debian-devel.lists.debian.org>
List-URL	<https://lists.debian.org/debian-devel/>
List-Archive	https://lists.debian.org/msgid-search/9196186a-2453-8209-c091-8adc49fab8c8@debian.org
Approved	robomod@news.nic.it
Lines	64
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Thu, 26 Jan 2023 09:51:21 +0100
X-Original-Message-ID	<9196186a-2453-8209-c091-8adc49fab8c8@debian.org>
X-Original-References	<20221012160820.r4tjfrz2v6czmz45@nileshpatra.info> <20230109102110.dwrdv56mdvebmkgu@nileshpatra.info> <Y7wWdowf1D0ywoJ5@an3as.eu> <Y8w+UDAWEDPdYNC9@eldamar.lan> <20230125191441.GA17520@inutil.org>
Xref	csiph.com linux.debian.devel:106922 linux.debian.security:6193

Cross-posted to 2 groups.

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi,

On 25-01-2023 20:14, Moritz Muehlenhoff wrote:
> 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

I have forwarded this message as bug #1029669. Unless we get more 
confidence that it's supportable, let's keep it out of stable. I guess 
fasttrack [1] is currently the best forum to supply 
singularity-container to our users.

Paul

[1] https://fasttrack.debian.net/

Back to linux.debian.security | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Re: Should singularity-container make it to next release? Andreas Tille <tille@debian.org> - 2023-01-09 14:30 +0100
  Re: Should singularity-container make it to next release? Salvatore Bonaccorso <carnil@debian.org> - 2023-01-21 20:40 +0100
    Re: Should singularity-container make it to next release? Moritz Muehlenhoff <jmm@inutil.org> - 2023-01-25 20:30 +0100
      Re: Should singularity-container make it to next release? Paul Gevers <elbrus@debian.org> - 2023-01-26 10:00 +0100
        Re: Should singularity-container make it to next release? Nilesh Patra <nilesh@debian.org> - 2023-01-26 10:10 +0100
          Re: Should singularity-container make it to next release? Paul Gevers <elbrus@debian.org> - 2023-01-26 10:40 +0100
          Re: Should singularity-container make it to next release? Sam Hartman <hartmans@debian.org> - 2023-01-26 16:30 +0100
            Re: Should singularity-container make it to next release? Andreas Tille <tille@debian.org> - 2023-01-26 18:00 +0100
              Re: Should singularity-container make it to next release? Nilesh Patra <nilesh@nileshpatra.info> - 2023-01-26 20:50 +0100

csiph-web