Package: mayavi
Version: 1.5-4~frx.1
Severity: minor
Hi again!
After backporting mayavi 1.5-4 to sarge, I checked it with lintian and
got some complaints, so I thought I should report them...
Take into account that this is what _sarge's_ version of lintian says,
hence some of the following errors/warnings can be false positives,
because of Policy changes made since sarge release.
An up-to-date version of lintian should be run on mayavi 1.5-4, in
order to get correct results.
Please also note that complaints about bad-version-number should be
entirely ignored, since are introduced by my version number change
(sarge's version of lintian does not accept tildes in version numbers).
OK, after the caveats, here's the output I got:
$ lintian -i -I -v mayavi_1.5-4~frx.1_i386.changes
N: Setting up lab in /tmp/5A84Oeqbi6 ...
N: Processing changes file mayavi_1.5-4~frx.1_i386.changes ...
N: Processing 2 packages...
N: ----
N: Processing source package mayavi (version 1.5-4~frx.1) ...
E: mayavi source: bad-version-number 1.5-4~frx.1
N:
N: The version number fails one of the syntactic requirements of dpkg.
N:
N: Refer to Policy Manual, section 5.6.11 for details.
N:
N: ----
N: Processing binary package mayavi (version 1.5-4~frx.1) ...
I: mayavi: hyphen-used-as-minus-sign usr/share/man/man1/mayavi.1.gz:23
N:
N: Manual page seems to contain a hyphen where a minus sign was intended.
N: '-' chars are interpreted as hyphens (U+2010) by groff, not as minus
N: signs (U+002D). Since options to programs use minus signs (U+002D),
N: this means for example in UTF-8 locales that you cannot cut&paste
N: options, nor search for them easily.
N:
N: '-' must be escaped ('\-') to be interpreted as minus. If you really
N: intend a hyphen, write it as '\(hy' to emphasise that fact. See
N: groff(7) and especially groff_char(7) for details, and also the thread
N: starting with
N: http://lists.debian.org/debian-devel/2003/debian-devel-200303/msg01481
N: .html
N:
N: If you use some tool that converts your documentation to groff format,
N: it might be possible that this tool converts dashes of any kind to
N: groff hyphens, while the safe way of converting dashes is usually to
N: convert them to '\-'.
N:
N: Because this error can occur very often we show only the first 10
N: occurrences for each man page and give the number of suppressed
N: occurrences. If you want to see all warnings, run lintian with the
N: -d/--debug option.
N:
I: mayavi: hyphen-used-as-minus-sign usr/share/man/man1/mayavi.1.gz:28
I: mayavi: hyphen-used-as-minus-sign usr/share/man/man1/mayavi.1.gz:40
I: mayavi: hyphen-used-as-minus-sign usr/share/man/man1/mayavi.1.gz:46
I: mayavi: hyphen-used-as-minus-sign usr/share/man/man1/mayavi.1.gz:52
I: mayavi: hyphen-used-as-minus-sign usr/share/man/man1/mayavi.1.gz:58
I: mayavi: hyphen-used-as-minus-sign usr/share/man/man1/mayavi.1.gz:64
I: mayavi: hyphen-used-as-minus-sign usr/share/man/man1/mayavi.1.gz:70
I: mayavi: hyphen-used-as-minus-sign usr/share/man/man1/mayavi.1.gz:76
I: mayavi: hyphen-used-as-minus-sign usr/share/man/man1/mayavi.1.gz:82
I: mayavi: hyphen-used-as-minus-sign usr/share/man/man1/mayavi.1.gz 2 more
occurrences not shown
W: mayavi: binary-without-manpage vtk_doc
N:
N: Each binary in /usr/bin, /usr/sbin, /bin, /sbin or /usr/games should
N: have a manual page
N:
N: Note, that though the `man' program has the capability to check for
N: several program names in the NAMES section, each of these programs
N: should have its own manual page (a symbolic link to the appropriate
N: manual page is sufficient) because other manual page viewers such as
N: xman or tkman don't support this.
N:
N: Refer to Policy Manual, section 12.1 for details.
N:
W: mayavi: image-file-in-usr-lib
usr/lib/python2.3/site-packages/vtkPipeline/Icons/actor.gif
N:
N: This package installs a pixmap or a bitmap within /usr/lib. According
N: to the Filesystem Hierarchy Standard, architecture-independent files
N: need to be placed within /usr/share instead.
N:
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/camera.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/colormap.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/coord.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/data.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/dir.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/file.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/folder.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/light.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/minusnode.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/openfolder.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/plusnode.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/process.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/python.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/question.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/ren.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/renwin.gif
W: mayavi: image-file-in-usr-lib usr/lib/python2.3/site-packages/vtkPipeline/Ico
ns/tk.gif
E: mayavi: bad-version-number 1.5-4~frx.1
N: Removing /tmp/5A84Oeqbi6 ...
Thanks for the attention!
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.33.3
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages mayavi depends on:
ii libvtk5-dev 5.0.1-4~frx.1 VTK header files for building C++
ii python 2.3.5-2 An interactive high-level object-o
ii python-tk 2.3.5-2 Tkinter - Writing Tk applications
ii python-vtk 5.0.1-4~frx.1 Python bindings for VTK
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
