Re: Bug#942172: clamav-daemon: After upgrade, clamd cannon create /var/run/clamav/clamd.ctl and stop.

2019-10-14 Thread Marco Gaiarin
Mandi! Hugo Lefeuvre
  In chel di` si favelave...

> thanks for your time. I have done some more tests myself and went ahead
> with the upload, I hope everything will be fine now. Sorry for the trouble.

I canconfirm that now the bug is solved.


Thanks!

-- 
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''  http://www.lanostrafamiglia.it/
  Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento (PN)
  marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f +39-0434-842797

Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
  http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000
(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)



Re: Bug#942172: clamav-daemon: After upgrade, clamd cannon create /var/run/clamav/clamd.ctl and stop.

2019-10-14 Thread Filipe Fonseca

Thank you. You're very welcome. Regards,
Filipe

On 14/10/19 08:20, Hugo Lefeuvre wrote:

Hi Filipe, Sebastian,


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.


thanks for your time. I have done some more tests myself and went ahead
with the upload, I hope everything will be fine now. Sorry for the trouble.

If you see anything suspicious, don't hesitate to open a bug report, I will
take a look at it.

regards,
Hugo




--
filipe.fons...@farmingbits.com
+351.914593743



Re: Bug#942172: clamav-daemon: After upgrade, clamd cannon create /var/run/clamav/clamd.ctl and stop.

2019-10-14 Thread Hugo Lefeuvre
Hi Filipe, Sebastian,

> 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.

thanks for your time. I have done some more tests myself and went ahead
with the upload, I hope everything will be fine now. Sorry for the trouble.

If you see anything suspicious, don't hesitate to open a bug report, I will
take a look at it.

regards,
Hugo

-- 
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


signature.asc
Description: PGP signature


Re: Bug#942172: clamav-daemon: After upgrade, clamd cannon create /var/run/clamav/clamd.ctl and stop.

2019-10-13 Thread Filipe Fonseca

Hello,

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.


Many thanks!!!

Regards,
Filipe

On 13/10/19 10:32, Filipe Fonseca wrote:

Hello,

I can test it but probably only in half a day time or so. I'll get back 
to you then. Many thanks.


Regards,
Filipe

On October 13, 2019 09:33:17 Hugo Lefeuvre  wrote:


Hi Filipe,

I did strike this in three boxes. Straight upgrade but opted not to 
touch

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 
in the

package scripts as in stretch.

The chown did make the difference. And the extend.conf prior to the 
upgrade

on further two boxes got the upgrade working, AFAICT.


thanks for your answer.

After further investigations, I have found a probable cause for this 
issue:

debian/patches/clamd_dont_depend_on_clamav_demon_socket.patch was
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 
package in

0.99.2+dfsg-3 because of #824042[0].

I did not backport this removal because I considered it too intrusive 
for a

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 
a try

before I go on with uploading. You can find (UNRELEASED) amd64 builds,
signed by myself on my Debian webpage:

https://people.debian.org/~hle/lts/clamav/

regards,
Hugo

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824042

--
   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


--
filipe.fons...@farmingbits.com
+351.914593743






--
filipe.fons...@farmingbits.com
+351.914593743



Re: Bug#942172: clamav-daemon: After upgrade, clamd cannon create /var/run/clamav/clamd.ctl and stop.

2019-10-13 Thread Filipe Fonseca

Hello,

I can test it but probably only in half a day time or so. I'll get back to 
you then. Many thanks.


Regards,
Filipe

On October 13, 2019 09:33:17 Hugo Lefeuvre  wrote:


Hi Filipe,


I did strike this in three boxes. Straight upgrade but opted not to touch
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 in the
package scripts as in stretch.

The chown did make the difference. And the extend.conf prior to the upgrade
on further two boxes got the upgrade working, AFAICT.


thanks for your answer.

After further investigations, I have found a probable cause for this issue:
debian/patches/clamd_dont_depend_on_clamav_demon_socket.patch was
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 package in
0.99.2+dfsg-3 because of #824042[0].

I did not backport this removal because I considered it too intrusive for a
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 a try
before I go on with uploading. You can find (UNRELEASED) amd64 builds,
signed by myself on my Debian webpage:

https://people.debian.org/~hle/lts/clamav/

regards,
Hugo

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824042

--
   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


--
filipe.fons...@farmingbits.com
+351.914593743