date: rfc-822 shows time off by an hour

[NickJackolson]

Machine Info:

$ uname -a
Linux localhost 7.0.0-15-generic #15-Ubuntu SMP PREEMPT Wed Apr 22 15:04:00 UTC 2026 s390x GNU/Linux

$ date --version
date (uutils coreutils) 0.8.0

When timezone is set to UTC rfc-822 matches the time

$ timedatectl show
Timezone=Etc/UTC
LocalRTC=no
CanNTP=yes
NTP=yes
NTPSynchronized=yes
TimeUSec=Mon 2026-06-01 12:55:55 UTC

$ date
Mon Jun  1 12:54:58 PM UTC 2026

$ date --rfc-822 -d "1970/01/01 UTC $(date '+%s') seconds"
Mon, 01 Jun 2026 12:54:55 +0000

When timezone is set to CEST rfc-822 output is off by one hour

$ timedatectl show
Timezone=Europe/Berlin
LocalRTC=no
CanNTP=yes
NTP=yes
NTPSynchronized=yes
TimeUSec=Mon 2026-06-01 14:57:52 CEST

$ date
Mon Jun  1 02:57:16 PM CEST 2026

$ date --rfc-822 -d "1970/01/01 UTC $(date '+%s') seconds"
Mon, 01 Jun 2026 15:57:19 +0200

$ date --rfc-822 -d "1970/01/01 CEST $(date '+%s') seconds"
Mon, 01 Jun 2026 14:02:07 +0200

[sylvestre]

seems that it still happens with 0.9.0

[NickJackolson]

I was just checking that:

$ git log --oneline -1
b286558423b5 (HEAD -> main, origin/main, origin/HEAD) chown/chgrp/chmod/rm: open recursive descent with O_NOFOLLOW

$ git status
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean

$ cargo run date --version
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.16s
     Running `target/debug/coreutils date --version`
date (uutils coreutils) 0.9.0

$ cargo run date
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.16s
     Running `target/debug/coreutils date`

Mon Jun  1 03:20:30 PM CEST 2026    <----------------------

$ cargo run date --rfc-822 -d "1970/01/01 UTC $(date '+%s') seconds"
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.16s
     Running `target/debug/coreutils date --rfc-822 -d '1970/01/01 UTC 1780320032 seconds'`

Mon, 01 Jun 2026 16:20:32 +0200       <----------------------