Re: [ANNOUNCE] haproxy-2.2.0

2020-07-16 Thread Ryan O'Hara
On Fri, Jul 10, 2020 at 3:26 PM Илья Шипицин wrote: > instead of disabling Lua support, is it possible to build against Lua-5.3 ? > I recall there's Lua-5.3 on Fedora-33 > Right. I saw the same message, but it does not work. I sent a message to the Lua maintainer for Fedora last Friday and he

Re: [ANNOUNCE] haproxy-2.2.0

2020-07-10 Thread Илья Шипицин
instead of disabling Lua support, is it possible to build against Lua-5.3 ? I recall there's Lua-5.3 on Fedora-33 пт, 10 июл. 2020 г. в 21:20, Ryan O'Hara : > > > On Thu, Jul 9, 2020 at 2:24 PM Tim Düsterhus wrote: > >> Ryan, >> >> Am 09.07.20 um 20:34 schrieb Ryan O'Hara: >> > I'm currently

Re: [ANNOUNCE] haproxy-2.2.0

2020-07-10 Thread Willy Tarreau
On Fri, Jul 10, 2020 at 11:17:33AM -0500, Ryan O'Hara wrote: > On Thu, Jul 9, 2020 at 2:24 PM Tim Düsterhus wrote: > > > Ryan, > > > > Am 09.07.20 um 20:34 schrieb Ryan O'Hara: > > > I'm currently packaging this for Fedora. It seems to build just fine on > > > Fedora 32 and rawhide. Is there any

Re: [ANNOUNCE] haproxy-2.2.0

2020-07-10 Thread Ryan O'Hara
On Thu, Jul 9, 2020 at 2:24 PM Tim Düsterhus wrote: > Ryan, > > Am 09.07.20 um 20:34 schrieb Ryan O'Hara: > > I'm currently packaging this for Fedora. It seems to build just fine on > > Fedora 32 and rawhide. Is there any new build options or dependencies to > be > > aware of? I'm looking at the

Re: [ANNOUNCE] haproxy-2.2.0

2020-07-09 Thread Tim Düsterhus
Ryan, Am 09.07.20 um 20:34 schrieb Ryan O'Hara: > I'm currently packaging this for Fedora. It seems to build just fine on > Fedora 32 and rawhide. Is there any new build options or dependencies to be > aware of? I'm looking at the Makefile now and nothing jumps out at me. That > said, I am

Re: [ANNOUNCE] haproxy-2.2.0

2020-07-09 Thread Willy Tarreau
Hi Ryan, On Thu, Jul 09, 2020 at 01:34:40PM -0500, Ryan O'Hara wrote: > On Tue, Jul 7, 2020 at 12:41 PM Willy Tarreau wrote: > > > Hi, > > > > HAProxy 2.2.0 was released on 2020/07/07. It added 24 new commits > > after version 2.2-dev12. > > > > This is great. Thank you to all who contributed

Re: [ANNOUNCE] haproxy-2.2.0

2020-07-09 Thread Ryan O'Hara
On Tue, Jul 7, 2020 at 12:41 PM Willy Tarreau wrote: > Hi, > > HAProxy 2.2.0 was released on 2020/07/07. It added 24 new commits > after version 2.2-dev12. > This is great. Thank you to all who contributed to this release. I'm currently packaging this for Fedora. It seems to build just fine on

Re: [ANNOUNCE] haproxy-2.2.0

2020-07-08 Thread Willy Tarreau
On Wed, Jul 08, 2020 at 07:53:51PM +0200, Luke Seelenbinder wrote: > > We would then pick from the first > > list and if it's empty, then the next one. > > This slightly concerns me. Hopefully I'm just not quite understanding the > behavior. > > Would that imply request A would pick from the

Re: [ANNOUNCE] haproxy-2.2.0

2020-07-08 Thread Luke Seelenbinder
Hi Willy, Thanks for your tome treatment of my ideas! I forgot how much I enjoyed reading them. :) >> To dig up an old discussion--I took a look at better support for SRV records >> (using the priority field as backup/non-backup, etc.) a few weeks ago, but >> determined it didn't make sense in

Re: [ANNOUNCE] haproxy-2.2.0

2020-07-08 Thread Willy Tarreau
Hi Luke! On Wed, Jul 08, 2020 at 11:57:15AM +0200, Luke Seelenbinder wrote: > I've been following along the torturous road, and I'm happy to see all the > issues resolved and the excellent results. You can imagine how I am as well :-) > Personally, I'm excited about the > performance gains.

Re: [ANNOUNCE] haproxy-2.2.0

2020-07-08 Thread Luke Seelenbinder
Congrats on the release, Willy & the rest of the team! I've been following along the torturous road, and I'm happy to see all the issues resolved and the excellent results. Personally, I'm excited about the performance gains. I'll deploy this soon on our network. To dig up an old discussion—I

[ANNOUNCE] haproxy-2.2.0

2020-07-07 Thread Willy Tarreau
Hi, HAProxy 2.2.0 was released on 2020/07/07. It added 24 new commits after version 2.2-dev12. There were very few last-minute changes since dev12, just as I hoped, that's pretty fine. We're late by about 1 month compared to the initial planning, which is not terrible and should be seen instead