Richard Burton schrieb:
Am I becoming a pain yet?
No, but patches would be cool if you are skilled enough for that. (You
could get svn commit access on svn.debian.org for that)
Sure, no problem. Sorry I've been lazy with patches previously. My
alioth userid is raburton-guest.
I vote for ignore.
Questionable, some other logwatch scripts report connection timeouts.
At least one ignores the timout but contains a comment like "why do we
ignore this?". And that's the solution I'll choose. :-)
I'm happy to go with whatever the general policy is, but couldn't see a
lot of value in reporting it in this particular case.
The problem is that there is no general policy (except
HOWTO-Customize-LogWatch where short definition for each major detail
level is given), the only way is to find out what was previously done.
7.2.1-2test0 is out, you can test.
I've have added you to pkg-logwatch members. You should have write
access to the svn repository on svn.debian.org. I've have also created a
mailing list for discussion: [EMAIL PROTECTED]
All svn commits are posted there too.
Please don't feel forced now to do commits instead of bug reports.
However, this your chance to get your bug fixes more quickly incorporated.
Note that my custom build system is not documented. For the start: Place
the upstream tarball in trunk and execute
./buildversion.sh <upstream-version>
then cd in the new directory and execute debuild from the devscripts
package. (Or whatever you prefer to build debs from source)
Willi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
