Configure step fails when trying to build FTL on development branch

Hello,

I was reading Thank You for Being Part of the V6 Beta! which tells us to switch to the development branch. As you all know, I am compiling FTL myself since I am running pi-hole on an unsupported platform.
On the new development branch, the cmake .. step fails with the following:

root@pogo01:~/FTL/cmake# cmake ..
-- The C compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Building FTL with readline support: YES
-- Embedded LUA will use readline for history: YES
-- Configuring done
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
LIBIDN
    linked by target "pihole-FTL" in directory /root/FTL/src

-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.

This step does not fail on development-v6:

root@pogo01:~/FTL/cmake# cmake ..
-- The C compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Compiling dynamically linked executable
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Building FTL with readline support: YES
-- Building FTL with TLS support: YES
-- Configuring done
-- Generating done
-- Build files have been written to: /root/FTL/cmake

Thank you for looking into this.

This is an easy one, simply run git pull


The long(er) story:

libidn has been used by Pi-hole until v5.x and is replaced by libidn2 starting from v6.0 on. Your already previously existing local (!) development branch has just not been updated since development-v6 was merged into it two days ago. This won't be an issue for any newly cloned repositories.

Oh my god, I feel so stupid. Sorry for this ... simply forgot to pull. Thanks! It's working now.