On Fri, Jul 31, 2020 at 02:13:14AM +0500, ??? wrote:
> Hello,
>
> I repaired SLZ build.
>
> it used to work earlier because of SSL_LIB, SSL_INC variables.
Makes sense indeed, applied now, thanks!
Willy
Hi Tim,
On Thu, Jul 30, 2020 at 10:37:15PM +0200, Tim Düsterhus wrote:
> Hi List,
> Willy,
>
> either I am dumb or it appears that the generation of HAProxy 1.9
> snapshots is broken. In
> http://www.haproxy.org/download/1.9/src/snapshot/ the newest tarball is
> from Jun, 12th.
Wow, seems
Hello,
I repaired SLZ build.
it used to work earlier because of SSL_LIB, SSL_INC variables.
чт, 30 июл. 2020 г. в 16:14, Илья Шипицин :
> SLZ also copied lib and headers to ${HOME}/opt
>
>
> I do not want to use SSL_INC, SSL_LIB for SLZ.
> I will send patch tomorrow (or earlier)
>
> чт, 30
Ilya,
Am 29.07.20 um 21:15 schrieb Илья Шипицин:
> as for migrating to GH actions in general, I suggest the following
>
> 1) I will have a look at red builds (I did not expect red LibreSSL builds)
They look like a fluke to me, the test for the field converter failed.
But I did not bother to
Ilya,
Am 30.07.20 um 08:50 schrieb Илья Шипицин:
> as for failing osx builds, I think it might be due to long folder name
>
> https://github.com/TimWolla/haproxy/runs/924097118?check_suite_focus=true#step:10:361
>
> it is 100+ characters. there's also unix socket in that dir, which has
>
On Thu, Jul 30, 2020 at 10:37 PM Julien Pivotto wrote:
> I'm with Lukas on this. 2.1 is a strong release, and we should be
> grateful for everyone which is using that release, as their feedback is
> valuable for the building the next releases of HAProxy.
My apologies if the message sounded
On 30 Jul 21:29, Lukas Tribus wrote:
> Hello,
>
> On Thu, 30 Jul 2020 at 20:49, Valter Jansons wrote:
> >
> > On Thu, Jul 30, 2020 at 6:44 PM Harris Kaufmann
> > wrote:
> > > my company really needs the next 2.1 release but we want to avoid
> > > deploying a custom, self compiled version.
> >
Hello,
On Thu, 30 Jul 2020 at 20:49, Valter Jansons wrote:
>
> On Thu, Jul 30, 2020 at 6:44 PM Harris Kaufmann
> wrote:
> > my company really needs the next 2.1 release but we want to avoid
> > deploying a custom, self compiled version.
> >
> > Is there something I can do to help with the
On Thu, Jul 30, 2020 at 6:44 PM Harris Kaufmann wrote:
> my company really needs the next 2.1 release but we want to avoid
> deploying a custom, self compiled version.
>
> Is there something I can do to help with the release? I guess there
> are no blocking issues left?
For mission-critical
Hi,
my company really needs the next 2.1 release but we want to avoid
deploying a custom, self compiled version.
Is there something I can do to help with the release? I guess there
are no blocking issues left?
Best regards,
Harris
SLZ also copied lib and headers to ${HOME}/opt
I do not want to use SSL_INC, SSL_LIB for SLZ.
I will send patch tomorrow (or earlier)
чт, 30 июл. 2020 г. в 07:48, Willy Tarreau :
> Hi Ilya,
>
> thanks for this. Two minor comments (just let me know, I can adjust
> the patches before merging
On Fri, Jul 17, 2020 at 04:47:10PM +0900, Sehoon Kim wrote:
> Hi,
>
> ssl-skip-self-issued-ca option does not work.
> commit "83cb2cb7" seems to remove this option.
>
>
> Best regards,
> Seri
I suppose you were talking about commit f187ce6.
There is indeed a problem there, because a previous
Tim, let us move this activity to GH issue ?
as for failing osx builds, I think it might be due to long folder name
https://github.com/TimWolla/haproxy/runs/924097118?check_suite_focus=true#step:10:361
it is 100+ characters. there's also unix socket in that dir, which has
limitation on
13 matches
Mail list logo
