Your message dated Fri, 18 Sep 2009 16:24:55 +0200
with message-id <[email protected]>
and subject line Re: [Openvas-distro-deb] Bug#547285: openvas-server does not
start
has caused the Debian Bug report #547285,
regarding openvas-server does not start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
547285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547285
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openvas-server
Version: 2.0.3-2
# /etc/init.d/openvas-server start
Starting OpenVAS daemon: store_init(): called with NULL
[27877]() gpgme_new failed: User defined source 1/Unknown error code
/etc/init.d/openvas-server: rad 77: 27877 Segmenteringsfel
start-stop-daemon --start --exec $DAEMON -- $DAEMONOPTS -D 2>&1
ERROR.
This looks like OpenVAS bug 1079 for which it seems to be a fix.
It would be nice if this one could be incorporated in Debian as
the packet is not working.
OS: 2.6.30-1-amd64
Debian-version: Sid
Torbjörn Wictorin,
Uppsala univ.
--- End Message ---
--- Begin Message ---
reassign 547285 openvas-libnasl
thank you
Version: 2.0.2-2
Hi Torbjorn,
thanks for the bugreport.
On Friday 18 September 2009 11:32:53 [email protected] wrote:
> # /etc/init.d/openvas-server start
>
> Starting OpenVAS daemon: store_init(): called with NULL
> [27877]() gpgme_new failed: User defined source 1/Unknown error code
> /etc/init.d/openvas-server: rad 77: 27877 Segmenteringsfel
> start-stop-daemon --start --exec $DAEMON -- $DAEMONOPTS -D 2>&1
> ERROR.
Yeah ... I uploaded a new openvas-libnasl yesterday.
Changes:
openvas-libnasl (2.0.2-2) unstable; urgency=low
.
* Add README.source
* add 10_fix_gpgme.dpatch to prevent openvasd to secfault when using gpgme
with revent versions
> This looks like OpenVAS bug 1079 for which it seems to be a fix.
> It would be nice if this one could be incorporated in Debian as
> the packet is not working.
Sure ... I acked yesterday the fix and did attach my patch to the upstream
bug.
With kind regards, Jan.
--
Never write mail to <[email protected]>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
