On Tue, Jan 30, 2024 at 04:27:49PM -0500, Robert Edmonds wrote:
> I guess you have to do it that way since there isn't really anything
> universal and machine readable that says: this is the public API header
> file to include to use this library.
Exactly. Though there are good practices (I hesi
Steve Langasek wrote:
> Hi Robert,
>
> On Tue, Jan 30, 2024 at 02:05:11PM -0500, Robert Edmonds wrote:
> > Steve Langasek wrote:
> > > As part of the 64-bit time_t transition required to support 32-bit
> > > architectures in 2038 and beyond
> > > (https://wiki.debian.org/ReleaseGoals/64bit-time),
Hi Robert,
On Tue, Jan 30, 2024 at 02:05:11PM -0500, Robert Edmonds wrote:
> Steve Langasek wrote:
> > As part of the 64-bit time_t transition required to support 32-bit
> > architectures in 2038 and beyond
> > (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
> > avro-c as a s
Steve Langasek wrote:
> As part of the 64-bit time_t transition required to support 32-bit
> architectures in 2038 and beyond
> (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
> avro-c as a source package shipping runtime libraries whose ABI
> either is affected by the change
Source: avro-c
Version: 1.11.1-1
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.d
5 matches
Mail list logo