openvas-server creates the directory /var/lib/lib/openvas instead of /var/lib/openvas As a side note, can you keyword this stuff for ~ppc? I've compiled all of openvas on my efika with no issues.
This occurs on both my x86 box and on my ppc box, I don't have an amd64 box, but I would presume it would also be the same there.
Paths fixed in 2.0.1-r1, opened a new bug for ppc (ppc-team should do this).
unfortunately this just changes the path but actually breaks functionality. **** /var/lib/lib/openvas/openvas-services could not be found. Install it and try again going back to 2.0.1 restores it.
There are several patches in openvas-server-2.0.1/packaging/ including openvas-server-2.0.1/packaging/fedora/openvas-server-1.0.0-Makefile.diff which seems fixing this problem, we might need something similar too. The bug is not fixed, please re-open.
Yeah, seems I broke more than i fixed - sorry for the long delay, now switching back to old behaviour, weird paths but working.
*** Bug 266578 has been marked as a duplicate of this bug. ***
This bug is still present with openvas-server-2.0.2, I symlinked the folders to match; /var/lib/lib/openvas -> /var/lib/openvas /var/lib/log/openvas -> /var/log/openvas The program functions as it should. Have some issues with certificates, but I reckon that has another cause. Any hope of resolution in the ebuilds?
(In reply to comment #7) > This bug is still present with openvas-server-2.0.2, I symlinked the folders to > match; > > /var/lib/lib/openvas -> /var/lib/openvas > /var/lib/log/openvas -> /var/log/openvas i tried this with ln -s /var/lib/lib/openvas /var/lib/openvas and ln -s /var/lib/log/openvas to /var/log/openvas i have synced the rules but the daemon still won't start how did you get it to work? different link method?
This issue applies to openvas-2.0.3 too. After adding the symbolic links above, the daemon starts.
openvas-server is no longer part of the openvas package and will be removed soon.
