Comment 13 for bug 2038987

I believe this is common on release date and it "fixes" it self by freezing release pocket and thus slowly it's timestamps becoming in the past for anybody in early or late timezones, and local timezone clocks, instead of UTC.

To the point where we potentially should employ the snapd strategy - snapd uses timestamps from valid assertion signatures to advance clock to the most recent signature timestamp, because we trust snapd assertions authority.

Similarly, if ubuntu archive release file has time signed in the future, we clearly should be advancing the local system clock forward.