On Tue, Feb 06, 2024 at 10:48:21PM -0800, tony mancill wrote:
> The full debdiff is attached, but it's mostly comprised of
> non-functional build system and autoconf drift. A pared-down diff with
> only the packaging and true (semantic) upstream changes is attached as
> well.
Thank you, this is r
On Tue, Feb 06, 2024 at 06:01:43PM +, Jonathan Wiltshire wrote:
> On Tue, Jul 25, 2023 at 10:19:50PM +0100, Jonathan Wiltshire wrote:
> > Control: tag -1 moreinfo
> >
> > On Mon, Dec 05, 2022 at 11:22:51PM -0800, tony mancill wrote:
> > > As the upstream author notes in [3], the issue is prese
On Tue, Jul 25, 2023 at 10:19:50PM +0100, Jonathan Wiltshire wrote:
> Control: tag -1 moreinfo
>
> On Mon, Dec 05, 2022 at 11:22:51PM -0800, tony mancill wrote:
> > As the upstream author notes in [3], the issue is present in inlined
> > code, thus applications built against capnproto must be rebu
Control: tag -1 moreinfo
On Mon, Dec 05, 2022 at 11:22:51PM -0800, tony mancill wrote:
> As the upstream author notes in [3], the issue is present in inlined
> code, thus applications built against capnproto must be rebuilt against
> the patched version.
This doesn't immediately make any of us en
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: capnpr...@packages.debian.org
Control: affects -1 + src:capnproto
Dear Release Team,
This is a bit of an odd one... I have contacted the Security Team and
they have
5 matches
Mail list logo
