[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aD8Ox7DFbYB6JJkG@voyager>
Date: Tue, 3 Jun 2025 17:03:35 +0200
From: Markus Wichmann <nullplan@....net>
To: musl@...ts.openwall.com
Cc: David Steele <david@...ackrest.org>
Subject: Re: Possible issue formatting epoch time with strftime()
Am Mon, Jun 02, 2025 at 07:33:41PM +0000 schrieb David Steele:
> Ubuntu 22.04 (UTC) gcc:
>
> local epoch: 1573222014
> utc epoch: 1573240014
> local time: 20191108-090654
> utc time: 20191108-140654
>
> [...]
>
> Alpine 3.21 (America/New_York or UTC) gcc/musl:
>
> local epoch: 1573222014
> utc epoch: 1573222014 <------
> local time: 20191108-090654
> utc time: 20191108-140654
>
I think what happened here is that musl is currently implementing
non-standard extension behavior that is no longer conforming as of last
year. My reading of POSIX-2024 is that strftime() is to treat the
incoming timestamp as local time, at least for the purpose of a %s
conversion. Which it isn't at the moment. But POSIX-2018 did not
specify %s at all, so musl was allowed to do whatever until POSIX-2024.
Ciao,
Markus
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
