Package: exim4-config Version: 4.92-6 During this upgrade,
$ cat /var/log/apt/history.log Start-Date: 2019-04-18 01:32:49 Upgrade: exim4-base:amd64 (4.92-5, 4.92-6), openssl:amd64 (1.1.1b-1, 1.1.1b-2), unicode-data:amd64 (12.0.0-1, 12.1.0~pre1-1), exim4-daemon-light:amd64 (4.92-5, 4.92-6), rsyslog:amd64 (8.1903.0-4, 8.1904.0-1), exim4-config:amd64 (4.92-5, 4.92-6), exim4:amd64 (4.92-5, 4.92-6), libssl1.1:amd64 (1.1.1b-1, 1.1.1b-2), libfaad2:amd64 (2.8.8-1, 2.8.8-2) End-Date: 2019-04-18 01:32:56 some process did a touch(1) or otherwise changing $ stat /etc/exim4/update-exim4.conf.conf File: /etc/exim4/update-exim4.conf.conf Size: 1154 Blocks: 8 IO Block: 4096 regular file Device: 803h/2051d Inode: 524387 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Modify: 2019-04-18 01:32:53.473019451 +0800 <------------THIS Change: 2019-04-18 01:32:53.477019558 +0800 causing alarm bells to ring on my homebrew security system. Please don't "touch" files for no good reason. Thanks. P.S., In fact, looking at that second in /var/log/dpkg.log shows: 2019-04-18 01:32:53 status half-configured exim4-config:all 4.92-6 2019-04-18 01:32:53 status installed exim4-config:all 4.92-6 2019-04-18 01:32:53 configure openssl:amd64 1.1.1b-2 <none> 2019-04-18 01:32:53 status unpacked openssl:amd64 1.1.1b-2 2019-04-18 01:32:53 status half-configured openssl:amd64 1.1.1b-2 2019-04-18 01:32:53 status installed openssl:amd64 1.1.1b-2 2019-04-18 01:32:53 configure exim4-base:amd64 4.92-6 <none> 2019-04-18 01:32:53 status unpacked exim4-base:amd64 4.92-6 2019-04-18 01:32:53 status half-configured exim4-base:amd64 4.92-6 (Plus I bet it is a policy violation.)
