Repro for the case with:
# install trusty
$ apt install clamav-daemon
upgrade to Xenial repo
$ apt update && apt upgrade
Issues seen on:
clamav-base 0.98.7+dfsg-0ubuntu0.14.04.1 -> clamav-daemon:0.98.7+dfsg-0ubuntu0.15.04.1
clamav-base 0.99.2+addedllvm-0ubuntu0.14.04.1 -> clamav-daemon 0.99.2+dfsg-0ubuntu0.16.04.1
Even in current 0.99.2+addedllvm-0ubuntu0.14.04.2 the file that shown up in all of those is still in clamav-base.
The problem here is that that the trusty version was bumped above those released with 16.04 and therefore the old breaks/replaces isn't correctly applying anymore.
Unless this is bumped that way again (should not I hope) we can rely on being before "0.99.2+dfsg-0ubuntu0.16.04.1" - since those both are bumped by SRUs only on the last level.
This will make is break/conflict with the version Xenial provided on release, but
1. the later 16.04.2+ releases had the new already
2. it isn't breaking anyone, but fixing the upgrade issue for others
Later releases are on 0.99.2+dfsg-6... and 0.99.3... so all safe.
That means we need to change the
<< 0.99+dfsg-1ubuntu1
to
<< 0.99.2+dfsg-0ubuntu0.16.04.1~
I have a proposal to implement those changed deps, soon up for review ...
Repro for the case with:
# install trusty
$ apt install clamav-daemon
upgrade to Xenial repo
$ apt update && apt upgrade
Issues seen on: dfsg-0ubuntu0. 14.04.1 -> clamav- daemon: 0.98.7+ dfsg-0ubuntu0. 15.04.1 addedllvm- 0ubuntu0. 14.04.1 -> clamav-daemon 0.99.2+ dfsg-0ubuntu0. 16.04.1
clamav-base 0.98.7+
clamav-base 0.99.2+
Even in current 0.99.2+ addedllvm- 0ubuntu0. 14.04.2 the file that shown up in all of those is still in clamav-base.
The problem here is that that the trusty version was bumped above those released with 16.04 and therefore the old breaks/replaces isn't correctly applying anymore.
Unless this is bumped that way again (should not I hope) we can rely on being before "0.99.2+ dfsg-0ubuntu0. 16.04.1" - since those both are bumped by SRUs only on the last level.
This will make is break/conflict with the version Xenial provided on release, but
1. the later 16.04.2+ releases had the new already
2. it isn't breaking anyone, but fixing the upgrade issue for others
Later releases are on 0.99.2+dfsg-6... and 0.99.3... so all safe. dfsg-0ubuntu0. 16.04.1~
That means we need to change the
<< 0.99+dfsg-1ubuntu1
to
<< 0.99.2+
I have a proposal to implement those changed deps, soon up for review ...