[gnurl] 73/411: CI/azure: MQTT is now enabled by default

[gnunet]

This is an automated email from the git hooks/post-receive script.

nikita pushed a commit to branch master
in repository gnurl.

commit ce56cc8b1118ea7ed0a3c91924224013e1977038
Author: Marc Hoersken <info@marc-hoersken.de>
AuthorDate: Tue Sep 1 19:58:21 2020 +0200

    CI/azure: MQTT is now enabled by default
    
    Reviewed-by: Daniel Stenberg
    
    Follow up to #5858
    Closes #5903
---
 .azure-pipelines.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index 6bab7c506..da833f0df 100644
--- a/.azure-pipelines.yml
+++ b/.azure-pipelines.yml
@@ -117,14 +117,14 @@ stages:
           container_img: mback2k/curl-docker-winbuildenv-msys2-mingw32:ltsc2019
           container_cmd: C:\msys64\usr\bin\sh
           prepare: pacman -S --needed --noconfirm --noprogressbar 
libssh2-devel mingw-w64-i686-libssh2
-          configure: --host=i686-w64-mingw32 --build=i686-w64-mingw32 
--prefix=/mingw32 --enable-debug --enable-werror --enable-mqtt --with-libssh2
+          configure: --host=i686-w64-mingw32 --build=i686-w64-mingw32 
--prefix=/mingw32 --enable-debug --enable-werror --with-libssh2
           tests: ~612 ~1056 ~1299 !SCP
         msys2_mingw64_debug_openssl:
           name: 64-bit OpenSSL and MQTT
           container_img: mback2k/curl-docker-winbuildenv-msys2-mingw64:ltsc2019
           container_cmd: C:\msys64\usr\bin\sh
           prepare: pacman -S --needed --noconfirm --noprogressbar 
libssh2-devel mingw-w64-x86_64-libssh2
-          configure: --host=x86_64-w64-mingw32 --build=x86_64-w64-mingw32 
--prefix=/mingw64 --enable-debug --enable-werror --enable-mqtt --with-libssh2
+          configure: --host=x86_64-w64-mingw32 --build=x86_64-w64-mingw32 
--prefix=/mingw64 --enable-debug --enable-werror --with-libssh2
           tests: ~612 ~1056 ~1299 !SCP
         msys1_mingw_debug_openssl:
           name: 32-bit OpenSSL (legacy)

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.