[pkg-lighttpd] First issue, patch system?

[Krzysztof Krzyzaniak]

Torsten Marek wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi Krzysztof,
> 
> thanks for creating the mailing list! I'll inaugurate it with a technical mail.
> 
> While I was rebooting my machine, I found out that lighttpd needs the SHELL
> environment variable set to be able to execute include_shell directives in the
> configuration file. Maybe you already saw it, but the creation of the file
> extension -> mimetype dictionary (or hash, if you prefer) is done by a perl
> script, using /etc/mime.types. Thus, lighttpd fails when it is started by init
> rather than a user.
> 
> The code is in proc_open.c, l. 154
> if (NULL == (shell = getenv(SHELLENV))) {
>     fprintf(stderr, "env %s is required", SHELLENV);
>     return -1;
> }
> 
> where SHELLENV contains "SHELL" on POSIX. Couldn't "shell" just be hardcoded to
>  /bin/sh?

First of all I think all such bugs (which I think are general) should be 
reported upstream.

> Following that, which patch system should we use? I've been working with dpatch
> mostly and am quite satisfied with it, but I know that some devs don't like it.

I know dpatch, dpatch is ok (I've use it in motor package).

Issues:

1) there is lighttd 1.4.8 without debian directory so you can upgrade 
package

2) There is short tutorial for svn-buildpackage 
<http://pkg-perl.alioth.debian.org/subversion.html>, second is included 
in svn-buildpackage

3) We have created svn module in svn.debian.org so we can make initial 
upload here.


   eloy
-- 
-------e-l-o-y-----------e-l-o-y- at -t-r-a-n-s-i-l-v-a-n-i-a-.-e-u-.-o-r-g------

        jak to dobrze, że są oceany - bez nich byłoby jeszcze smutniej