From: "Pádraig Brady" <P@draigBrady.com>
To: Jelle de Jong <jelledejong@powercraft.nl>, 63784@debbugs.gnu.org
Subject: bug#63784: date --date "1 month ago" +%Y-%m does not work as expected on day 31
Date: Mon, 29 May 2023 15:27:13 +0100 [thread overview]
Message-ID: <b87d1a02-ff58-b239-1de8-bc83abc90fac@draigBrady.com> (raw)
In-Reply-To: <d7795b0b-3ee2-d937-d337-59bb90f5e715@powercraft.nl>
On 29/05/2023 12:55, Jelle de Jong wrote:
> Hello everybody,
>
> I been hitting an issue for a while now that date commands return the
> wrong month on day 31 of a month and my automations stops working on
> correctly on these days.
>
> root@sydney:~# date
> Wed Aug 31 22:09:04 CEST 2022
> root@sydney:~# date --date "1 month ago" +%Y-%m
> 2022-07
> root@sydney:~# date --date "2 month ago" +%Y-%m
> 2022-07
> root@sydney:~# date --date "3 month ago" +%Y-%m
> 2022-05
> root@sydney:~# date --date "4 month ago" +%Y-%m
> 2022-05
>
> root@sydney:~# date
> Sat Dec 31 19:20:13 CET 2022
> root@sydney:~# date --date '1 month ago' +%Y-%m
> 2022-12
>
> $ date --version
> date (GNU coreutils) 8.30
> Copyright (C) 2018 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
>
> I would love to have this fixed if possible.
>
> If I am using the wrong command I would love to be educated as well.
> Should I use date --date "$(date +%Y-%m-01) -1 month" +%Y-%m instead...
Yes that is confusing.
The current workaround is to operate relative to the middle of the month as described at:
https://www.gnu.org/software/coreutils/faq/coreutils-faq.html#The-date-command-is-not-working-right_002e
prev parent reply other threads:[~2023-05-29 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 11:55 bug#63784: date --date "1 month ago" +%Y-%m does not work as expected on day 31 Jelle de Jong
2023-05-29 14:27 ` Pádraig Brady [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b87d1a02-ff58-b239-1de8-bc83abc90fac@draigBrady.com \
--to=p@draigbrady.com \
--cc=63784@debbugs.gnu.org \
--cc=jelledejong@powercraft.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).