[Bug 259948] security/vuls port does not see default config file on /usr/local/etc/vuls/config.toml
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259948] security/vuls port does not see default config file on /usr/local/etc/vuls/config.toml"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259948] security/vuls port does not see default config file on /usr/local/etc/vuls/config.toml"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259948] security/vuls port does not see default config file on /usr/local/etc/vuls/config.toml"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259948] security/vuls port does not see default config file on /usr/local/etc/vuls/config.toml"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259948] security/vuls port does not see default config file on /usr/local/etc/vuls/config.toml"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 259948] security/vuls port does not see default config file on /usr/local/etc/vuls/config.toml"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 20 Nov 2021 14:27:44 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259948 Bug ID: 259948 Summary: security/vuls port does not see default config file on /usr/local/etc/vuls/config.toml Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: ulassayginim@gmail.com CC: iscandr@gmail.com CC: iscandr@gmail.com Flags: maintainer-feedback?(iscandr@gmail.com) Hi, I installed Vuls port without problem. but to run vuls scan, it does not see default config file on /usr/local/etc/vuls/config.toml when i want to run command: vuls configtest it give error below ERROR [localhost] Error loading %%ETCDIR%%/config.toml If you update Vuls and get this error, there may be incompatible changes in config.toml Please check config.toml template : https://vuls.io/docs/en/usage-settings.html open %%ETCDIR%%/config.toml: no such file or directory In addition this, config.toml template url is broken. they need to update this too. -- You are receiving this mail because: You are the assignee for the bug.