Re : haproxy.com : New ways to improve your google Rankings.

[Ashley Benson]

Hello *haproxy.com  *,



One of the main goals of any business owner is the consistent growth of
their business. Through careful strategic planning, quality marketing
campaigns and a healthy website are likely to increase steadily.



For every Internet-based business, website speed, security, and
infrastructure are important foundations of not only logistics but also
SEO. These aspects of online business translate to better search engine
visibility, resulting in more traffic, leads, brand credibility and
sales. Speeding up your *haproxy.com  * is crucial for
successful online business.



As a business owner, you need to know where your consumers are. But what
if consumers know your business and what you can offer, but they can’t
reach you? That is one of the risks you take by not having a popular
*haproxy.com
*  for your business.



*$149: * Complete package for technical issue fixing + 2 months promotion
service with *top page ranking guarantee*



If this is something you are looking for, I don't see a reason for
otherwise, then don't hesitate to contact me.



or else you can get in touch with us any time over phone or email to get a
customized plan with the suggestions according to your requirements.





I look forward to hearing from you.



Best Regards,



*Ashley  Benson,*

SEO Specialist

--

*P.S:* Our pricing for fixing the issues would *cost $149(one time).*


[image: beacon]

[PATCH v3] MINOR: build: add aix72-gcc build TARGET and power{8,9} CPUs

[Chris]

Hi Илья,

I agree! I just made a new patch which adds the missing documentation
for the new build-TARGET as well as the two new CPU-types.

thanks,
Chris

