# and to be frank I believe this bug is just plain invalid severity 511687 normal thanks
On Tue, Jan 13, 2009 at 02:06:36PM +0000, Bastien ROUCARIES wrote: > Package: git-daemon-run > Version: 1:1.5.6.5-2 > Severity: serious > > Seveirty serious because it is a policy violation: according to section 9.3 > of debian policy. > > Please add a script, and document correctly dependancy using > http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot > > Regards No it doesn't _need_ to, the very standard way to use git-daemon is usually through a super-server. git-daemon-run is just a way to enable git-daemon into runit, which is the packager choice and has nothing to do with the policy as-is. git-daemon is part of git-core and it would make really no sense to enable git-daemon as an init script part of this package. As an example, I serve git-daemon through xinetd on my server, and I just had to write this: $ cat /etc/xinetd.d/git-daemon # description: The git server offers access to git repositories service git { disable = no type = UNLISTED port = 9418 socket_type = stream wait = no user = nobody server = /usr/bin/git-daemon flags = IPv6 server_args = --inetd --export-all --base-path=/git/public --user-path=public_git log_on_failure += USERID } Arguably the packager could document this or a way to enable git-daemon through the usual inetd servers, but that's it IMNSHO. Cheers, -- ·O· Pierre Habouzit ··O madco...@debian.org OOO http://www.madism.org
pgpeYwjF1baW9.pgp
Description: PGP signature