Your message dated Mon, 31 Mar 2008 19:47:23 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#473525: retracted,
has caused the Debian Bug report #473525,
regarding libgnutls
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.)
--
473525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473525
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Subject: libgnutls26: symbol lookup error in libgnutls.so.26
Package: libgnutls26
Version: 2.2.2-1
Severity: normal
*** Please type your report below this line ***
I found to indepent errors all pointing to:
/usr/lib/libgnutls.so.26: undefined symbol:
cnutls_srp_1024_group_generator, version GNUTLS_1_4
^
Maybe it should read gnutls_srp_1024_group_generator?
Bernhard
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages libgnutls26 depends on:
ii libc6 2.7-10 GNU C Library: Shared
libraries
ii libgcrypt11 1.4.0-3 LGPL Crypto library -
runtime libr
ii libgpg-error0 1.4-2 library for common error
values an
ii libopencdk10 0.6.6-1 Open Crypto Development Kit
(OpenC
ii libtasn1-3 1.3-1 Manage ASN.1 structures
(runtime)
ii zlib1g 1:1.2.3.3.dfsg-11 compression library -
runtime
libgnutls26 recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On 2008-03-31 "Dr. Bernhard Kleine" <[EMAIL PROTECTED]> wrote:
> I am sorry for the too fast submission. Re-installation of libgnutls-2.6
> solved the problem!
Thanks for letting us know, marking as fixed.
cu andreas
--- End Message ---