On Tue, Feb 11, 2020 at 8:29 PM Илья Шипицин  wrote:
>
> there's AIX related build guide
>
> https://github.com/haproxy/haproxy/blob/master/INSTALL#L512-L517
>
> maybe it should be updated as well
>
> пн, 10 февр. 2020 г. в 16:45, Chris :
>>
>> Hi Willy,
>>
>> thanks a lot for your input and sorry for the delay. Work is pretty
>> rough right now...
>>
>> > Thank you for doing this work. I'm having a few questions below.
>> Sure, I am glad I can help :).
>>
>> > > +# AIX 7.2 and above
>> > > +ifeq ($(TARGET),aix72-gcc)
>> > > +  set_target_defaults = $(call default_opts, \
>> > > +USE_POLL USE_THREAD USE_LIBCRYPT USE_OBSOLETE_LINKER
>> > > USE_GETADDRINFO USE_TFO)
>> >
>> > Are you really really sure about USE_TFO ? I suspect you might have
>> > accidently borrowed it from another line. It stands for TCP FastOpen
>> > and is really not broadly deployed, I was only aware of Linux and
>> > FreeBSD, but there are likely a few other ones. And the fact that it
>> > looks OK is possibly just that it's causing a different TCP socket
>> > option to be set on the connection, so if you're not certain we'd
>> > rather avoid it.
>> I think you are right. I kept USE_TFO in there because it neither
>> introduced any build-issues nor did it cause any runtime issues.
>> However, it probably does nothing and should be removed as long as we
>> are not certain it is actually beneficial. I will have a look at the
>> corresponding AIX internals later at some point.
>>
>> > > src/hlua.c: In function 'hlua_panic_ljmp':
>> > > src/hlua.c:128:1: warning: no return statement in function returning
>> > > non-void [-Wreturn-type]
>> > >  static int hlua_panic_ljmp(lua_State *L) { longjmp(safe_ljmp_env, 1); }
>> > >  ^~
>> >
>> > Don't worry about this one, I'll handle it. I suspect that on linux
>> > platforms the longjmp() function prototype is decorated with
>> > __attribute__((noreturn)) which makes the compiler happy, but that's
>> > likely not the case on any system not relying on a gcc-compatible
>> > compiler by default.
>> Thanks for handling this one. If there is something I shoult test
>> please let me know.
>>
>> > Just two small extra requests :
>> >   - please rebase it on top of the development branch. If you really
>> > need it in 2.1, just indicate it. Given that it's well isolated,
>> > I'm fine with having it backported.
>> >
>> >   - please have a look at CONTRIBUTING to get guidance to write a
>> > subject and a commit message. It doesn't need to be very long
>> > but at least indicating what options you chosed to enable/disable
>> > and on what system you tested it will be enough if we need to
>> > reconsider parts of it later.
>> I already made a new patch based on the current development-HEAD and
>> tried to follow all the guidelines from CONTRIBUTING. I would love to
>> have it backported to 2.1 as the patch is pretty much identical and
>> should not cause any regressions. The patch will follow shortly!
>>
>> > Do you have a permanent and durable access to this machine, with the
>> > ability to occasionally re-run a build test in case we ask you (likely
>> > no more than 2-3 times a year in the worst case) ? I'm asking because
>> > I'm still keeping a very old IBM server running 5.2 on a Power3 just
>> > for the sake of revalidating new releases once in a while. Given that
>> > I could not upgrade it to latest OpenSSL, it cannot even be used to
>> > provide complete binaries to those needing them, so it's getting very
>> > obsolete and knowing that there's a better solution somewhere would
>> > allow me to get rid of it.
>> Well, I am not the primary administrator of this machine. However, I
>> have permanent access and no problem doing the occasional build on it.
>> I will have a chat with the server admin in regards to the longtime
>> prospects of this server and report back to you.
>>
>> > thanks!
>> > Willy
>> You are welcome - I am happy I can contribute!
>>
>> thanks,
>> Christian
>>
>> On Thu, Feb 6, 2020 at 3:36 PM Willy Tarreau  wrote:
>> >
>> > Hello Christian,
>> >
>> > On Mon, Feb 03, 2020 at 12:09:46PM +0100, Chris wrote:
>> > > Hello everybody,
>> > >
>> > > I spent some time making haproxy compile and run successfully on AIX
>> > > 7.2 using GCC 8.3 and wanted to contribute my patch in the hope that
>> > > it could be merged. The patch is based on the current haproxy 2.1 head
>> > > revision. I can make one for the development branch too - but it
>> > > should be basically identical.
>> >
>> > Thank you for doing this work. I'm having a few questions below.
>> >
>> > > +# AIX 7.2 and above
>> > > +ifeq ($(TARGET),aix72-gcc)
>> > > +  set_target_defaults = $(call default_opts, \
>> > > +USE_POLL USE_THREAD USE_LIBCRYPT USE_OBSOLETE_LINKER
>> > > USE_GETADDRINFO USE_TFO)
>> >
>> > Are you really really sure 

Bid Writing Workshops

[NFP Workshops]

NFP WORKSHOPS
Affordable Training Courses For Charities And Public Sector Organisations 




This email has been sent to haproxy@formilux.org
CLICK TO UNSUBSCRIBE FROM LIST
Alternatively send a blank e-mail to unsubscr...@nfpmail1902.co.uk quoting 
haproxy@formilux.org in the subject line. 
Unsubscribe requests will take effect within seven days at the latest. 
CLICK TO MAKE A SPAM COMPLAINT




Bid Writing: The Basics 

START 09.00 FINISH 11.30

COST £95.00

TOPICS COVERED

Do you know the most common reasons for rejection? Are you gathering the right 
evidence? Are you making the right arguments? Are you using the right 
terminology? Are your numbers right? Are you learning from rejections? Are you 
assembling the right documents? Do you know how to create a clear and concise 
standard funding bid?

Are you communicating with people or just excluding them? Do you know your own 
organisation well enough? Are you thinking through your projects carefully 
enough? Do you know enough about your competitors? Are you answering the 
questions funders will ask themselves about your application? Are you 
submitting applications correctly?

ATTENDEES

Staff members, volunteers, trustees or board members of charities, schools or 
public sector organisations who intend to submit grant funding applications to 
charitable grant making trusts and foundations. People who provide advice to 
these organisations are also welcome.

TRAVEL INFORMATION

