Merge ~ahasenack/ubuntu/+source/clamav:bionic-clamav-merge-0.99.3beta2-2u1 into ~usd-import-team/ubuntu/+source/clamav:debian/sid
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Merge reported by: | ChristianEhrhardt | ||||
| Merged at revision: | bba0cd64e5efeb7ab09ac22fb82a6c71c71d88e8 | ||||
| Proposed branch: | ~ahasenack/ubuntu/+source/clamav:bionic-clamav-merge-0.99.3beta2-2u1 | ||||
| Merge into: | ~usd-import-team/ubuntu/+source/clamav:debian/sid | ||||
| Diff against target: |
178 lines (+117/-3) 5 files modified
debian/changelog (+59/-0) debian/control (+3/-2) debian/patches/fix_newer_zlib.patch (+53/-0) debian/patches/series (+1/-0) debian/rules (+1/-1) |
||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| ChristianEhrhardt | 2017-11-22 | Approve on 2017-11-23 | |
|
Review via email:
|
|||
Description of the Change
Merge from debian's 0.99.3~
Dropped security patches (already applied) and updated the DEP3 header of debian/
I tested in a bionic container running clam[d]scan in all files in /usr/share/
There is a small issue that is coming from debian and that we have been carrying already in the extend.conf systemd extra file we create in postinst:
# cat /etc/systemd/
[Service]
ExecStartPre=
ExecStartPre=
That mkdir may fail if the directory already exists, that's why that command is prefixed with "-". I think a cleaner approach would have been to also add -p to mkdir. Then we wouldn't see that FAILURE bit in one of the ExecStartPre lines:
root@bionic-
root@bionic-
● clamav-
Loaded: loaded (/lib/systemd/
Drop-In: /etc/systemd/
Active: active (running) since Wed 2017-11-22 21:53:20 UTC; 3s ago
Docs: man:clamd(8)
http://
Process: 21515 ExecStartPre=
Process: 21514 ExecStartPre=
Main PID: 21516 (clamd)
Tasks: 1 (limit: 4915)
CGroup: /system.
└─21516 /usr/sbin/clamd --foreground=true
Nov 22 21:53:20 bionic-clamav-test systemd[1]: Starting Clam AntiVirus userspace daemon...
Nov 22 21:53:20 bionic-clamav-test systemd[1]: Started Clam AntiVirus userspace daemon.
- f301d06... by Andreas Hasenack on 2017-11-22
- 5281f64... by Andreas Hasenack on 2017-11-22
- bba0cd6... by Andreas Hasenack on 2017-11-22
| ChristianEhrhardt (paelzer) wrote : | # |
| ChristianEhrhardt (paelzer) wrote : | # |
Arrr well all my tasks suck atm - damn you bugs :-)
So lets unblock you at least.
General linting via git ubuntu lint - ok
Building .changes - ok
dput linter - only stuff you didn't cause (in Debian and nto too bad)
Test from ppa: https:/
Build cross arches - ok
Carried changes: ok - thanks for the header update
- the llvm one is a bit odd afaik upstream only goes to 3.6, but for dependencies we want 3.9
I had related issues 1717574, but I think it is more for dependencies than for testcases
Except you have better info that points you to testcases?
Dropped changes: ok - all in upstream already
Test - TBD
| ChristianEhrhardt (paelzer) wrote : | # |
Build cross arch (I had formerly built the wrong changes file): Ok
Test: unsure
Note: ppa at https:/
Out of some older bugs I new that some (black and very dark) magic happens when freshclam is complete and clamav needs to compile the bytecode. But even that worked for me on the tests.
It successfully kicked of the service and other things.
Also on the box without network it correctly waited on the condition to have a virus database.
But - I happened to see an error I'm not sure it is new with the new version.
Nov 23 09:22:37 bionic-test freshclam[3708]: bytecode.cvd updated (version: 318, sigs: 75, f-level: 63, builder: raynman)
Nov 23 09:22:41 bionic-test freshclam[3708]: Database updated (6353848 signatures) from db.local.clamav.net (IP: 5.9.38.226)
Nov 23 09:22:41 bionic-test freshclam[3708]: ERROR: NotifyClamd: Can't find or parse configuration file /etc/clamav/
That file existed later and a restart of the service no more complained.
I found the file really does not exist if you only install freshclam.
And on any parsing of new files we get the error (which means it goes on with defaults).
I found the file is installed by clamav-daemon (generated in postinst according to the comment in the file).
It does not seem to break anything - except freshclam running on defaults unless clamav-daemon is installed.
Is that a BUG - I'm not sure, but one should take a look at it.
Steps to reproduce:
$ apt install clamav-freshclam
# wait until the files are downloaded and compiled (some random wait + download time)
$ systemctl status clamav-freshclam
# Instead you can stop the service and just call sudo freshclam (no config)
I checked the pre-merge version and the issue is present there as well.
I found the bug on Arch, RH, Fedora, Ubuntu, Debian e.g. [1]
ALso keep in mind that this config is meant to make freshclam NOTIFY clamd (which is not installed) so all is ok.
Maybe the message shold be no error, but ok for now.
Much noise and time spent, but the merge is good - +1
Waiting for your ping-ack to actually sponsor it into Debian.
[1]: https:/
| Andreas Hasenack (ahasenack) wrote : | # |
Yeah, the daemon can only run once the databases are downloaded. And after they are downloaded by freshclam, it tries to notify the daemon, but fails because it's not running. So there is a bit of hand holding that has to happen for fresh installations. It works, but is not super friendly on a fresh install.
Please go ahead with the sponsoring, thanks!


Hi,
FYI I found this by checking from the Trello card.
Since it is lacking a review request from ~canonical-server it is missing on [1] where I think we would usually look for it.
Putting it onto my TODO List.
I have a few things I need to prep and submit to run tests on then I hope to get to it.
If you get online today and this is not done yet please remind me.
[1]: https:/ /code.launchpad .net/~canonical -server/ +activereviews