[Bug 1816045] Re: secureboot-db: release upgrade from 16.04 to 18.04 modifies changelog.gz but resets mtime

[Dimitri John Ledkov]

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 higher/same/lower mtime than in previous releases. For
example, a package in xenial may have an SRU to fix a bug, which doesn't
affect and/or has always been fixed in bionic, thus upgrade from xenial
to bionic may see files go back in time w.r.t. mtime.

A backup system that exclusively relies on mtime, or mtime increasing
linearly, will be broken across release-upgrades. After a release-
upgrade a contents/checksum check should be executed to detect changes.

Which backup system are you using?

** Changed in: secureboot-db (Ubuntu)
       Status: New => Won't Fix

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

Title:
  secureboot-db: release upgrade from 16.04 to 18.04 modifies
  changelog.gz but resets mtime

Status in secureboot-db package in Ubuntu:
  Won't Fix

Bug description:
  During a release-upgrade from Ubuntu 16.04 to 18.04, the file
  /usr/share/doc/secureboot-db/changelog.gz is modified, but retains its
  original mtime. This will interfere with incremental backups, which
  will fail to pick up the updated file.

  The file's first line has changed
  from: secureboot-db (1.4~ubuntu0.16.04.1) xenial; urgency=medium
  to:   secureboot-db (1.4~ubuntu0.18.04.1) bionic; urgency=medium

  ... but the file time for both file versions is identical:
  2018-10-19 20:20:34.000000000 +0200 changelog.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/secureboot-db/+bug/1816045/+subscriptions