All our venues are within walking distance of major railway stations. None of 
our venues have on site car parking but commercial car parks are available 
within walking distance. The booking pages have links to maps, travel and car 
parking information.

BOOKING DETAILS

£95 including booking fees. Refreshments provided. Attendees receive full notes 
and sample bids by e-mail after the workshop. The workshop consists of talk, 
questions and answers. There are no power points or audio visuals used. All 
places must be booked through the online booking system using a debit or credit 
card. We do not issue invoices or accept bank or cheque payments. If you do not 
have a debit card from your organisation please use a personal one and claim 
reimbursement using the booking confirmation e-mail as proof of purchase.

BOOKING TERMS

 Workshop bookings are non cancellable, non refundable and non transferable 
between dates unless the event is cancelled. If you are unable to attend on the 
date booked you may send someone else in your place. There is no need to 
contact us to let us know that there will be a different attendee. Events may 
occasionally be cancelled due to insufficient bookings, illness, travel 
difficulties or venue problems in which case refunds will be made. The 
organisers do not accept any liability for travel or accommodation costs 
relating to cancelled events. If you wish to make travel or accommodation 
bookings relating to an event you are welcome to contact us regarding the level 
of bookings currently held for that event.

QUESTIONS

If you have a question please e-mail questi...@nfpmail1902.co.uk You will 
usually receive a response within 24 hours. Due to our training and travel 
commitments we are unable to accept questions by phone. 
Bid Writing: Advanced 

START 12.00 FINISH 14.30

COST £95.00

TOPICS COVERED

Are you applying to the right trusts? Are you applying to enough trusts? Are 
you asking for the right amount of money? Are you applying in the right ways? 
Are your projects the most fundable projects? Are you carrying out trust 
fundraising in a professional way? Are you delegating enough work?

Are you highly productive or just very busy? Are you looking for trusts in all 
the right places? How do you compare with your competitors for funding? Is the 
rest of your fundraising hampering your bids to trusts? Do you understand what 
trusts are ideally looking for?

ATTENDEES

Staff members, volunteers, trustees or board members of charities, schools or 
public sector organisations who intend to submit grant funding applications to 
charitable grant making trusts and foundations. People who provide advice to 
these organisations are also welcome. Around half of all attendees do both 
Basics and Advanced workshops on the same day but there is no discount for 
doing so.

TRAVEL INFORMATION

All our venues are within walking distance of major railway stations. None of 
our venues have on site car parking but commercial car parks are available 
within walking distance. The booking pages have links to maps, travel and car 
parking information.

BOOKING DETAILS

£95 including booking fees. Refreshments provided. Attendees receive full notes 
and sample bids by e-mail after the workshop. The workshop consists of talk, 
questions and answers. There are no power points or audio visuals used. All 
places must be booked through the online booking system using a debit or credit 
card. We do not issue invoices or accept bank or cheque payments. If you do not 

Re: [PATCH] AIX 7.2 support

[Илья Шипицин]

there's AIX related build guide

https://github.com/haproxy/haproxy/blob/master/INSTALL#L512-L517

maybe it should be updated as well

пн, 10 февр. 2020 г. в 16:45, Chris :

