RFS: monkey (updated package)
Dear mentors, I am looking for a sponsor for the new version 0.11.0-1 of my package monkey. It builds these binary packages: monkey - very small and fast open source web server for Linux The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/m/monkey - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/m/monkey/monkey_0.11.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards Thorsten Schmale -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100727082923.ga20...@maggie.schmalenegger.com
Re: RFS: monkey (updated package)
On Tue, 13 Apr 2010, Thorsten Schmale wrote: Dear mentors, I am looking for a sponsor for the new version 0.10.1-1 of my package monkey. It builds these binary packages: monkey - very small and fast open source web server for Linux Did you get this uploaded? If not, where is your original sponsor? (-: If you're willing to work with me to get DebianMaintainer status, then I can review this (but I'm busy until 10 days from today). -- Asheesh. -- You will forget that you ever knew me. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.00.1004230554240.16...@rose.makesad.us
RFS: monkey (updated package)
Dear mentors, I am looking for a sponsor for the new version 0.10.1-1 of my package monkey. It builds these binary packages: monkey - very small and fast open source web server for Linux The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/m/monkey - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/m/monkey/monkey_0.10.1-1.dsc I would be glad if someone uploaded this package for me. Kind regards Thorsten Schmale -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100413073006.ga7...@maggie.schmalenegger.com
RFS: monkey (updated package)
Dear mentors, I am looking for a sponsor for the new version 0.9.2-5 of my package monkey. It builds these binary packages: monkey - fast, efficient, small and easy to configure web server The package appears to be lintian clean. The upload would fix these bugs: 548583 The former version 0.9.2-4 fixes also this bug: 505666, but unfortunately I haven't found a sponsor for that version. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/m/monkey - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/m/monkey/monkey_0.9.2-5.dsc I would be glad if someone uploaded this package for me. Kind regards Thorsten Schmale -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: monkey (updated package)
Il giorno mar, 29/09/2009 alle 14.03 +0200, Thorsten Schmale ha scritto: Dear mentors, I am looking for a sponsor for the new version 0.9.2-5 of my package monkey. I would be glad if someone uploaded this package for me. I'll have a look at it. Marco -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: monkey (updated package)
Dear mentors, I am looking for a sponsor for the new version 0.9.2-4 of my package monkey. It builds these binary packages: monkey - fast, efficient, small and easy to configure web server The package appears to be lintian clean. The upload would fix these bugs: 505666 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/m/monkey - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/m/monkey/ monkey_0.9.2-4.dsc I would be glad if someone uploaded this package for me. Kind regards Thorsten Schmale PGP.sig Description: Signierter Teil der Nachricht
Re: RFS: monkey (updated package)
Hello Thorsten, On Mon, Nov 24, 2008 at 08:51, Thorsten Schmale [EMAIL PROTECTED] wrote: Dear mentors, I am looking for a sponsor for the new version 0.9.2-4 ... The upload would fix these bugs: 505666 While the changelog contains only a line for that bug closure, I see many file changed/added to upstream code, like: $ debdiff monkey_0.9.2-3.dsc monkey_0.9.2-4.dsc | diffstat Makefile | 43 bin/banana| 92 + conf/monkey.conf | 221 ++ conf/monkey.deny | 71 + monkey-0.9.2/debian/changelog |9 + monkey-0.9.2/debian/control |1 monkey-0.9.2/debian/postinst | 12 +- src/Makefile | 34 ++ src/include/info.h|3 9 files changed, 480 insertions(+), 6 deletions(-) May you please clarify what happened? if it's crust, then remove in clean debian/rules target, if not, please use a patch system to change upstream source code. In addition to this, you've changed (adding the last line) the previous entry in debian/changelog, and there's a change in postinst too (I think they should be in -4 not in -3, is it correct?). Regards, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: monkey (updated package)
On Mon, Nov 24, 2008 at 4:51 PM, Thorsten Schmale [EMAIL PROTECTED] wrote: http://mentors.debian.net/debian/pool/main/m/monkey/monkey_0.9.2-4.dsc Firstly, please do not send HTML mail: http://www.debian.org/MailingLists/#codeofconduct You should not modify the changelog entries of versions that have already been uploaded to the archive. This version adds the following files outside the debian/ directory, why? monkey-0.9.2/bin/banana monkey-0.9.2/conf/monkey.conf monkey-0.9.2/conf/monkey.deny monkey-0.9.2/src/include/info.h monkey-0.9.2/src/Makefile monkey-0.9.2/Makefile You should include a Homepage field. Why the blank line at the end of the package description? Please send your manual page, default configuration file and possibly init script upstream if you haven't already. Why do you run ./configure twice in debian/rules? The watch file does not work - gives 403 Forbidden. Perhaps you could educate upstream about using the sf.net file release system so their get the benefit of local mirrors and you can use the magical uscan support for sf.net? You should target experimental during the freeze or contact the release team for getting -3 into testing and pre-approval for -4. Your package has no debtags, please add some: http://debtags.alioth.debian.org/edit.html?pkg=monkey -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Homepages and debtags (was Re: RFS: monkey)
On Mon, 24 Nov 2008 17:55:48 +0900 Paul Wise [EMAIL PROTECTED] wrote: You should include a Homepage field. Your package has no debtags, please add some: http://debtags.alioth.debian.org/edit.html?pkg=monkey Maybe both of these should be default criteria for sponsoring? The first upload of any non-native package should either include the Homepage field or an explanation of why there might be no homepage. Subsequent uploads of any package should ensure that debtags are complete. I've added both as requirements for my own sponsoring, once I get back to normal levels of sponsoring activity. Worth adding these two to the mentors FAQ? http://oldpeople.debian.org/~codehelp/#debtags http://oldpeople.debian.org/~codehelp/#homepage I've also added a bit of extra text to some of the sections, noticeably on communication: All communication by email only, preferably on the debian-mentors mailing list and wherever possible, signed with your GnuPG key. Pestering me on IRC is likely to end with you needing a new sponsor (or at best being ignored). I'm always busy, I have always got lots of stuff that needs doing before your upload, so ask me nicely and I'll look at moving you up the ToDo list. Make sure that your requests for sponsorship on the mentors mailing list contain all necessary information, this includes listings for: Programming Languages, Licence, Version, Authors, Description and Homepage. ITP or RFS content that does not detail the programming language or does not include appropriate Licence information *will* be ignored. If the upload closes a bug that is not an ITP bug, the full title of that bug should be included in the RFS along with the current severity of that bug. (and if any DD can remember how to fix oldpeople sites to show up on people again, let me know - the ordinary fix has not worked) -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpTOnFBq75JR.pgp Description: PGP signature
Re: Homepages and debtags (was Re: RFS: monkey)
On Mon, Nov 24, 2008 at 6:34 PM, Neil Williams [EMAIL PROTECTED] wrote: Maybe both of these should be default criteria for sponsoring? The first upload of any non-native package should either include the Homepage field or an explanation of why there might be no homepage. I don't think this should be a hard requirement. One problem is where to include why there is no homepage. I don't think there is an appropriate place for that information, other than in the RFS itself, or when debexpo gets deployed there could be a field about that. Sponsors could then de-prioritise packages without a Homepage or an explanation of why there is not one. Subsequent uploads of any package should ensure that debtags are complete. I don't think this should be a hard requirement either. On the other hand when debexpo gets deployed and mentors.d.n is more useful for sponsors I'll certainly be de-prioritising such packages. (and if any DD can remember how to fix oldpeople sites to show up on people again, let me know - the ordinary fix has not worked) scp/rsync your public_html from gluck.d.o - yourpc - ravel.d.o. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Homepages and debtags (was Re: RFS: monkey)
On Mon, Nov 24, 2008 at 10:34, Neil Williams [EMAIL PROTECTED] wrote: On Mon, 24 Nov 2008 17:55:48 +0900 Paul Wise [EMAIL PROTECTED] wrote: You should include a Homepage field. Your package has no debtags, please add some: http://debtags.alioth.debian.org/edit.html?pkg=monkey Maybe both of these should be default criteria for sponsoring? The first upload of any non-native package should either include the Homepage field or an explanation of why there might be no homepage. Subsequent uploads of any package should ensure that debtags are complete. While this is nice to have, I don't think add a strong require on this is the right way to go. Debtags are approved by Enrico in a very async way from the upload to mentors or to ftp-master. What we can do is encourage the debtags user (and I'm culprit for my packages missing them ;) ), but not reject a sponsorship for the miss of debtags, IMHO. Cheers, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Homepages and debtags (was Re: RFS: monkey)
On Mon, 24 Nov 2008 18:52:46 +0900 Paul Wise [EMAIL PROTECTED] wrote: On Mon, Nov 24, 2008 at 6:34 PM, Neil Williams [EMAIL PROTECTED] wrote: Maybe both of these should be default criteria for sponsoring? The first upload of any non-native package should either include the Homepage field or an explanation of why there might be no homepage. I don't think this should be a hard requirement. One problem is where to include why there is no homepage. I don't think there is an appropriate place for that information, other than in the RFS itself, or when debexpo gets deployed there could be a field about that. Sponsors could then de-prioritise packages without a Homepage or an explanation of why there is not one. I was expecting the explanation to only be in the RFS (and for the need for an explanation to be quite rare for non-native packages). Subsequent uploads of any package should ensure that debtags are complete. I don't think this should be a hard requirement either. On the other hand when debexpo gets deployed and mentors.d.n is more useful for sponsors I'll certainly be de-prioritising such packages. OK, not a hard requirement but a penalty in that omitting it reduces the chances of actually getting a sponsor. Right now, I'm looking for as many filters as possible until I can make more time available for sponsoring, whilst also trying to help maintainers make it easy for me to spot the packages that I *will* sponsor (RC bugs). Another pointer is to post to the RC bug report that a package with a possible fix has been uploaded to mentors - some maintainers do that already, so well done to those people. Also consider adding a comment on the unofficial RC bugs page: http://bts.turmzimmer.net/details.php?bydist=bothsortby=packagesignmerged=onigncontrib=onignnonfree=onnew=7refresh=1800 (and if any DD can remember how to fix oldpeople sites to show up on people again, let me know - the ordinary fix has not worked) scp/rsync your public_html from gluck.d.o - yourpc - ravel.d.o. Doh! Thanks Paul. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpjGePOo4KHA.pgp Description: PGP signature
Re: Homepages and debtags (was Re: RFS: monkey)
On Mon, Nov 24, 2008 at 7:53 PM, Neil Williams [EMAIL PROTECTED] wrote: Right now, I'm looking for as many filters as possible until I can make more time available for sponsoring, whilst also trying to help maintainers make it easy for me to spot the packages that I *will* sponsor (RC bugs). You might want to consider adding any automatable package metrics you can think of to this brainstorming page: http://wiki.debian.org/DebianMentorsNet Hopefully debexpo will be deployed soon and sponsors can use it to prioritise packages uploaded there. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: monkey
Hi Roman,
first of all: thank you very much for your help!
Creating the package with Standards-Version 3.7.3 shows errors like
Version you are using is newer than the latest one. Please update
lintian. (I don't remember the exact error message) But all my
packages are up2date.
I made some changes in the package regarding dh_installinit,
dh_installchangelog. I also created a new init-script with
start-stop-daemon and opened a wnpp bug (#468183)
Also lintian is fine now.
Should i create a new 0.9.2-1 version with my changes or is it a better
solution to make a 0.9.2-2 version?
I think uploading the same version to mentors is not possible, right?
Thanks again,
Thorsten Schmale
On 26/02/08 14:39 +0100, Romain Beauxis wrote:
Le Tuesday 26 February 2008 14:09:34 Thorsten Schmale, vous avez écrit :
Dear mentors,
Hi !
I am looking for a sponsor for my package monkey.
Few remarks on your package.
It builds these binary packages:
monkey - a small http server
* Could you provide more informations, we already have other http server, so
why this one in particular ?
* in debian/control:
- Standards-Version: 3.7.2, should be 3.7.3
- a small http server: should avoid the a I think. Also, a more
specific
description would be good (cf up)
* In debian/rules:
- Why do you pass -n option to dh_installinit ? This generates code
snippets
for maintainer scripts that turns out to be exactly what you have..
- You don't have to move changelog in rules, just pass the good name to
dh_installchangelog
- Same for monkey.conf, you should use a install file or dh_install...
* in debian/changelog
- You should open a ITP bug (use reportbug wnpp in command line) and close
it in the initial changelog.
* Daemon init:
- You perhaps could run the daemon under a specific user, not nobody. You
will then need to create the user in maintainer scripts. You can look at
other mackaged daemons for that.
- Also the init script doesn't look very standard (not tested though). In
particular it doesn't call start-stop-daemon. It also has a lintian warning
(see below). Have you compared with other packaged daemons ??
Appart from those remarks, you have lintian issues (some of which are
reported
already...):
14:32 [EMAIL PROTECTED] /tmp/monkey-0.9.2%
lintian -viI ../monkey_0.9.2-1_amd64.changes
N: Setting up lab in /tmp/ie1BcMJmsS ...
N: Processing changes file monkey_0.9.2-1_amd64.changes ...
N: Processing 2 packages...
N:
N: Processing source package monkey (version 0.9.2-1) ...
W: monkey source: debian-rules-ignores-make-clean-error line 29
N:
N: A rule in the debian/rules file for this package calls the package's
N: clean or distclean target with a line like:
N:
N:-$(MAKE) distclean
N:
N: The leading - tells make to ignore all errors. Normally this is done
N: for packages using Autoconf since Makefile may not exist. However,
N: this line ignores all other error messages, not just the missing
N: Makefile error. It's better to use:
N:
N:[ ! -f Makefile ] || $(MAKE) distclean
N:
N: so that other error messages from the clean or distclean rule will
N: still be caught (or just remove the - if the package uses a static
N: makefile).
N:
W: monkey source: out-of-date-standards-version 3.7.2 (current is 3.7.3)
N:
N: The source package refers to a 'Standards-Version' that is starting to
N: get out of date, compared to current Policy. You can safely ignore
N: this warning, but please consider updating the package to current
N: Policy.
N:
N:
N: Processing binary package monkey (version 0.9.2-1) ...
I: monkey: hyphen-used-as-minus-sign usr/share/man/man8/monkey.8.gz:17
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 cutpaste
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: monkey: hyphen-used-as-minus-sign
Re: RFS: monkey
Le Wednesday 27 February 2008 16:13:58 Thorsten Schmale, vous avez écrit : Hi Roman, Hi ! first of all: thank you very much for your help! No pb, the issue is just free time :) Creating the package with Standards-Version 3.7.3 shows errors like Version you are using is newer than the latest one. Please update lintian. (I don't remember the exact error message) But all my packages are up2date. Sounds like your tools are not up to date. Are you on testing ? I made some changes in the package regarding dh_installinit, dh_installchangelog. I also created a new init-script with start-stop-daemon and opened a wnpp bug (#468183) Nice Also lintian is fine now. Should i create a new 0.9.2-1 version with my changes or is it a better solution to make a 0.9.2-2 version? That's up to you, but I personaly prefer an initial debian version for an initial upload.. I think uploading the same version to mentors is not possible, right? I don't really know.. Do as you like, changelog and version is not really an issue. What matters is the quality of the upoaded package ;-) Romain
Re: RFS: monkey
Hi again, i'm not on testing - i'm using etch currently. Is that a problem? I created a new version 0.9.2-1 with all modifications and uploaded it again to mentors. Can you please have a look at it and tell me what to do next? Thanks, Thorsten On 27/02/08 16:37 +0100, Romain Beauxis wrote: Le Wednesday 27 February 2008 16:13:58 Thorsten Schmale, vous avez écrit : Hi Roman, Hi ! first of all: thank you very much for your help! No pb, the issue is just free time :) Creating the package with Standards-Version 3.7.3 shows errors like Version you are using is newer than the latest one. Please update lintian. (I don't remember the exact error message) But all my packages are up2date. Sounds like your tools are not up to date. Are you on testing ? I made some changes in the package regarding dh_installinit, dh_installchangelog. I also created a new init-script with start-stop-daemon and opened a wnpp bug (#468183) Nice Also lintian is fine now. Should i create a new 0.9.2-1 version with my changes or is it a better solution to make a 0.9.2-2 version? That's up to you, but I personaly prefer an initial debian version for an initial upload.. I think uploading the same version to mentors is not possible, right? I don't really know.. Do as you like, changelog and version is not really an issue. What matters is the quality of the upoaded package ;-) Romain -- I AM NOT A LEAN MEAN SPITTING MACHINE I AM NOT A LEAN MEAN SPITTING MACHINE I AM NOT A LEAN MEAN SPITTING MACHINE I AM NOT A LEAN MEAN SPITTING MACHINE Bart Simpson on chalkboard in episode 3F02 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: monkey
Hello, On Wed, 27 Feb 2008, Thorsten Schmale wrote: i'm not on testing - i'm using etch currently. Is that a problem? Even if you run etch you should probably have a testing/unstable copy of lintian and the various documents like policy, developer's ref and maint-guide. Of course, you should do your builds in an unstable chroot as well (probably using pbuilder). One solution to this is to have a testing/unstable chroot with a minimal install for development (lintian, pbuilder and the documents at the very least). You can use (c)debootstrap to build such a chroot. (Note that pbuilder will then create a chroot inside this chroot but that is fine of course!). Regards, Kapil. -- signature.asc Description: Digital signature
RFS: monkey
Dear mentors, I am looking for a sponsor for my package monkey. * Package name: monkey Version : 0.9.2-1 Upstream Author : Eduardo Silva [EMAIL PROTECTED] * URL : http://monkeyd.sourceforge.net * License : GPL Section : web It builds these binary packages: monkey - a small http server The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/m/monkey - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/m/monkey/monkey_0.9.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards Thorsten Schmale signature.asc Description: Digital signature
Re: RFS: monkey
Le Tuesday 26 February 2008 14:09:34 Thorsten Schmale, vous avez écrit :
Dear mentors,
Hi !
I am looking for a sponsor for my package monkey.
Few remarks on your package.
It builds these binary packages:
monkey - a small http server
* Could you provide more informations, we already have other http server, so
why this one in particular ?
* in debian/control:
- Standards-Version: 3.7.2, should be 3.7.3
- a small http server: should avoid the a I think. Also, a more specific
description would be good (cf up)
* In debian/rules:
- Why do you pass -n option to dh_installinit ? This generates code snippets
for maintainer scripts that turns out to be exactly what you have..
- You don't have to move changelog in rules, just pass the good name to
dh_installchangelog
- Same for monkey.conf, you should use a install file or dh_install...
* in debian/changelog
- You should open a ITP bug (use reportbug wnpp in command line) and close
it in the initial changelog.
* Daemon init:
- You perhaps could run the daemon under a specific user, not nobody. You
will then need to create the user in maintainer scripts. You can look at
other mackaged daemons for that.
- Also the init script doesn't look very standard (not tested though). In
particular it doesn't call start-stop-daemon. It also has a lintian warning
(see below). Have you compared with other packaged daemons ??
Appart from those remarks, you have lintian issues (some of which are reported
already...):
14:32 [EMAIL PROTECTED] /tmp/monkey-0.9.2%
lintian -viI ../monkey_0.9.2-1_amd64.changes
N: Setting up lab in /tmp/ie1BcMJmsS ...
N: Processing changes file monkey_0.9.2-1_amd64.changes ...
N: Processing 2 packages...
N:
N: Processing source package monkey (version 0.9.2-1) ...
W: monkey source: debian-rules-ignores-make-clean-error line 29
N:
N: A rule in the debian/rules file for this package calls the package's
N: clean or distclean target with a line like:
N:
N:-$(MAKE) distclean
N:
N: The leading - tells make to ignore all errors. Normally this is done
N: for packages using Autoconf since Makefile may not exist. However,
N: this line ignores all other error messages, not just the missing
N: Makefile error. It's better to use:
N:
N:[ ! -f Makefile ] || $(MAKE) distclean
N:
N: so that other error messages from the clean or distclean rule will
N: still be caught (or just remove the - if the package uses a static
N: makefile).
N:
W: monkey source: out-of-date-standards-version 3.7.2 (current is 3.7.3)
N:
N: The source package refers to a 'Standards-Version' that is starting to
N: get out of date, compared to current Policy. You can safely ignore
N: this warning, but please consider updating the package to current
N: Policy.
N:
N:
N: Processing binary package monkey (version 0.9.2-1) ...
I: monkey: hyphen-used-as-minus-sign usr/share/man/man8/monkey.8.gz:17
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 cutpaste
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: monkey: hyphen-used-as-minus-sign usr/share/man/man8/monkey.8.gz:20
I: monkey: hyphen-used-as-minus-sign usr/share/man/man8/monkey.8.gz:21
I: monkey: hyphen-used-as-minus-sign usr/share/man/man8/monkey.8.gz:22
I: monkey: hyphen-used-as-minus-sign usr/share/man/man8/monkey.8.gz:23
I: monkey: hyphen-used-as-minus-sign usr/share/man/man8/monkey.8.gz:24
W: monkey: init-d-script-stops-in-s-runlevel /etc/init.d/banana
N:
N: This /etc/init.d script specifies the S runlevel in Default-Stop in
N: its LSB keyword section. The S runlevel is not a real runlevel and is
N: only used during boot. There is no way to switch to it and hence no
N: use for stop scripts for it, so S should be removed from Default-Stop.
N:
W: monkey: new-package-should-close-itp-bug
N:
N: This package appears to be the first packaging of a new upstream
N: software package (there is only one changelog entry and the
