Your message dated Sun, 28 Aug 2011 18:49:03 +0100
with message-id <1314553743.9176.30.camel@deadeye>
and subject line Re: libdnet: Only suggest dnet-common
has caused the Debian Bug report #636373,
regarding libdnet: Only suggest dnet-common
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 ow...@bugs.debian.org
immediately.)


-- 
636373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdnet
Version: 2.56
Severity: normal

Installing dnet-common requires user input for an archaic artifact that
most users will not be familiar with. People who wat to use DECnet will
know where to look.

Please reduce dnet-common to a suggestion for libdnet.

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

Kernel: Linux 3.0.0-rc6-no-evgmem+ (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libdnet depends on:
ii  libc6                         2.13-13    Embedded GNU C Library: Shared lib
ii  libgcc1                       1:4.6.1-5  GCC support library
ii  libstdc++6                    4.6.1-5    GNU Standard C++ Library v3

Versions of packages libdnet recommends:
pn  dnet-common                   <none>     (no description available)

libdnet suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 2.56.1+nmu1

I've made this change now.

Ben.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to