> Hi Willy,
>
> thanks a lot for your input and sorry for the delay. Work is pretty
> rough right now...
>
> > Thank you for doing this work. I'm having a few questions below.
> Sure, I am glad I can help :).
>
> > > +# AIX 7.2 and above
> > > +ifeq ($(TARGET),aix72-gcc)
> > > +  set_target_defaults = $(call default_opts, \
> > > +USE_POLL USE_THREAD USE_LIBCRYPT USE_OBSOLETE_LINKER
> > > USE_GETADDRINFO USE_TFO)
> >
> > Are you really really sure about USE_TFO ? I suspect you might have
> > accidently borrowed it from another line. It stands for TCP FastOpen
> > and is really not broadly deployed, I was only aware of Linux and
> > FreeBSD, but there are likely a few other ones. And the fact that it
> > looks OK is possibly just that it's causing a different TCP socket
> > option to be set on the connection, so if you're not certain we'd
> > rather avoid it.
> I think you are right. I kept USE_TFO in there because it neither
> introduced any build-issues nor did it cause any runtime issues.
> However, it probably does nothing and should be removed as long as we
> are not certain it is actually beneficial. I will have a look at the
> corresponding AIX internals later at some point.
>
> > > src/hlua.c: In function 'hlua_panic_ljmp':
> > > src/hlua.c:128:1: warning: no return statement in function returning
> > > non-void [-Wreturn-type]
> > >  static int hlua_panic_ljmp(lua_State *L) { longjmp(safe_ljmp_env, 1);
> }
> > >  ^~
> >
> > Don't worry about this one, I'll handle it. I suspect that on linux
> > platforms the longjmp() function prototype is decorated with
> > __attribute__((noreturn)) which makes the compiler happy, but that's
> > likely not the case on any system not relying on a gcc-compatible
> > compiler by default.
> Thanks for handling this one. If there is something I shoult test
> please let me know.
>
> > Just two small extra requests :
> >   - please rebase it on top of the development branch. If you really
> > need it in 2.1, just indicate it. Given that it's well isolated,
> > I'm fine with having it backported.
> >
> >   - please have a look at CONTRIBUTING to get guidance to write a
> > subject and a commit message. It doesn't need to be very long
> > but at least indicating what options you chosed to enable/disable
> > and on what system you tested it will be enough if we need to
> > reconsider parts of it later.
> I already made a new patch based on the current development-HEAD and
> tried to follow all the guidelines from CONTRIBUTING. I would love to
> have it backported to 2.1 as the patch is pretty much identical and
> should not cause any regressions. The patch will follow shortly!
>
> > Do you have a permanent and durable access to this machine, with the
> > ability to occasionally re-run a build test in case we ask you (likely
> > no more than 2-3 times a year in the worst case) ? I'm asking because
> > I'm still keeping a very old IBM server running 5.2 on a Power3 just
> > for the sake of revalidating new releases once in a while. Given that
> > I could not upgrade it to latest OpenSSL, it cannot even be used to
> > provide complete binaries to those needing them, so it's getting very
> > obsolete and knowing that there's a better solution somewhere would
> > allow me to get rid of it.
> Well, I am not the primary administrator of this machine. However, I
> have permanent access and no problem doing the occasional build on it.
> I will have a chat with the server admin in regards to the longtime
> prospects of this server and report back to you.
>
> > thanks!
> > Willy
> You are welcome - I am happy I can contribute!
>
> thanks,
> Christian
>
> On Thu, Feb 6, 2020 at 3:36 PM Willy Tarreau  wrote:
> >
> > Hello Christian,
> >
> > On Mon, Feb 03, 2020 at 12:09:46PM +0100, Chris wrote:
> > > Hello everybody,
> > >
> > > I spent some time making haproxy compile and run successfully on AIX
> > > 7.2 using GCC 8.3 and wanted to contribute my patch in the hope that
> > > it could be merged. The patch is based on the current haproxy 2.1 head
> > > revision. I can make one for the development branch too - but it
> > > should be basically identical.
> >
> > Thank you for doing this work. I'm having a few questions below.
> >
> > > +# AIX 7.2 and above
> > > +ifeq ($(TARGET),aix72-gcc)
> > > +  set_target_defaults = $(call default_opts, \
> > > +USE_POLL USE_THREAD USE_LIBCRYPT USE_OBSOLETE_LINKER
> > > USE_GETADDRINFO USE_TFO)
> >
> > Are you really really sure about USE_TFO ? I suspect you might have
> > accidently borrowed it from another line. It stands for TCP FastOpen
> > and is really not broadly deployed, I was only aware of Linux and
> > FreeBSD, but there are likely a few other ones. And the fact that it
> > looks OK is possibly just that it's causing a different TCP 

