>> "RC" == Randolph Chung <[EMAIL PROTECTED]> writes:
RC> what's the easiest way to write a manpage if i don't want to learn
RC> troff? :)
You could use a .pod file (this is the perl documentation format),
which you can convert into a man page.
pod2man --section=1 --release="`date +'%d
> "Randolph" == Randolph Chung <[EMAIL PROTECTED]> writes:
Randolph> if a package uses a .xpm file, is there something i can
Randolph> do so that lintian doesn't complain about it not being
Randolph> an executable file? do i list it as a conffile?
chmod -x xgdip.xpm
Randolph>
if a package uses a .xpm file, is there something i can do so that lintian
doesn't complain about it not being an executable file? do i list it as a
conffile?
i.e.
tausq[11:56] debian% lintian xgdipc*changes
W: xgdipc: executable-not-elf-or-script usr/share/xgdipc/xgdip.xpm
even though this is a
> "Thomas" == Thomas Schoepf <[EMAIL PROTECTED]> writes:
Thomas> A few days ago my application went through, now I am an
Thomas> official maintainer.
Congratulation and welcome onboard.
Thomas> The new package is ready, waiting for being uploaded.
Thomas> But in the mail I r
A few days ago my application went through, now I am an official
maintainer.
The new package is ready, waiting for being uploaded.
But in the mail I received as an answer to my application, it says, I have
to wait until my public key is put into the Debian keyring.
Does that mean I have to regul
> Question for dpkg gurus:
>
> It is technically possible to make package A to conflict with releases of
> B earlier than "p" and also with all releases of B between "r" and "s"
> but not with release "q" of B (where p < q < r < s)?
>
> Thanks.
Could you not simply say that your package conflict
7 matches
Mail list logo
