dh_gstscancodecs.1.gz is plain text file

[arky]

The dh_gstscancodes is plain text file. Thus whatis parse fails with following error
mandb: warning: /usr/share/man/man1/dh_gstscancodecs.1.gz: whatis parse for dh_gstscancodecs(1) failed

ProblemType: Bug
Architecture: i386
Date: Thu Aug 13 16:27:27 2009
DistroRelease: Ubuntu 9.10
Package: libgstreamer0.10-dev 0.10.24-1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SourcePackage: gstreamer0.10
Uname: Linux 2.6.31-5-generic i686

[Sebastien Bacher (seb128)]

not confirming the issue there

$ file /usr/share/man/man1/dh_gstscancodecs.1.gz
/usr/share/man/man1/dh_gstscancodecs.1.gz: gzip compressed data, from Unix, max compression

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

[arky (arky)]

$ sudo mandb -c

<snip>
mandb: warning: /usr/share/man/man1/dh_gstscancodecs.1.gz: whatis parse for dh_gstscancodecs(1) failed

The reason for whatis parse failure is that it expects troff file.

$ gunzip -cd /usr/share/man/man1/dh_gstscancodecs.1.gz | head
DH_GSTSCANCODECS(1) User Contributed Perl Documentation DH_GSTSCANCODECS(1)

NAME
       dh_gstscancodecs - enumerate and classify gstreamer codecs

SYNOPSIS
         dh_gstscancodecs [debhelper options]

$ gunzip -cd /usr/share/man/man1/less.1.gz | head
.TH LESS 1 "Version 429: 11 Apr 2009"
.SH NAME
less \- opposite of more
.SH SYNOPSIS
.B "less \-?"
.br
.B "less \-\-help"
.br
.B "less \-V"
.br

[Sebastien Bacher (seb128)]

The bug should be sent to debian since the package comes from there

[Sebastien Bacher (seb128)]

The debian maintainer is subscribed there too

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of GStreamer is available in both Lucid and Maverick and we are wondering if this is still reproducible in any of those versions, May you please test and give us of feedback about it? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.