Re: spoa-mirror

[Aleksandar Lazic]

Hi Dmitry.

On 11.02.20 15:29, Дмитрий Меркулов wrote:

Good day!
Could you help with the setup spoa-mirror v1.2.1?
SPOE: [mirroragent]  sid=0 st=0 0/0/0/0/0 
1/1 0/0 0/1
I see the backend sends data to the agent, but the agent does not broadcast 
anything to the destination server.
I run the agent with the following command
spoa-mirror --runtime 0 -u http://***.***.***.**:*/  --logfile 
W:/var/log/haproxy-mirror.log -n 1 -i 2s -b 30
Sometimes in the log I get the following error:
[ 1][  110.567823]   <7:10> (E) Failed to send frame length: Broken pipe
I would be very grateful for your help.


Which version of haproxy do you use?
haproxy -vv

What's your haproxy config?
Do you have any logs from haproxy?

Please don't send Screenshots because they are not visible in text only 
mailers, thanks.


--
Dmitry Merkulov


Regards
Aleks

spoa-mirror

[Дмитрий Меркулов]

>Good day!
>Could you help with the setup spoa-mirror v1.2.1?
> 
>SPOE: [mirroragent]  sid=0 st=0 0/0/0/0/0 1/1 
>0/0 0/1
>I see the backend sends data to the agent, but the agent does not broadcast 
>anything to the destination server.
> 
>I run the agent with the following command
>spoa-mirror --runtime 0 -u  http://***.***.***.**:*/  --logfile 
>W:/var/log/haproxy-mirror.log -n 1 -i 2s -b 30
> 
>Sometimes in the log I get the following error:
>[ 1][  110.567823]   <7:10> (E) Failed to send frame length: Broken pipe
> 
> 
>I would be very grateful for your help.
>--
>Dmitry Merkulov 
 
   
 

[PATCH] travis-ci: remove "allow failures", add ERR=1, modernize build-ssl.sh script

[Илья Шипицин]

Hello,

I split patch into separate patches.

cheers,
Ilya Shipitcin
From 17b0b5fae3afe6df42e938073ccf8d7a2105fbb7 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin 
Date: Tue, 11 Feb 2020 14:29:41 +0500
Subject: [PATCH 1/3] BUILD: travis-ci: no more allowed failures for
 openssl-1.0.2

