Bug 148996 – www-servers/lighttpd-1.4.13 version bump

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Kilburn Abrahams 2006-09-24 14:51:58 UTC]

lighttpd 1.4.12 released.

[Comment 1 Johan Bergström 2006-09-26 06:47:51 UTC]

In order to use the new mod_magnet (which you want :), one will need lua 5.1. Refs #124719.

[Comment 2 Johan Bergström 2006-09-26 06:50:59 UTC]

Further reading about mod_magnet can be found here: http://trac.lighttpd.net/trac/wiki/Docs%3AModMagnet

[Comment 3 Thilo Bangert (RETIRED) (RETIRED) 2006-09-29 14:03:27 UTC]

can't add version lighttpd-1.4.12 before lua-5.1 has hit the tree... bugger...

[Comment 4 Thilo Bangert (RETIRED) (RETIRED) 2006-10-10 09:06:14 UTC]

*** Bug 150721 has been marked as a duplicate of this bug. ***

[Comment 5 Thilo Bangert (RETIRED) (RETIRED) 2006-10-13 00:07:53 UTC]

Created attachment 99504 [details]
lighttpd-1.4.12.ebuild

due to popular demand - find attached an ebuild for version 1.4.12 of lighttpd

[Comment 6 Jari-Matti Mäkelä 2006-10-20 05:25:18 UTC]

Something wrong with the ebuilds? I've just installed lua-5.1.1 (http://bugs.gentoo.org/show_bug.cgi?id=124719). After that I tried to install 1.4.13 using the attached 1.4.12 ebuild (USE="lua" emerge lighttpd) and got:

--

checking for LUA... configure: error: Package requirements (lua >= 5.1) were not met:

No package 'lua' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables LUA_CFLAGS
and LUA_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

--

If I remove the lua dependency and install the newest lua (<5.1) from portage tree, it compiles just fine.

[Comment 7 Jari-Matti Mäkelä 2006-10-21 06:29:40 UTC]

(In reply to comment #6)
> If I remove the lua dependency and install the newest lua (<5.1) from portage
> tree, it compiles just fine.

A slight correction to the previous comment. I was not able to pass through the configuration checking with any version of lua when emerging lighttpd-1.4.13 with lua use flag. Lighttpd-1.4.12 compiles fine with the latest lua from portage with and without lua useflag. Lighttpd-1.4.13 compiles only without lua use flag set. It always fails in the econf stage, when --enable-lua is set.

[Comment 8 Johan Bergström 2006-10-21 14:42:24 UTC]

Jari-Matti: As i explained in the lua 5.1 ebuild thread a little earlier - there are no DSO's built, which makes it hard for lighttpd to link against lua.

[Comment 9 Jari-Matti Mäkelä 2006-10-22 01:50:55 UTC]

(In reply to comment #8)
> Jari-Matti: As i explained in the lua 5.1 ebuild thread a little earlier -
> there are no DSO's built, which makes it hard for lighttpd to link against lua.

Ok, no problem. The regressions in 1.4.12 aren't that critical. I can probably backport most critical fixes from svn trunk if needs be. Currently 1.4.11 is unusable because it somehow corrupts the webdav headers (using lighttpd as a webdav proxy for apache2), but 1.4.12 works fine.

[Comment 10 Cheng Zhang 2006-10-23 22:32:02 UTC]

FYI: lighttpd 1.4.13 released
http://blog.lighttpd.net/articles/2006/10/10/release-lighttpd-1-4-13

[Comment 11 Marcel Klein 2006-11-26 03:25:52 UTC]

dev-lang/lua-5.1.1 is in portage (but hard masked!).

lighttpd-1.4.13 compiles fine here.

[Comment 12 Marcel Klein 2006-11-26 03:27:37 UTC]

Created attachment 102741 [details]
lighttpd-1.4.13.ebuild

[Comment 13 Christian Hoffmann (RETIRED) 2007-01-08 16:25:54 UTC]

Nobody added any status information, so I'll just do it: lua-5.1.1 is no longer hardmasked and lighttpd-1.4.13 has been in the tree (hardmasked) since yesterday (Jan 7th).

[Comment 14 Robin Johnson 2007-01-09 18:06:09 UTC]

1.4.13 in the tree now.