New prereleases: 1.4.20-r2294 and 1.5-r2294 40

Posted by icy Wed, 20 Aug 2008 17:20:00 GMT

It’s been some time since the last 1.4 release and especially since the last 1.5 prerelease. There have been a lot of fixes in both branches so be sure to check them out, no matter if you are using 1.4 or 1.5.

You can get the prereleases from this url: http://opensu.se/~darix/lighttpd/

The 1.4.20 changes can be read here:
http://trac.lighttpd.net/trac/browser/branches/lighttpd-1.4.x/NEWS
While 1.5 changes can be fetched from here:
http://trac.lighttpd.net/trac/browser/trunk/NEWS

We ask you to test these snapshots as extensive as possible and report any broken things back to us.
If everything goes well and no showstoppers are encountered, there will be an official 1.4.20 release soon.

As for 1.5: should this prerelease be stable and bugfree enough, it will be the last prerelease and there will be a 1.5.0 release. It will not retire the 1.4 branch though. There are still some things missing in 1.5 like internal spawning of fcgi backends that prevent it form being the next main branch.

You can thank stbuehler for all his hard work he has put into both trees as he is responsible for nearly all of the work recently.

If you want to get the latest source for any branch, you can get it from our svn repository.
Documentation to do so can be obtained from this page:
http://trac.lighttpd.net/trac/wiki/Devel/Subversion
Bug reports or feature requests can be filed in our trac ticket system:
http://trac.lighttpd.net/trac/newticket
Please make sure to check if there isn’t a ticket already here:
http://trac.lighttpd.net/trac/report


Thank you for using lighty.

Comments

