64-bit time_t functions are not implemented/exposed
Bug #2002803 reported by
Adrien Nader
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| datefudge (Debian) |
Fix Released
|
Unknown
|
|||
| datefudge (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
There are no functions for 64-bit time_t in datefudge and packages such as coreutils (>=9.1 i.e. lunar) now use such a time_t. On armhf this makes datefudge inoperative for coreutils and probably more and more packages as time goes on.
Reported upstream (i.e. Debian) at https:/
| tags: | added: update-excuse |
| Changed in datefudge (Debian): | |
| status: | Unknown → New |
| Changed in datefudge (Debian): | |
| status: | New → Fix Released |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in datefudge (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package datefudge - 1.26
---------------
datefudge (1.26) unstable; urgency=low
* Fix autpokgtest case introduced recently for #946776 so that it does not
depend on time zone.
-- Robert Luberda <email address hidden> Sun, 14 Jan 2024 11:16:31 +0100