Unattended-upgrades failed to install exim4-daemon-heavy 4.89-2+deb9u4

[Andreas Metzler]

On 2019-06-06 Phil Endecott <phil_ltdnf_endecott at chezphil.org> wrote:
> Dear Debian Exim people,

> I have a system running exim4-daemon-heavy on Stretch 
> with unattended-upgrades.  This morning I checked to see 
> if the security upgrade to 4.89-2+deb9u4 had been 
> installed and I found this:

> $ dpkg -l '*exim*'
> (edited output)
> ii  exim4-base             4.89-2+deb9u4    amd64
> ii  exim4-config           4.89-2+deb9u4    all
> ii  exim4-daemon-heavy     4.89-2+deb9u3    amd64

> Note the daemon-heavy package has not been upgraded.

[...]
> So unattended-upgrades.log lists exim4-daemon-heavy as "will be upgraded", 
> and also reports "All upgrades installed", but unattended-upgrades-dpkg.log 
> doesn't mention it at all.

> It did install when I tried manually:

> # apt-get install exim4-daemon-heavy
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> The following additional packages will be installed:
>   libmariadbclient18
[...]
> Note that that has also installed a new libmariadbclient18.  Is 
> that what caused the problem for unattended-upgrades?
[...]

Hello Phil,

I am no expert on unattended-upgrades, 
unattended-upgrades at packages.debian.org might know better. However what
I am actually wondering about is why it did not automatically upgrade
libmariadbclient18 before? Did you limit unattended-upgrades to
security, excluding main?

> Is it OK 
> for this security update to require a new version of a library?

Yes. libmariadbclient18 is part of the current Debian stable release, it
was upgraded in the latest point release, 9.9.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'