Stale DNF metadata after system clock rollback
Stale DNF metadata after system clock rollback The goal is to understand how DNF decides whether its cached repository metadata remains valid when the system clock is set backward, potentially bypassing the metadata_expire timer. Constraints include differences in cache layout and expiration logic between DNF releases prior to version 4.0 and later versions,