On Fri, Mar 18, 2022 at 10:22:57PM +0100, Sebastian Andrzej Siewior wrote:
> On 2022-03-18 14:51:32 [+], Adam D. Barratt wrote:
> > Boo. Hope you're doing better.
>
> Thanks, yes.
>
> > > I would also do the upload for Buster, would that work? I remember
> > > that
> > > the packages, that
On 2022-03-18 14:51:32 [+], Adam D. Barratt wrote:
> Boo. Hope you're doing better.
Thanks, yes.
> > I would also do the upload for Buster, would that work? I remember
> > that
> > the packages, that broken, were already uploaded a few cycles ago.
>
> Also as 1.1.1n?
Yes.
> I assume there
On Fri, 2022-03-18 at 14:12 +0100, Sebastian Andrzej Siewior wrote:
> On 2022-03-18 09:21:50 [+], Adam D. Barratt wrote:
> > Apologies if the status here got confused - based on the above, I
> > was
> > assuming that in the absence of a negative response you would
> > proceed
> > with the
On 2022-03-18 09:21:50 [+], Adam D. Barratt wrote:
> Apologies if the status here got confused - based on the above, I was
> assuming that in the absence of a negative response you would proceed
> with the 1.1.1n-0+deb11u1 plan. For complete clarity, please feel free
> to do so, bearing in
On Wed, 2022-03-09 at 08:45 +0100, Sebastian Andrzej Siewior wrote:
> On 2022-02-19 17:57:25 [+], Adam D. Barratt wrote:
> > Feel free to upload; we'll wait for the d-i ack before accepting
> > the
> > package into p-u.
>
> There will be the release of 1.1.1n on Tuesday 15th March 2022
>
Sebastian Andrzej Siewior (2022-03-09):
> On 2022-02-19 17:57:25 [+], Adam D. Barratt wrote:
> > Feel free to upload; we'll wait for the d-i ack before accepting the
> > package into p-u.
>
> There will be the release of 1.1.1n on Tuesday 15th March 2022 including
> a security fix. Therefore
On 2022-02-19 17:57:25 [+], Adam D. Barratt wrote:
> Feel free to upload; we'll wait for the d-i ack before accepting the
> package into p-u.
There will be the release of 1.1.1n on Tuesday 15th March 2022 including
a security fix. Therefore I will:
- prepare a security release against
On 2022-02-19 17:57:25 [+], Adam D. Barratt wrote:
>
> Feel free to upload; we'll wait for the d-i ack before accepting the
> package into p-u.
Okay. The Bullseye package has been uploaded.
> Regards,
>
> Adam
Sebastian
On Sat, 2022-02-19 at 18:52 +0100, Sebastian Andrzej Siewior wrote:
> On 2022-02-19 17:04:16 [+], Adam D. Barratt wrote:
> > Control: tags -1 + confirmed d-i
> …
> > Thanks. Assuming the above is still accurate, then this looks good
> > to
> > me.
> >
> > As the package builds a udeb, it will
On 2022-02-19 17:04:16 [+], Adam D. Barratt wrote:
> Control: tags -1 + confirmed d-i
…
> Thanks. Assuming the above is still accurate, then this looks good to
> me.
>
> As the package builds a udeb, it will need a d-i ack; tagging and CCing
> accordingly.
I'm confused. May I upload or do I
Control: tags -1 + confirmed d-i
On Tue, 2022-01-11 at 00:00 +0100, Sebastian Andrzej Siewior wrote:
> This is an update to the latest stable update of the openssl package
> provided by upstream. It contains fixes for bugs which were not
> identified as security critical but still worth fixing.
>
Processing control commands:
> tags -1 + confirmed d-i
Bug #1003484 [release.debian.org] bullseye-pu: package openssl/1.1.1m-0+deb11u1
Added tag(s) confirmed and d-i.
--
1003484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003484
Debian Bug Tracking System
Contact ow...@bugs.debian.org
12 matches
Mail list logo