Leave a response

  1. Josh Davis Wed, 20 Aug 2008 17:37:45 GMT
    Nice to hear. I'm subscribed to Lighty's timeline (as well as the sandbox's...) so it doesn't come to me as a surprise, but those who don't follow Lighty's development as closely will surely appreciate the good news :) Keep up the good work.
  2. Brad Smith Thu, 21 Aug 2008 02:13:54 GMT
    The 1.4-r2294 snapshot unlike all previous 1.4 releases is broken with bmake. make all-recursive Making all in src make: don't know how to make |. Stop in /usr/ports/www/lighttpd/w-lighttpd-1.4.20.r2294/lighttpd-1.4.20/src. BTW, I would have opened a ticket but the authentication/password reset thing with your Trac is broken.
  3. 191919 Thu, 21 Aug 2008 02:30:09 GMT
    the 1.5 prerelease cannot be built:

    /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DLIBRARY_DIR="\"/usr/local/lib\"" -I. -I.. -D_REENTRANT -D__EXTENSIONS__ -I/usr/local/include -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGE_FILES -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -g -O2 -Wall -W -Wshadow -pedantic -std=gnu99 -MT mod_status.lo -MD -MP -MF .deps/mod_status.Tpo -c -o mod_status.lo mod_status.c
    gcc -DHAVE_CONFIG_H -DLIBRARY_DIR=\"/usr/local/lib\" -I. -I.. -D_REENTRANT -D__EXTENSIONS__ -I/usr/local/include -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGE_FILES -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -g -O2 -Wall -W -Wshadow -pedantic -std=gnu99 -MT mod_status.lo -MD -MP -MF .deps/mod_status.Tpo -c mod_status.c -fno-common -DPIC -o .libs/mod_status.o
    mv -f .deps/mod_status.Tpo .deps/mod_status.Plo /bin/sh ../libtool --tag=CC --mode=link gcc -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -g -O2 -Wall -W -Wshadow -pedantic -std=gnu99 -module -export-dynamic -avoid-version -no-undefined -o mod_status.la -rpath /usr/local/lib mod_status.lo liblightcomp.la
    gcc -o .libs/mod_status.so -bundle .libs/mod_status.o ./.libs/liblightcomp.dylib -L/usr/local/lib /usr/local/lib/libpcre.dylib /usr/local/lib/libgthread-2.0.dylib /usr/local/lib/libglib-2.0.dylib /usr/local/lib/libintl.dylib /usr/lib/libiconv.dylib
    Undefined symbols:
    "_network_get_backends", referenced from:
    _mod_status_handle_server_config in mod_status.o
    "_network_get_backend_info_by_type", referenced from: _mod_status_handle_server_config in mod_status.o
    ld: symbol(s) not found
    collect2: ld returned 1 exit status
    make[3]: *** [mod_status.la] Error 1
    make[2]: *** [all-recursive] Error 1
    make[1]: *** [all-recursive] Error 1
    make: *** [all] Error 2
    ~/apps/lighttpd-1.5.0#

  4. 191919 Thu, 21 Aug 2008 02:34:18 GMT
    network.c and connections.c (and perhaps some others) are missed in liblightcomp?
  5. 191919 Thu, 21 Aug 2008 02:35:59 GMT
    quote: There are still some things missing in 1.5 like internal spawning of fcgi backends that prevent it form being the next main branch.

    What we can see this nice feature? :)
  6. akrus Thu, 21 Aug 2008 04:40:56 GMT
    hello! could you please implement the patch from bugreport:1288 ? i'm really missing client-certificate authorization :(
  7. stbuehler Thu, 21 Aug 2008 06:04:49 GMT
    Brad Smith: use gnu make (gmake)
    akrus: too late for 1.4.20
  8. akrus Thu, 21 Aug 2008 06:22:12 GMT
    stbuehler: maybe for 1.4.21 or 1.5.x?
  9. stbuehler Thu, 21 Aug 2008 06:40:29 GMT
    maybe.
  10. akrus Thu, 21 Aug 2008 07:55:01 GMT
    it would be great. thanks :) keep up good work :)
  11. cla Thu, 21 Aug 2008 09:02:49 GMT
    (cd .libs && rm -f mod_evasive.la && ln -s ../mod_evasive.la mod_evasive.la) make[3]: *** No rule to make target `mod_fastcgi.lo', needed by `mod_fastcgi.la'. Stop.
  12. happypanda Thu, 21 Aug 2008 11:17:13 GMT
    Yay! Nice to see some new releases... External fcgi spawning will make it's way into 1.5 eventually, right?
  13. icy Thu, 21 Aug 2008 11:22:34 GMT
    External fcgi spawning is the current way to do it in 1.5 (using spawn-fcgi)
  14. happypanda Thu, 21 Aug 2008 14:14:16 GMT
    icy: sorry, I meant internal spawning
  15. James Thu, 21 Aug 2008 16:01:23 GMT
    Any idea if x-lighttpd-send-file will support resuming aka content range etc ?
  16. mlx Thu, 21 Aug 2008 18:35:27 GMT
    Sweet :-)

    Thanks a lot for those new pre-releases!
  17. Jonah Thu, 21 Aug 2008 19:36:28 GMT
    I am curious about content-range support with x-lighttpd-send-file as well... did this get released? (http://trac.lighttpd.net/trac/ticket/865)
  18. rapidshare premium account Thu, 21 Aug 2008 21:24:29 GMT
    been using lighty for over a year now ... never going back to apache :) Nick
  19. eric Thu, 21 Aug 2008 22:16:38 GMT
    mod_magnet was removed?
  20. hoffie Fri, 22 Aug 2008 09:33:21 GMT
    What makes you think that mod_magnet was removed? There have never been such plans.
  21. Neville Mon, 25 Aug 2008 05:15:53 GMT
    Hi, I have been using lighttpd 1.4.19 on my development server (ubuntu) and production server (debian). The speed is amazing and love the stability as well. It would be great if the http://www.lighttpd.net/ include binaries for major distros. like debian, ubuntu and cent os as I do find that updates come rather late from the distros. repositories.
  22. stbuehler Mon, 25 Aug 2008 14:01:46 GMT
    We will not provide binary packages, and there are many reasons for this.
  23. Steve Wed, 27 Aug 2008 08:41:07 GMT
    Great work guys, keep it up. I have been watching the development closely and there sure has been a lot of bug fixes being made to the 1.4.x branch. Can't wait to try it out :)
  24. Jan Berger Fri, 29 Aug 2008 12:23:35 GMT
    Awesome! Thanks for this great release. I'm excited to test it this evening.
  25. GW Sun, 31 Aug 2008 17:03:41 GMT
    "make: don't know how to make |. Stop" error was introduced somewhere between 2282 and 2294. It appears because someone put some | (pipe) characters near the end of src/Makefile.in in lines like: @CROSS_COMPILING_FALSE@configparser.c configparser.h: $(srcdir)/configparser.y $(srcdir)/lempar.c | $(LEMON) Just remove the pipe character before $(LEMON) and it should work.
  26. nitrox Sun, 31 Aug 2008 19:07:18 GMT
    @GW:
    current svn is ok. -> http://trac.lighttpd.net/trac/wiki/Devel/Subversion
  27. stbuehler Sun, 31 Aug 2008 19:27:11 GMT
    i guess GW is talking about 1.5 (in 1.4 it was "| lemon"); use gnu make and you should be fine (building the parsers is really ugly with make, you have to care about cross compile, -jX, ...). The "solution" in 1.4 is only a workaround (the automake faq says it can be fixed, but their solution doesn't work with -jX)
  28. Omar Tue, 02 Sep 2008 04:50:50 GMT
    Thank you very much for lighty. Been using for more than a year now and i think now i get the hang of it and how to refine configuration (especially on a light-weight server). Anyhow, i'm using ubuntu hardy server and the binary that is provided by ubuntu is rather old. At the same time, i would like to maintain an easy to update environment and don't want to break my server. Is there any plan you know of to update the repos of ubuntu to include lighty 1.5? Where can i find a comparison between the features of 1.4.x and 1.5? thanks.
  29. GW Tue, 02 Sep 2008 15:17:42 GMT
    @nitrox and @stbuehler: No? In http://trac.lighttpd.net/trac/browser/trunk/src/Makefile.am lines from 24 to 40 still contain the | (pipe) character and if I remove it it compiles fine under PMake (FreeBSD-7.0).
  30. Ali Tue, 02 Sep 2008 21:26:21 GMT
    Hm, thx very much, but it dont run when i test it now :-/
  31. Random dude Wed, 03 Sep 2008 02:00:08 GMT
    > like debian, ubuntu and cent os
    FYI: Ubuntu provides recent 1.4.19 version. They MAYBE slow BUT they're sometimes apply some patches or testing. So some delay is OK. As for Debian, they're conservative bastards. Too conservative sometimes. As for me, I'm preferring Ubuntu Server due to this fact on my servers so I do not have to stick to ancient versions of software and do not have to risk with updating all system to "unstable" or "testing" but still can have recent software.As for CentOS ... uhm er, I used it and do not like it (just another boring RedHat ripoff). Same applies as to Debian and what worse, it's packet manager is really ugly and changes too often. In such system I may even prefer to rebuild from source, especially if this gives some benefits\features.

    In general I'm thinking that putting task of maintaining distro-specific stuff on developers is not a good idea. Developers should create great programs, just like lighttpd is. Distro maintainers should cope with distro specifics.Nothing good happens when someone tries to do job he is not skilled to do.Do you remember Debian and SSL keys vuln?That's what happens when someone deals with thing he really shouln't.

    P.S. sorry for double-post.Pls delete upper one.And uhm, what about to delete trackback stuff with adult advertising? 8)
  32. CyberCr33p Wed, 03 Sep 2008 12:23:56 GMT
    We are shared hosting provider which use lighttpd sucessfully since 2006. I can't wait for the new release.
  33. U294 Thu, 04 Sep 2008 20:20:33 GMT
    > We ask you to test these snapshots as extensive as possible and report any broken things back to us.
    Don't you think that such news should appear on main page if you want EXTENSIVE test??? Surely it should be clearly stated that it's not release but rather pre-release. However, keep in mind: I figured out this fact some TWO WEEKS after your posting. You're quite successful in hiding news from people, so how you can expect extensive test then?... :(
  34. ben Thu, 04 Sep 2008 23:37:46 GMT
    hi, i just want to say thank you for this wonderful piece of software. walk on
  35. Murat Sun, 07 Sep 2008 05:27:32 GMT
    What happened to linux-aio support? It seems that option is removed from 1.5.0 ?
  36. kes Wed, 10 Sep 2008 15:10:52 GMT
    Murat, gthread-aio is replacement for it, I think.
  37. JamesD Sat, 13 Sep 2008 20:36:26 GMT
    No reply on Content-Range support for X-LIGHTTPD-send-file replies ? http://trac.lighttpd.net/trac/ticket/865
  38. Ray Stinger Sun, 14 Sep 2008 03:40:54 GMT
    1. --disable-ipv6 doesn't work, since the first pre-release of 1.5.0; 2. Is there any alternative way to enable GDBM and memcache? I am using FreeBSD 5.5 with these libs, but -lgdbm or -lfam doesn't work. 3. FAM and Sqlite could not be enabled, but I used them in 1.4.
  39. nitrox Sun, 14 Sep 2008 12:32:58 GMT
    @Ray Stinger and others:

    Bug reports or feature requests can be filed in our trac ticket system: http://trac.lighttpd.net/trac/newticket
    Please make sure to check if there isn’t a ticket already here: http://trac.lighttpd.net/trac/report

    We need this in our ticket system to work with and get things done.
    Thx for testing!
  40. helox@gmail.com Mon, 15 Sep 2008 07:38:55 GMT
    (plugin.c.541) plugin-version doesn't match lighttpd-version for extforward 2008-09-15 05:31:40: (server.c.1419) Initialization of plugins failed. Going down.
Comments