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

[Oliver O.]

Public bug reported:

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

** Affects: secureboot-db (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to man-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:
  New

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