Thanks for explaining. I am using an internally developed, Python-based
backup system. It makes backups from Btrfs snapshots and regularly
verifies the integrity of the entire restore process. The verification
shows discrepancies such as the one above.
As most backup systems rely on mtime to
so the mtime is set to the one mentioned inside the changelog, "Fri, 19
Oct 2018 11:20:34 -0700" and that's what's included in the package, and
by Debian Policy, one should maintain the timestamps as much as
possible.
at the moment we do not provide any guarantees that files in later
series, have
Update affected package
** Package changed: man-db (Ubuntu) => secureboot-db (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816045
Title:
secureboot-db: release upgrade from 16.04 to