Your message dated Mon, 14 Jan 2008 11:12:22 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#243754: man-db: repeated output from apropos
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: man-db
Version: 2.3.20-18.woody.4
Severity: important

Since an "apropos blah" often finds many things related to "blah",
duplication of that information makes it even more difficult to 
find the relevant information.  And since the re-configuration of
/etc/manpath.config is far from straight forward, this is a non-
trivial problem for a user to solve.

My choice of "important" may be questionable, but I think it's
correct.  The user is asking for information when s/he invokes this
command and is instead confronted with a redundant mass of data.


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux infidel 2.4.18-1-686 #1 Sun Feb 1 03:55:30 MST 2004 i686
Locale: LANG=en_CA, LC_CTYPE=en_CA

Versions of packages man-db depends on:
ii  bsdmainutils           5.20020211-4.99   More utilities from FreeBSD.
ii  debconf                1.2.23woody1      Debian configuration management sy
ii  dpkg                   1.9.21            Package maintenance system for Deb
ii  groff                  1.17.2-15.woody.1 GNU troff text-formatting system
ii  groff-base             1.17.2-15.woody.1 GNU troff text-formatting system (
ii  libc6                  2.2.5-11.5        GNU C Library: Shared libraries an
ii  libdb2                 2:2.7.7.0-7       The Berkeley database routines (ru



--- End Message ---
--- Begin Message ---
Source: man-db
Source-Version: 2.5.0-1

On Wed, Apr 14, 2004 at 11:24:59PM +0100, Colin Watson wrote:
> On Wed, Apr 14, 2004 at 04:16:58PM -0600, s. keeling wrote:
> > Incoming from Colin Watson:
> > > Hm. That's most odd. Do you have /usr/man as a symlink to /usr/share/man
> > 
> > lrwxrwxrwx    1 root     root   9 Nov 29 23:28 /usr/man -> share/man/
> > 
> > Nice call Colin.
> 
> I'll downgrade this as I don't think this is a default configuration
> (?), and at least it's a configuration which shouldn't be necessary. If
> something breaks without /usr/man, that too is a bug.
> 
> I'll see what I can do; it may be an easy fix.

In the end I fixed this without realising it, in the process of fixing
#259338.

man-db (2.5.0-1) unstable; urgency=low

  * New upstream release.
    [...]
    - Add output keys to a hashtable, and skip any that have already been
      seen (closes: #259338).
  [...]

 -- Colin Watson <[EMAIL PROTECTED]>  Sun, 07 Oct 2007 20:38:25 +0100

Cheers,

-- 
Colin Watson                                       [EMAIL PROTECTED]


--- End Message ---

Reply via email to