Package Details: openvas-scanner 23.13.2-1

Git Clone URL: https://aur.archlinux.org/openvas-scanner.git (read-only, click to copy)
Package Base: openvas-scanner
Description: Vulnerability scanning Daemon
Upstream URL: https://github.com/greenbone/openvas-scanner
Licenses: GPL-2.0-only
Groups: greenbone-vulnerability-manager
Submitter: mfulz
Maintainer: TrialnError
Last Packager: TrialnError
Votes: 0
Popularity: 0.000000
First Submitted: 2021-02-16 22:17 (UTC)
Last Updated: 2024-12-10 18:18 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

TrialnError commented on 2024-09-04 18:25 (UTC)

23.9.0 compiled for me without issues.

TrialnError commented on 2024-09-04 17:42 (UTC)

This is a case of -Werror, rek2. Every warning is treated as an error. Upstream issue.
But they released a new version in the meantime. We will see if the issue is fixed with that.

rek2 commented on 2024-09-03 18:32 (UTC)

I am having this issue :/

-- Found Doxygen: /usr/bin/doxygen (found version "1.12.0") found components: doxygen missing components: dot
-- Configuring done (0.8s)
-- Generating done (0.0s)
-- Build files have been written to: /home/rek2/.cache/paru/clone/openvas-scanner/src/build
make: Entering directory '/home/rek2/.cache/paru/clone/openvas-scanner/src/build'
[  1%] Building C object misc/CMakeFiles/openvas_misc_shared.dir/bpf_share.c.o
<command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
<command-line>: note: this is the location of the previous definition
cc1: all warnings being treated as errors
make[2]: *** [misc/CMakeFiles/openvas_misc_shared.dir/build.make:76: misc/CMakeFiles/openvas_misc_shared.dir/bpf_share.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:229: misc/CMakeFiles/openvas_misc_shared.dir/all] Error 2
make: *** [Makefile:166: all] Error 2
make: Leaving directory '/home/rek2/.cache/paru/clone/openvas-scanner/src/build'
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'openvas-scanner-23.8.5-2': 
error: packages failed to build: openvas-scanner-23.8.5-2

Any ideas?

lmat commented on 2024-07-16 16:34 (UTC)

Yes, I opened https://github.com/greenbone/openvas-scanner/issues/1681

TrialnError commented on 2024-07-16 16:29 (UTC)

Yes, for whatever reason the cmake script cannot get the version of the libgcrypt package.
Odd thing is, the version is available and it doesn't do anything different from the other dep checks:

$ pkg-config libgcrypt-config --version
2.1.1

https://github.com/greenbone/openvas-scanner/blob/1ffc0c8310354aedab481750ec9fbfea42ee4d26/nasl/CMakeLists.txt#L98

Did you open the respective issue on the upstream repo?

lmat commented on 2024-07-16 13:38 (UTC)

I'm trying to install, but having trouble. I installed gvm-libs using makepkg. During make, I saw an error about missing libgcrypt, so I installed that. But, when I makepkg -sri, I get

...
-- Looking for netsnmp...
-- Looking for netsnmp... /usr/lib/libnetsnmp.so
-- Looking for libgcrypt...
-- Looking for libgcrypt... /usr/lib/libgcrypt.so
--   found libgcrypt, version 
CMake Error at nasl/CMakeLists.txt:103 (message):
  libgcrypt 1.6 or greater is required


-- Looking for bison...
-- Found BISON: /usr/bin/bison (found suitable version "3.8.2", minimum required is "2.5")
-- Checking for module 'libbsd'
--   Found libbsd, version 0.12.2
-- Looking for libgcrypt...
-- Looking for libgcrypt... /usr/lib/libgcrypt.so
--   found libgcrypt, version 
CMake Error at src/CMakeLists.txt:38 (message):
  libgcrypt 1.6 or greater is required


-- Looking for pcap...
-- Looking for pcap... /usr/lib/libpcap.so
-- Looking for pcap-config...
-- Looking for pcap-config... /usr/bin/pcap-config
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Found Doxygen: /usr/bin/doxygen (found version "1.11.0") found components: doxygen dot
-- WARNING: pandoc is required to build the HTML user manual.
-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in build().
    Aborting...

Maybe there is a problem with the libgcrypt version in official repositories?

carlosnewmusic commented on 2024-07-08 15:41 (UTC) (edited on 2024-07-08 15:54 (UTC) by carlosnewmusic)

I don't have custom flags, I use makepkg, I use pamac, https://pastebin.com/4BizdnbZ

TrialnError commented on 2024-06-18 22:03 (UTC)

I cannot reproduce this build failure in a clean chroot, carlosnewmusic. 

(...)
==> Creating package "openvas-scanner"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: openvas-scanner 23.4.1-1 (Tue Jun 18 23:54:47 2024)

Do you have any custom CFLAGS/LDFLAGS configured? How are you building the package? makepkg or some aur helper?
As a sidenote: You can use LANG=C before a command to temporarily get the output of a command in english. I got the gist of the error messages when they were localized, but my knowledge is almost non existant. To much time has passend when I dabbled with languages like spanish or similiar to it.

carlosnewmusic commented on 2024-06-18 08:56 (UTC)

Build error https://pastebin.com/xZ1eyHEg

chovy commented on 2024-06-04 18:02 (UTC)

From your posted log snippet I assume there is some AUR helper at work? The issue seems to be, that gvm-libs offers PGP signatures and the key doesn't seem to be in your local gpg keyring. And therefore it didn't build the package.

yes, the key would not import so I tried without it.

« First ‹ Previous 1 2 3 4 5 Next › Last »