Your message dated Fri, 17 Jul 2015 14:05:42 -0700
with message-id <[email protected]>
and subject line resolving; not a bug
has caused the Debian Bug report #792544,
regarding ping6: error while loading shared libraries: libnettle.so.4
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.)


-- 
792544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792544
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: iputils-ping
Version: 3:20121221-5+b2
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Maintainer,

   When trying to verify ipv6 connectivity, I encounter the following
   error trying to start ping6:

   $ ping6 google.com
   ping6: error while loading shared libraries: libnettle.so.4: cannot
   open shared object file: No such file or directory


- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages iputils-ping depends on:
ii  libc6                2.19-18
ii  libcap2              1:2.24-9
ii  libgnutls-openssl27  3.3.15-7

Versions of packages iputils-ping recommends:
ii  libcap2-bin  1:2.24-9

iputils-ping suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iF4EAREIAAYFAlWnNfUACgkQa46zoGXPuqkLJwD+Psjxarsife274SlV1dO+24dk
ac47V/Kcx8H3KL3iEc4A/j/SiOPytNOrAJNY9ohnvXCswidBL1j0dSbYi0f/3FzV
=IeQ9
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
resolving. problem was caused by local state on the machine.

--- End Message ---

Reply via email to