On Tue, Jul 28, 2009 at 10:57 PM, Russ Allbery wrote:
> George Danchev writes:
>
>> There is no easy way for dh_installman to guess that optin.so as found
>> in source directory is actually a manpage content meant for inclusion,
>> so you should take the control yourself and install that files in
ls: manpage-has-errors-from-man
> usr/share/man/man1/andump.1.gz can't open man1/optin.so: No such file
> or directory
I use the gsoelim command from the groff package to resolve all of the
includes, and install the output. I do not install the include files at
all. The makefile fragme
> George Danchev writes:
> > There is no easy way for dh_installman to guess that optin.so as found
> > in source directory is actually a manpage content meant for inclusion,
> > so you should take the control yourself and install that files in place
> > from debian/rules either by copying it or b
George Danchev writes:
> There is no easy way for dh_installman to guess that optin.so as found
> in source directory is actually a manpage content meant for inclusion,
> so you should take the control yourself and install that files in place
> from debian/rules either by copying it or by calling
.1.gz can't open man1/optin.so: No such file
> or directory
> ...
> W: dicom3tools: manpage-has-errors-from-man
> usr/share/man/man1/rawtodc.1.gz can't open man1/genin.so: No such
> file or directory
>
>
> Because the naming convention of those common paramete
Hi there,
I am working on the dicom3tools package. The dicom3tools is writing
the man page using groff '.so' macro (source) (*). Which leads to the
following lintian warning :
W: dicom3tools: manpage-has-errors-from-man
usr/share/man/man1/andump.1.gz can't open man1/optin.so:
6 matches
Mail list logo