Hello! As quoted here: bug 517034#c3 from here http://nginx.com/blog/nginx-1-6-1-7-released/ ""Which version should I use? In general, you should deploy the NGINX mainline branch at all times. [...] "" but the following text is forgotten: "You may wish to use stable if you are concerned about possible impacts of new features, such as incompatibility with third-party modules or the introduction of bugs in new features." As for now current stable in gentoo version of nginx-1.7.6 is completely broken when USE=rtmp (bug 525836). And no other version is in portage! After updating my server witch mainly uses ebuilds from stable gentoo branch my video-streaming web-server had gone and I had to compile it from sources out of portage. I'm not alone as we can also see from #525866. The fix of the situation is to use nginx 1.7.6 with unstable rtmp from its git master branch or to use "stable" nginx 1.6.2 with stable rtmp-module 1.1.5. I'm completely sure that the "stable way" is the second with stable nginx and stable rtmp-module. By the way there is other bug witch prevents building nginx-1.7.6 with stable rtmp-module, it's fixed now by rtmp-nginx-1.7.6.patch. Dear nginx maintainers! You were so kind to add to nginx ebuild 20 3rd party modules. I'm really grateful for you. Please continue be so kind and give us an ability to use them stably in stable branch. Give stable version of nginx in stable gentoo branch back to us. Thank you!
bug 517034 comment 1: > If you need older versions, please use the nginx-overlay. and 1.6.x was never in g-x86. *** This bug has been marked as a duplicate of bug 519796 ***
(In reply to Alex Xu (Hello71) from comment #1) > bug 517034 comment 1: > > > If you need older versions, please use the nginx-overlay. > I'm sorry, but it seems that you have not ever read what I've wrote? bug 517034 comment 1: > As recommended by upstream: nginx-1.7.x is the mainline which should be used unless for a good reason We have really got reason: gentoo ebuild of nginx uses 20 3rd party modules. Usage of one is completely broken without patches from its unstable version and I'm not sure that it's not so with others. Bleeding edge distributions like arch linux or fedora (and obviously stable one like debian, ubuntu or centos) have not more than 1.6.2 version as stable one in their distributions. I really can't guess why it's not so in gentoo. Yes, I can use nginx-overlay on my server, but I have no overlays on any of my production servers cause I trusted to gentoo stable branch. And it's really strange that you make me to add overlay to use stably main part of my web-servers. We even have no 1.6.2 in nginx-overlay if we speak about https://github.com/gentoo/nginx-overlay . > and 1.6.x was never in g-x86. > > *** This bug has been marked as a duplicate of bug 519796 ***
(In reply to Alex Xu (Hello71) from comment #1) > bug 517034 comment 1: > > and 1.6.x was never in g-x86. > My miss, please read "readd" as "add". But I don't thing it changes the situation.
There's been several tickets about this, and all have been closed as duplicate or wontfix. I don't understand, nginx is an important piece of technologie and is treated a a third-class citizen in gentoo. Ningx 1.7 is probably great, and i'm sure lot of people are happy to have it in tree, but we need a stable, proven one as well. At least I do, and it seems lot of other people do. Overlays are supposed to be for testing, not for stable stuff. Usualy, the stable stuff is in the main tree, i can't understand neither why we are asked to install an overlay to get stable ebuilds. Currently i have a local overlay with stable 1.6, this is not confortable at all.
Hello! We still have no working version of nginx with rtmp in portage. It will be good to hear some answer from nginx gentoo maintainers.
By the way, apache 2.2 is stable in gentoo but 2.4 is the last version. Why isn't so in nginx? Only according to nginx developers words taken out of context? It seems that I disprove the position with 1.7.* branch first comment of this bug.
I don't use apache but what I can see is that apache 2.2 and ~2.4 is in portage. I think this should be pretty fine. On nginx there is 1.7.4 and 1.7.6 right now available. Upstream has to versions: mainline & stable What would make sense to me is, to see some thing like this available in portage nginx 1.6.2 ~1.7.4 ~1.7.6 I really appreciate the work you do, specially to implement third party modules, nginx is really conformable to use with gentoo! But right now it is broken. But regardless of what caused the problem with rtmp lately - I don't know right now if cause by the module it self or a problem with nginx 1.7.6 - but out of my view something like this could happen any time with mainline! At least the expectation that anything like this happens with stable is much lower. You read right, the upstream recommendation is to stay with mainline, that's is completely fine to me. But you to have to decide sometimes if you want to got with new features that maybe buggy or stay stable. Most distros have already made there decision - FOR THERE USERS - so they have ONLY nginx 1.6! So I really prefer to HAVE the choice, rather to have only stable. There is already an overlay for nginx which is maintained by someone who has/want to come over all mention problems. https://github.com/gentoo/nginx-overlay#nginx-overlay The after all this, the question to me is: why is this work not done in portage and why don't work these guys here but on an external overlay?
I'm closing this in favour of 1.8.x that landed in tree yesterday. As of 1.8.x we will treat stable differently and have a specific slot for the mainline series (1.9.x). All people (users and devs) involved in the discussion of this: I appreciate your feedback; without it we might not have changed strategy.
