Re: Bug#942172: clamav-daemon: After upgrade, clamd cannon create /var/run/clamav/clamd.ctl and stop.
I could only test from 0.100.0+dfsg-0+deb8u1 as I couldn't find
0.100.3+dfsg-0+deb8u1 anywhere in the archives and I'm out of servers
running clamav-daemon 0.100.3+dfsg-0+deb8u1; but as /run/clamav/ is root
owned in 0.100.0+dfsg-0+deb8u1 and clamav-daemon 0.101.4+dfsg-0+deb8u2
got started without a problem after the upgrade I'd say it's OK.
On 13/10/19 10:32, Filipe Fonseca wrote:
I can test it but probably only in half a day time or so. I'll get back
to you then. Many thanks.
On October 13, 2019 09:33:17 Hugo Lefeuvre <email@example.com> wrote:
I did strike this in three boxes. Straight upgrade but opted not to
config when asked. Don't know if it matters. However I did not find any
reference to /etc/systemd/system/clamav-daemon.service.d/extend.conf
package scripts as in stretch.
The chown did make the difference. And the extend.conf prior to the
on further two boxes got the upgrade working, AFAICT.
thanks for your answer.
After further investigations, I have found a probable cause for this
mistakenly backported from the stretch upload.
This should not have been backported, because the jessie package is still
providing the systemd socket, which was removed from the stretch
0.99.2+dfsg-3 because of #824042.
I did not backport this removal because I considered it too intrusive
security upload. Looking back, this was maybe a mistake because it
increased the complexity of the backport.
I have prepared a regression update addressing this issue. It would be a
true benefit for the quality of this upload if somebody could give it
before I go on with uploading. You can find (UNRELEASED) amd64 builds,
signed by myself on my Debian webpage:
Hugo Lefeuvre (hle) | www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C