On 26 January 2023 10:26:05 pm IST, Andreas Tille wrote:
>Am Thu, Jan 26, 2023 at 08:22:15AM -0700 schrieb Sam Hartman:
>>
>> Well, if you and a group of people believe you can maintain it in stable
>> given the additional discussions ith upstream, then explicitly say
>> you're ready to sign u
Am Thu, Jan 26, 2023 at 08:22:15AM -0700 schrieb Sam Hartman:
>
> Well, if you and a group of people believe you can maintain it in stable
> given the additional discussions ith upstream, then explicitly say
> you're ready to sign up to maintaining in stable.
> I think that's the kind of sing-up-t
> "Nilesh" == Nilesh Patra writes:
Nilesh> Since I had done quite a bit of work on this, I'm a sad to
Nilesh> see this happen, as fasttrack still has much less visibility
Nilesh> / availability than an official stable release, or even
Nilesh> backports.
Well, if you and a gro
Hi Nilesh,
On 26-01-2023 10:06, Nilesh Patra wrote:
I guess something that changed since then is that upstream is aware
about it and can help a bit with backporting. However the onus to
maintain it in stable is still on the maintainer and security@ (to some
extent)
It is bit of a high-effort mai
On Thu, Jan 26, 2023 at 09:51:21AM +0100, Paul Gevers wrote:
> 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 b
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 relea
6 matches
Mail list logo
