No support for new Barman state "WAITING_FOR_WALS"

Barman 2.5 added a new state "WAITING_FOR_WALS" which should not block a base sync. However, because this new state is not supported, base backups are skipped. My basesync.log is now full of these entries:

Tue Aug 13 23:05:01 UTC 2019 All done.
INFO: Executing task: /var/run/barmans3/queue.d/20190814T040001.run

+-------------------------------------------------------
START: Wed Aug 14 23:05:01 UTC 2019
WHOAMI: barman
BARMAN_BACKUP_DIR: /mnt/eph0/barman
BARMAN_BACKUP_ID: 20190814T040001
BARMAN_ERROR:
BARMAN_PHASE: post
BARMAN_SERVER: db-server
BARMAN_STATUS: WAITING_FOR_WALS

ERROR: Backup skipped!

Task done.

END: Wed Aug 14 23:05:01 UTC 2019
+-------------------------------------------------------

Here are the contents of the queue file:

sudo cat /var/run/barmans3/queue.d/20190821T040002.run
BARMAN_BACKUP_DIR="/mnt/eph0/barman"
BARMAN_BACKUP_ID="20190821T040002"
BARMAN_ERROR=""
BARMAN_PHASE="post"
BARMAN_SERVER="db-server"
BARMAN_STATUS="WAITING_FOR_WALS"

[mainframe]

Could you please show also cat /var/run/barmans3/queue.d/20190814T040001.run output?

@mainframe Done. Thanks.

[flavioarieta]

Would a simple modification to barmans3-base-sync:52 be enough to allow the base backup without any problems or there is more to it?

[mainframe]

@flavioarieta should be enough.