Hi Xavier,

Thanks for passing that on, I think it's about what I expected but it's good to 
see the actual reports.

I don't think we're likely to change these APIs away from using time_t, at 
least not in the short term, so the incompatibility will continue to exist and 
need to be packaged around.

I do hope to at least get the header situation cleaned up so that they're 
properly usable as installed, my WIP on this is at 
https://github.com/cyrusimap/cyrus-imapd/pull/4798

Cheers,

ellie

On Sat, 17 Feb 2024, at 2:16 PM, Yadd wrote:
> Hi Ellie,
>
> here you'll find a better analysis of time_t potential problems.
>
> Cheers,
> Xavier
>
>
> -------- Forwarded Message --------
> Subject: Bug#1061341: Some headers are still unusable
> Resent-Date: Fri, 16 Feb 2024 20:27:01 +0000
> Resent-From: Adrien Nader <adr...@notk.org>
> Resent-To: debian-bugs-d...@lists.debian.org
> Resent-CC: Debian Cyrus Team <team+cy...@tracker.debian.org>
> Date: Fri, 16 Feb 2024 21:23:40 +0100
> From: Adrien Nader <adr...@notk.org>
> Reply-To: Adrien Nader <adr...@notk.org>, 1061...@bugs.debian.org
> To: 1061...@bugs.debian.org
>
> On Fri, Feb 16, 2024, Adrien Nader wrote:
>> I was able to analyze the library after modifying auth.h (actually
>> cyrus/*.h) to use cyrus/strarray.h and skipping bitvector.h. The
>> analysis returns that the library is both time_t and LFS sensitive. I
>> will publish a report soon (hopefully this evening but I can't
>> guarantee it).
>
> I've pushed updated results. You can find the ones for cyrus-dev at
> https://adrien.dcln.fr/misc/armhf-time_t/2024-02-16T21%3A19%3A00/compat_reports/cyrus-dev/
>
> -- 
> Adrien

------------------------------------------
Cyrus: Devel
Permalink: 
https://cyrus.topicbox.com/groups/devel/T95c76ae933c0a082-M0434b30838a9ab9060903a76
Delivery options: https://cyrus.topicbox.com/groups/devel/subscription

Reply via email to