since 23fb037 (which fixes #429) no need to allow failures
on openssl-1.0.2
---
 .travis.yml | 6 --
 1 file changed, 6 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index a82c27327..1cce8db88 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -92,12 +92,6 @@ matrix:
 before_script:
   - git clone http://git.1wt.eu/git/libslz.git/
   - cd libslz && make && make PREFIX=${HOME}/opt install && cd ..
-  allow_failures:
-  - os: linux
-arch: ppc64le
-if: type == cron
-compiler: gcc
-env: TARGET=linux-glibc OPENSSL_VERSION=1.0.2u
 
 install:
   - git clone https://github.com/VTest/VTest.git ../vtest
-- 
2.24.1

From 80803044ad103fe3815f88eb4174c55914b5ac71 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin 
Date: Tue, 11 Feb 2020 14:31:13 +0500
Subject: [PATCH 2/3] BUILD: travis-ci: harden builds, add ERR=1 (warning ought
 to be errors)

---
 .travis.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.travis.yml b/.travis.yml
index 1cce8db88..fd136c980 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -102,7 +102,7 @@ install:
 script:
   - if [ "$CC"  = "clang" ]; then export FLAGS="$FLAGS USE_OBSOLETE_LINKER=1" DEBUG_CFLAGS="-g -fsanitize=address" LDFLAGS="-fsanitize=address"; fi
   - make -C contrib/wurfl
-  - make -j3 CC=$CC V=1 TARGET=$TARGET $FLAGS DEBUG_CFLAGS="$DEBUG_CFLAGS" LDFLAGS="$LDFLAGS -L$SSL_LIB -Wl,-rpath,$SSL_LIB" 51DEGREES_SRC="$FIFTYONEDEGREES_SRC" EXTRA_OBJS="$EXTRA_OBJS"
+  - make -j3 CC=$CC V=1 ERR=1 TARGET=$TARGET $FLAGS DEBUG_CFLAGS="$DEBUG_CFLAGS" LDFLAGS="$LDFLAGS -L$SSL_LIB -Wl,-rpath,$SSL_LIB" 51DEGREES_SRC="$FIFTYONEDEGREES_SRC" EXTRA_OBJS="$EXTRA_OBJS"
   - ./haproxy -vv
   - if [ "${TRAVIS_OS_NAME}" = "linux" ]; then ldd haproxy; fi
   - if [ "${TRAVIS_OS_NAME}" = "osx" ]; then otool -L haproxy; fi
-- 
2.24.1

From f850c0b44c52681ea94f0e42da2f0acf9baa3826 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin 
Date: Tue, 11 Feb 2020 14:36:23 +0500
Subject: [PATCH 3/3] BUILD: scripts/build-ssl.sh: use "uname" instead of
 ${TRAVIS_OS_NAME}

it is also useful for local builds, when ${TRAVIS_OS_NAME} is not set
---
 scripts/build-ssl.sh | 13 -
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/scripts/build-ssl.sh b/scripts/build-ssl.sh
index 384438a22..60b876c5d 100755
--- a/scripts/build-ssl.sh
+++ b/scripts/build-ssl.sh
@@ -28,11 +28,14 @@ build_openssl_osx () {
 build_openssl () {
 if [ "$(cat ${HOME}/opt/.openssl-version)" != "${OPENSSL_VERSION}" ]; then
 tar zxf "download-cache/openssl-${OPENSSL_VERSION}.tar.gz"
-if [ "${TRAVIS_OS_NAME}" = "osx" ]; then
-build_openssl_osx
-elif [ "${TRAVIS_OS_NAME}" = "linux" ]; then
-build_openssl_linux
-fi
+	case `uname` in
+		'Darwin')
+			build_openssl_osx
+			;;
+		'Linux')
+			build_openssl_linux
+			;;
+	esac
 echo "${OPENSSL_VERSION}" > "${HOME}/opt/.openssl-version"
 fi
 }
-- 
2.24.1

Re: [PATCH] add workaround to cirrus-ci

[Willy Tarreau]

On Tue, Feb 11, 2020 at 01:22:05PM +0500,  ??? wrote:
> Hello,
> 
> here's patch split into 3 patches.

All applied now, thanks Ilya.

Willy

Re: [PATCH] add workaround to cirrus-ci

[Илья Шипицин]

Hello,

here's patch split into 3 patches.

вт, 11 февр. 2020 г. в 12:17, Willy Tarreau :

> On Tue, Feb 11, 2020 at 12:14:47PM +0500,  ??? wrote:
> > I will send patch series soon.
> Thank you!
> willy
>
From e47087ecaea0aa32475593afbf460dc0cf72c1f9 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin 
Date: Tue, 11 Feb 2020 13:20:32 +0500
Subject: [PATCH 3/3] cirrus-ci: add ERR=1 to freebsd builds

---
 .cirrus.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.cirrus.yml b/.cirrus.yml
index 5c7c8403d..1a07c80c7 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -10,7 +10,7 @@ FreeBSD_task:
   script:
 - git clone https://github.com/VTest/VTest.git ../vtest
 - make -C ../vtest
-- gmake CC=clang V=1 TARGET=freebsd USE_ZLIB=1 USE_PCRE=1 USE_OPENSSL=1 USE_LUA=1 LUA_INC=/usr/local/include/lua53 LUA_LIB=/usr/local/lib LUA_LIB_NAME=lua-5.3
+- gmake CC=clang V=1 ERR=1 TARGET=freebsd USE_ZLIB=1 USE_PCRE=1 USE_OPENSSL=1 USE_LUA=1 LUA_INC=/usr/local/include/lua53 LUA_LIB=/usr/local/lib LUA_LIB_NAME=lua-5.3
 - ./haproxy -vv
 - ldd haproxy
 - env VTEST_PROGRAM=../vtest/vtest gmake reg-tests || (for folder in /tmp/*regtest*/vtc.*; do cat $folder/INFO $folder/LOG; done && exit 1)
