There are new upstream releases (not tagged in GitHub apparently) that result in big warnings when running clamav-unofficial-sigs 6.1.1: *********************************************************************************** ALERT: New version : v6.3.0 @ https://github.com/extremeshok/clamav-unofficial-sigs *********************************************************************************** *************************************************************************************** ALERT: New config version : v81 @ https://github.com/extremeshok/clamav-unofficial-sigs *************************************************************************************** The port should be updated to the latest release.
Apparently a new version was finally tagged in GitHub upstream (https://github.com/extremeshok/clamav-unofficial-sigs/releases/tag/7.0.1).
Created attachment 211062 [details] Proposed patch to update port to upstream 7.0.1 I've adapted the previous patch to the new upstream files. Some parts have already been incorporated upstream, so there's less to patch.
Created attachment 211063 [details] Fixed patch to update to 7.0.1 The previous diff was missing the patch for the clamav-unofficial-sigs.sh file itself.
The patch for files/patch-clamav-unofficial-sigs.sh does not apply cleanly.
(In reply to Matthias Fechner from comment #4) Can you tell me which parts? I can't reproduce the issue using "make clean && make" from my ports tree.
(In reply to Peter Putzer from comment #5) Sure: wget "https://bz-attachments.freebsd.org/attachment.cgi?id=211063&action=diff&format=raw&headers=1" patch -sp1 < attachment.cgi\?id=211063\&action=diff\&format=raw\&headers=1 1 out of 4 hunks failed--saving rejects to files/patch-clamav-unofficial-sigs.sh.rej
(In reply to Matthias Fechner from comment #6) Ah, so the diff does not apply cleanly to ports? OK, I'll have to get clean version, apparently my saved copy for diffing was compromised already. Also, I've noticed that the upstream script uses the GNU parameter "--wildcards", I'm not sure that there's an equivalent for our version of tar.
(In reply to Peter Putzer from comment #7) I think the BSD's tar(1) does not provide --wildcard option. But you can try ``gtar'' instead :) Because of old version of clamav-unofficial-sigs I temporarily redirected cron job output to /dev/null, all my mail servers were killing my mailbox about new version from cron user ;)
(In reply to Peter Putzer from comment #7) If it help you, just tar the directory and send it be email to me. There is really now need to upload here an updated patch.
(In reply to Matthias Fechner from comment #9) Thanks, I'll do so when I've fixed the issue with the --wildcards flag.
(In reply to Matthias Fechner from comment #9) OK, that was easier than expected. I've sent you the archive.
(In reply to Peter Putzer from comment #11) Thanks a lot Peter, I just did a testbuild, but it fails, here the testbuild log: https://pkg.fechner.net/data/121amd64-gitlab/2020-02-04_20h30m20s/logs/errors/clamav-unofficial-sigs-7.0.1.log The error message is: ===> Building for clamav-unofficial-sigs-7.0.1 (cd /wrkdirs/usr/ports/security/clamav-unofficial-sigs/work/clamav-unofficial-sigs-7.0.1 && /usr/local/bin/bash ./clamav-unofficial-sigs.sh -c manpage.conf --install-man) ======================================================================== ERROR: /usr/local/etc/clamav-unofficial-sigs/master.conf is not readable ======================================================================== *** Error code 1 It seems that they changed the logic how the installation works.
Created attachment 211355 [details] Update to 7.0.1 I corrected the patch a little bit, could you please review the attached patch if that looks ok to you? Testbuild is now fine: https://pkg.fechner.net/build.html?mastername=121amd64-gitlab&build=2020-02-04_20h51m21s
Created attachment 211485 [details] Fixed patch for 7.0.1 update Former maintainer of the port here. I've attached fixed version of the latest proposed update patch, so that configuration files are defined properly at script start. I don't use this script anymore, so I did not have time to do detailed functionality tests, nor build test using poudriere. So, YMMV. :-)
Created attachment 211502 [details] Patch with earlier detection custom config Thanks. I've attached another proposal that moves the detection of custom configurations to an earlier stage which would be the right thing IMHO. (I'll also propose this change upstream.)
Created attachment 211505 [details] Patch with earlier detection custom config The previous patch forgot to update pkg-plist (master.conf and os.conf are installed directly instead of as samples, because all user configuration should go into user.conf only.
I agree that detection of custom configuration should happen sooner. However, patching it by port touches a lot of code, which may complicate future updates in case this does not get changed upstream (i.e. patch may not apply cleanly, requiring further manual intervention on each port update). If you report this upstream and it gets accepted, personally I would simply wait for the next release and use a simpler patch in the meantime. I also took just a brief look at your patch and noticed that you hardcoded config_dir to "/usr/local/etc/clamav-unofficial-sigs", while it should respect %%PREFIX%%. Regarding plist changes, I don't have any preferences here and don't know if the changes to how configuration files are treated are really needed so late in the game, but shouldn't a change to configuration files also be mentioned in the ports/UPDATING file?
Dear Peter, Dear Marco, thanks a lot for your proposals. I will change the maintainer to Peter, so you can easier provide in future changes to this port. But I agree with Marco here, we should not modify to much and should better try to get these modification applied upstream. @Peter, I will not apply this modification now, because it will overwrite modification users could have done in the config files they are currently existing. We should warn them using an UPDATING entry before we change the logic for config files. I will testbuild now a changeset and if the builds fine, will commit it, you can then later fine tune the port to your wishes ok?
A commit references this bug: Author: mfechner Date: Sun Feb 9 19:15:02 UTC 2020 New revision: 525669 URL: https://svnweb.freebsd.org/changeset/ports/525669 Log: Update to 7.0.1. They next version will change the way config files can be used to configure this package. Users should use user.conf to do custom configuration. Changed maintainer. PR: 243556 Submitted by: sf@maxempire.com Reported by: freebsd@mnd.sc Changes: head/security/clamav-unofficial-sigs/Makefile head/security/clamav-unofficial-sigs/distinfo head/security/clamav-unofficial-sigs/files/patch-clamav-unofficial-sigs.sh head/security/clamav-unofficial-sigs/files/patch-config_master.conf head/security/clamav-unofficial-sigs/files/patch-config_user.conf
Committed, thanks a lot!
I got a build error: ============================= =======================<phase: configure >============================ ===> Configuring for clamav-unofficial-sigs-7.0.1 =========================================================================== =======================<phase: build >============================ ===> Building for clamav-unofficial-sigs-7.0.1 (cd /wrkdirs/usr/ports/security/clamav-unofficial-sigs/work/clamav-unofficial-sigs-7.0.1 && /usr/local/bin/bash ./clamav-unofficial-sigs.sh -c manpage.conf --install-man) ====================================================================== ERROR: both dig and host commands are missing, One of them is required ====================================================================== *** Error code 1 Stop. make: stopped in /usr/ports/security/clamav-unofficial-sigs Adding host:dns/bind-tools to build deps made it better.
Dependence on bind-tools should not be required, the script will work fine with ldns based host command replacement that's part of the base FreeBSD system (from version 10.0 onwards). You should have /usr/bin/host as part of the FreeBSD base system. Check your build system.
I don't build ldns, disabled it in src.conf. (Use BIND and Unbound from ports, LDNS does not cut it here.) I don't think it's far fetched to assume that I am not the only one. Perhaps a conditional DEPEND would be, as our saying goes, the church in the middle of the village.
You should have mentioned that you explicitly don't build ldns from base. At first, I thought that I made some mistake in my patch for update to the 7.0.1 version. You should open a separate bug report, since you would have gotten the same error even with the previous version of the port.
Sorry, I had all but forgotten about it, and did not realise it mattered anyway. I removed WITHOUT_LDNS from src.conf and rebuilt all my worlds and updated all the poudriere jails. Wish I could go back and delete my comments. :-)