Changes with nginx 1.1.5 05 Oct 2011 *) Feature: the "uwsgi_buffering" and "scgi_buffering" directives. Thanks to Peter Smit. *) Bugfix: non-cacheable responses might be cached if "proxy_cache_bypass" directive was used. Thanks to John Ferlito. *) Bugfix: in HTTP/1.1 support in the ngx_http_proxy_module. *) Bugfix: cached responses with an empty body were returned incorrectly; the bug had appeared in 0.8.31. *) Bugfix: 201 responses of the ngx_http_dav_module were incorrect; the bug had appeared in 0.8.32. *) Bugfix: in the "return" directive. *) Bugfix: the "ssl_session_cache builtin" directive caused segmentation fault; the bug had appeared in 1.1.1. Please add it to the tree.
While at it, some plugins have newer versions, too: HTTP_UPLOAD_PROGRESS_MODULE_PV="0.8.2" => "0.8.3" HTTP_CACHE_PURGE_MODULE_PV="1.3" => "1.4"
Changes with nginx 1.1.6 17 Oct 2011 *) Change in internal API: now module context data are cleared while internal redirect to named location. Requested by Yichun Zhang. *) Change: if a server in an upstream failed, only one request will be sent to it after fail_timeout; the server will be considered alive if it will successfully respond to the request. *) Change: now the 0x7F-0x1F characters are escaped as \xXX in an access_log. *) Feature: "proxy/fastcgi/scgi/uwsgi_ignore_headers" directives support the following additional values: X-Accel-Limit-Rate, X-Accel-Buffering, X-Accel-Charset. *) Feature: decrease of memory consumption if SSL is used. *) Bugfix: some UTF-8 characters were processed incorrectly. Thanks to Alexey Kuts. *) Bugfix: the ngx_http_rewrite_module directives specified at "server" level were executed twice if no matching locations were defined. *) Bugfix: a socket leak might occurred if "aio sendfile" was used. *) Bugfix: connections with fast clients might be closed after send_timeout if file AIO was used. *) Bugfix: in the ngx_http_autoindex_module. *) Bugfix: the module ngx_http_mp4_module did not support seeking on 32-bit platforms.
is there any reason...problems.. bugs that prevent those newer minor versions to be in portage..?
This is just a minor update for a development version. Not nescessary, just a nice-to-have. So there is no real need to be eager. :) rion-overlay has it: http://code.google.com/p/rion-overlay/source/detail?r=5afb41a14aa961058b94de6f7aa8f6533fdb41e3
(In reply to comment #3) > is there any reason...problems.. bugs that prevent those newer minor versions > to be in portage..? yes: some people have a life beside gentoo.
1.1.x is the unstable branch in nginx, and only available on ~arch. For such a minor update, i think renaming the file represents a very low risk of breakage. The changelog only mentions few bugfixes, so probably nothing was changed on the build system or whatever gentoo is concerned with. I've copied nginx-1.1.4.ebuild to nginx-1.1.6.ebuild and bumped two modules versions as mentionned in comment #1 (though i dont use them). The resulting ebuild installs fine and i have seen no problem so far on the web server. Downloads of all files/modules triggered by manifest creation are ok too. I dont have gentoo commit access, that's as much as I can do.
thanks :)