-- 
2.24.1

From 6d44d41d01fe150316b9ae9e7ba296464ad45393 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin 
Date: Tue, 11 Feb 2020 13:19:22 +0500
Subject: [PATCH 2/3] cirrus-ci: workaround "pkg install" bug

there's a bug https://github.com/freebsd/pkg/issues/902
adding "pkg update -f && pkg upgrade -y" is workaround.
---
 .cirrus.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.cirrus.yml b/.cirrus.yml
index d52808358..5c7c8403d 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -6,7 +6,7 @@ FreeBSD_task:
   image_family: freebsd-11-3-snap
   only_if: $CIRRUS_BRANCH =~ 'master|next'
   install_script:
-- pkg install -y openssl git gmake lua53 socat
+- pkg update -f && pkg upgrade -y && pkg install -y openssl git gmake lua53 socat
   script:
 - git clone https://github.com/VTest/VTest.git ../vtest
 - make -C ../vtest
-- 
2.24.1

From 84a013d8f6c1dfe4977e2d5c21887c4ede3230ae Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin 
Date: Tue, 11 Feb 2020 13:16:02 +0500
Subject: [PATCH 1/3] cirrus-ci: switch to "snap" images to unify openssl
 naming

"snap" images are updated frequently, while regular images are updated quarterly.
so, mixing "snap" and regular images lead to package naming mismatch, which will occur every
quarter. we cannot use 11.3 release image, it is broken, so we have to use 11.3 "snap" image.
Thus let us use all "snap" images. 13-snap is first introduced with this commit.
---
 .cirrus.yml | 11 +++
 1 file changed, 3 insertions(+), 8 deletions(-)

diff --git a/.cirrus.yml b/.cirrus.yml
index 4143e687b..d52808358 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -1,17 +1,12 @@
 FreeBSD_task:
   freebsd_instance:
 matrix:
-  image_family: freebsd-12-1
+  image_family: freebsd-13-0-snap
+  image_family: freebsd-12-1-snap
   image_family: freebsd-11-3-snap
   only_if: $CIRRUS_BRANCH =~ 'master|next'
   install_script:
-- case `uname -r` in
-11.3*)
-  export SSL=openssl;;
-12.1*)
-  export SSL=openssl111;;
-  esac
-- pkg install -y $SSL git gmake lua53 socat
+- pkg install -y openssl git gmake lua53 socat
   script:
 - git clone https://github.com/VTest/VTest.git ../vtest
 - make -C ../vtest
-- 
2.24.1

Re: [PATCH v2] MINOR: build: add aix72-gcc build TARGET and power{8,9} CPUs

[Chris]

Hi Willy,

I am really sorry - it feel like I fell into every newby trap. I
attached the proposed patch to this mail. Also, I will never use Gmail
to send patches again.

Thank you for your patience,
Chris

On Tue, Feb 11, 2020 at 8:07 AM Willy Tarreau  wrote:
>
> On Mon, Feb 10, 2020 at 01:19:38PM +0100, Chris wrote:
> > Hello,
> >
> > this is the reworked patch - rebased on the current development-HEAD
> > and formatted according to CONTRIBUTIONS.
>
> Thank you Chris. That's perfect, except for one thing, which is that
> your mailer mangled it by wrapping some long lines and changing tabs
> for spaces. I tried a few minutes to fix it by hand but failed and
> gave up. Please re-send it as an attachment then, it should work fine.
>
> Thanks,
> Willy


0001-MINOR-build-add-aix72-gcc-build-TARGET-and-power-8-9.patch
Description: Binary data