Hi Sebastian,
On Tue, Apr 09, 2024 at 06:18:13PM +0200, Sebastian Andrzej Siewior wrote:
> On 2024-04-07 23:46:28 [+0200], To Adam D. Barratt wrote:
> > On 2024-03-24 20:06:12 [+], Adam D. Barratt wrote:
> > >
> > > Sorry for not getting to this sooner. Is this still the case?
> >
> > So.
On 2024-04-07 23:46:28 [+0200], To Adam D. Barratt wrote:
> On 2024-03-24 20:06:12 [+], Adam D. Barratt wrote:
> >
> > Sorry for not getting to this sooner. Is this still the case?
>
> So. This happened #1068045 (yapet broke with 1.0 format) due to the
> update. On the bright side it has
On 2024-03-24 20:06:12 [+], Adam D. Barratt wrote:
>
> Sorry for not getting to this sooner. Is this still the case?
So. This happened #1068045 (yapet broke with 1.0 format) due to the
update. On the bright side it has been broken in unstable but unnoticed.
Looking into it but also sleeping
On 2024-03-24 20:06:12 [+], Adam D. Barratt wrote:
> On Mon, 2024-03-04 at 07:38 +0100, Sebastian Andrzej Siewior wrote:
> > This is an update to the current stable OpenSSL release in the 3.0.x
> > series. It addresses the following CVE reports which were postponed
> > due to low severity:
>
On Mon, 2024-03-04 at 07:38 +0100, Sebastian Andrzej Siewior wrote:
> This is an update to the current stable OpenSSL release in the 3.0.x
> series. It addresses the following CVE reports which were postponed
> due to low severity:
[...]
> I'm not aware of a problems/ regression at this point.
Package: release.debian.org
Control: affects -1 + src:openssl
X-Debbugs-Cc: open...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
X-Debbugs-Cc: sebast...@breakpoint.cc
Severity: normal
This is an update to the current stable OpenSSL release in the
6 matches
Mail list logo
