Lighttpd released 1.4.11, much nicer than the bug-infested 1.4.10 - or so it appears. I haven't seen nor required any fixes for it. Items: * Bump version * Remove epatch for gratuitous 1.4.10 release * Bug:116767 Add ~arm keyword * Bug:123436 Add ~alpha keyword BTW: Can't we at least unmask 1.4.8 already? I and several coworkers use lighttpd. 1.3 is useless as is, and unless someone really needs it....
Created attachment 82411 [details] lighttpd-1.4.11.ebuild lighttpd-1.4.11.ebuild * Bump version * Remove epatch for gratuitous 1.4.10 release * Bug:116767 Add ~arm keyword * Bug:123436 Add ~alpha keyword
*** Bug 126752 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > * Bug:123436 Add ~alpha keyword Joshua, thank you for taking the time to work on this ebuild. Users are a very important part of the Gentoo community. Just so you are aware, only arch teams are able to do keywording. The alpha arch team has not added the ~alpha keyword to lighttpd yet because it hasn't been fully tested on alpha. Additionally, there are two dependencies dev-libs/libmemcache and dev-libs/fcgi which also need to be tested and keyworded for alpha. There is more info on this topic in the "Gentoo Development Guide": http://dev.gentoo.org/~plasmaroo/devmanual/keywording/#keywording-new-packages
Created attachment 83993 [details, diff] Small change on mod_scgi preventing segfault A one-character patch preventing a segfault. By weigon on #lighttpd@irc.freenode.net
Created attachment 84289 [details] lighttpd-1.4.11-r1.ebuild Slightly modified ebuild for lighttpd 1.4.11. Added the "lfs" USE-flag from Bug 126980. Also added patches from http://trac.lighttpd.net/trac/wiki/Release-1.4.11-bugs for tickets 598, 606 and 607.
Created attachment 84290 [details] files/1.4.11/ticket598_1.diff
Created attachment 84291 [details] files/1.4.11/ticket598_2.diff
Created attachment 84292 [details] files/1.4.11/ticket606.diff
Created attachment 84293 [details] files/1.4.11/ticket607.diff
When will lighttpd-1.4.11 be added to portage ?
Is there any chance we'll see this in Portage before it hits Debian stable?
heh. I have to put in a third remark here, are we waiting for this to ferment? Or become obsolete? thanks.
1.5 will be out before this gets into portage, iam using the ebuild and patches from this bug and have been for over a week, no bugs to be found on x86 so far.
Well in the meanwhile, this is available on the asylumware-portage overlay: info: http://embassy.asylumware.com/projects/portage
FWIW, using the asylumwear ebuild works great on x86 (dual athlon mp) as far as I can tell (not rigorously tested, but around 30 instances running our main shared hosting box makes me feel warm and fuzzy).
I think I spotted a small bug in the ebuild. Here is the diff between a fixed and non fixed version. src_compile() { econf --libdir=/usr/$(get_libdir)/${PN} \ - --enable-lfs \ $(use_enable ipv6) \ $(use_enable lfs) \ $(use_with bzip2) \ I am running 1.4.11-r1 atm and I'm not seeing any strange things so it is stable for me this far. When will 1.4.11 get into portage?
I have just changed my ebuild with that fix and it works without a flaw. I hope this can be added ASAP *hint* *hint*
Created attachment 87892 [details] lighttpd-1.4.11-r2.ebuild Created lighttpd-1.4.11-r2.ebuild on Asylumware. - removed superfluous/errant --enable-lfs https://embassy.asylumware.com/projects/portage rsync://embassy.asylumware.com/asylumware-portage
1.4.11 now in your next esync - thanks everybody so far, the lfs use flag is not included, sorry
can we close this one and open a new one for the lfs-useflag to resolve blocks/depends on alpha?
the lfs-useflag issue is covered in bug 126980 - closing
