Package: opendkim Version: 2.11.0~alpha-9 Severity: important After upgrading opendkim to the Stretch version from Jessie I get the following error about liblua5.1.so.0 when running it. To solve the error I need to upgrade liblua5.1-0 to the Stretch version, so a versioned dependency is needed.
In the normal course of operation people won't run a mixture of Jessie and Stretch packages. But this bug might cause problems when running backports and also causes problems when trying to track down other upgrade related problems. As an aside one of my systems had OpenDKIM working well when running Jessie but fails inexplicably when running Stretch. I'm testing upgrading various packages to try and discover the cause of that bug. This problem will affect others who try the same test upgrades. # /usr/sbin/opendkim: /usr/lib/x86_64-linux-gnu/liblua5.1.so.0: no version information available (required by /usr/sbin/opendkim) opendkim: /etc/opendkim.conf: /etc/dkimkeys is writeable and owned by uid 105 which is not the executing uid (0) # apt-get install liblua5.1-0 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: liblua5.1-0 1 upgraded, 0 newly installed, 0 to remove and 206 not upgraded. 1 not fully installed or removed. Need to get 111 kB of archives. After this operation, 10.2 kB disk space will be freed. Get:1 http://mirror.internode.on.net/pub/debian/ stretch/main liblua5.1-0 amd64 5.1.5-8.1+b2 [111 kB] Fetched 111 kB in 0s (295 kB/s) (Reading database ... 16370 files and directories currently installed.) Preparing to unpack .../liblua5.1-0_5.1.5-8.1+b2_amd64.deb ... Unpacking liblua5.1-0:amd64 (5.1.5-8.1+b2) over (5.1.5-7.1) ... Processing triggers for libc-bin (2.19-18+deb8u7) ... Setting up liblua5.1-0:amd64 (5.1.5-8.1+b2) ... Setting up opendkim (2.11.0~alpha-9) ... Job for opendkim.service failed. See 'systemctl status opendkim.service' and 'journalctl -xn' for details. invoke-rc.d: initscript opendkim, action "start" failed. dpkg: error processing package opendkim (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.19-18+deb8u7) ... Errors were encountered while processing: opendkim E: Sub-process /usr/bin/dpkg returned an error code (1) # /usr/sbin/opendkim opendkim: /etc/opendkim.conf: /etc/dkimkeys is writeable and owned by uid 105 which is not the executing uid (0) -- System Information: Debian Release: 8.7 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages opendkim depends on: ii adduser 3.113+nmu3 ii dns-root-data 2015052300+h+1 ii init-system-helpers 1.22 ii libbsd0 0.7.0-2 ii libc6 2.24-9 ii libdb5.3 5.3.28-9 ii libldap-2.4-2 2.4.40+dfsg-1+deb8u2 ii liblua5.1-0 5.1.5-8.1+b2 ii libmemcached11 1.0.18-4 ii libmemcachedutil2 1.0.18-4 ii libmilter1.0.1 8.14.4-8+deb8u1 ii libopendbx1 1.4.6-8 ii libopendkim11 2.11.0~alpha-9 ii librbl1 2.9.2-2+deb8u1 ii libssl1.1 1.1.0e-1 ii libunbound2 1.4.22-3+deb8u2 ii libvbr2 2.9.2-2+deb8u1 ii lsb-base 4.1+Debian13+nmu1 opendkim recommends no packages. Versions of packages opendkim suggests: ii opendkim-tools 2.9.2-2+deb8u1 pn unbound <none> -- Configuration Files: /etc/default/opendkim [Errno 2] No such file or directory: '/etc/default/opendkim' /etc/opendkim.conf changed: Syslog yes UMask 007 Domain test.coker.com.au KeyFile /etc/dkimkeys/2017.private Selector 2017 OversignHeaders From TrustAnchorFile /usr/share/dns/root.key -- no debconf information
