On 2025-02-12 10:52, Tim Parenti via tz wrote:
On Wed, 12 Feb 2025 at 03:53, Alejandro Colomar wrote:
Even if that's non-standard, as long as it's a valid GNU date, I'm happy
with it.
I put much more detailed thoughts on both immediate-term fixes and longer-
term suggestions on GitHub where they were first requested:
<https://github.com/shadow-maint/shadow/issues/1202>
But, within the scope of this conversation, it mostly boils down to adding
one further qualification: "as long as it's a valid GNU date /which matches
the actual behavior of the system/"
GNU date(1) interprets such "yyyy-mm-ddZ" constructions as 00:00 UTC, but
in casual conversation, expiration dates are generally assumed to mean 24:00
by convention unless otherwise specified. Depending on the actual behavior
of your system, being more explicit at the expense of some verbosity may be
a better longer-term/transitional choice.
Unfortunately date dislikes 24:00 and requires Z-24:00 or Z+1day (YMMV):
$ date -u -d2023-09-30T24:00:00Z
date: invalid date ‘2023-09-30T24:00:00Z’
$ date -u -d2023-09-30Z-24:00
2023 Oct 01 Sun 00:00:00
$ date -u -d2023-09-30Z+1day
2023 Oct 01 Sun 00:00:00
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry
