[Bug 2127970] Update Released

[Andreas Hasenack]

The verification of the Stable Release Update for rust-coreutils has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to coreutils-from in Ubuntu.
https://bugs.launchpad.net/bugs/2127970

Title:
  [Ubuntu 25.10 Questing] rust coreutils "date -r file" returns a wrong
  date

Status in coreutils-from package in Ubuntu:
  Confirmed
Status in rust-coreutils package in Ubuntu:
  Fix Committed
Status in coreutils-from source package in Questing:
  Won't Fix
Status in rust-coreutils source package in Questing:
  Fix Released
Status in coreutils-from source package in Resolute:
  Won't Fix
Status in rust-coreutils source package in Resolute:
  Fix Committed

Bug description:
  [Impact]
  date -r reports current date instead of date specified by reference file. This makes files look "too new", causing for example backup scripts to not run their backups because they think the backups are current, and possible other mayhem.

  [Test plan]
  Take a file older than now, and check that the output of

  date -r <file>

  matches

  gnudate -r <file>

  (except for localization)

  If the build passes, then the included test case
  test_date_for_file_mtime also passed. Date has a regression test suite
  as well checking other code paths for basic functionality and past
  fixes.

  [Where problems could occur]
  The change is straightforward and only affects the code using `-r`, adding the specified file as a date source and using that if specified. This uses an enum member that is newly added, and a match statement. Match statements are exhaustive so the compiler effectively guarantees us that this only affects date -r and no other code paths.

  [Original bug report]
  Ubuntu 25.10 Questing came with this rust coreutils "date" command version:

  $ date -V
  date (uutils coreutils) 0.2.2

  Problem is that the command "date -r file", that will return the last
  modification time of the given file, is returning a wrong date, in
  fact, is returning the current date:

  Example given, this file "/usr/bin/bash":
  -rwxr-xr-x 1 root root 1608840 Sep  8 15:20 /usr/bin/bash*

  The command "date -r /usr/bin/bash" correct return will be:

  Mon Sep  8 15:20:42 CEST 2025

  But instead of that rust coreutils returns the current date:

  $ /usr/bin/date -r /usr/bin/bash
  Thu Oct 16 10:18:41 CEST 2025

  The gnu coreutils works as expected and returns the last modification
  date of the given file:

  $ /usr/bin/gnudate -r /usr/bin/bash
  Mon Sep  8 15:20:42 CEST 2025

  IMHO this is a very urgent to fix bug. We've noticed it because a
  couple of our monitor scripts started to act weird triggering date
  warnings for files that were untouched.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils-from/+bug/2127970/+subscriptions