mcuboot build is broken

[gmarull]

Describe the bug

mcuboot build is broken with current Zephyr master.

To Reproduce

west build -b nrf52840dk_nrf52840 -d build_bootloader -s ../bootloader/mcuboot/boot/zephyr

Expected behavior

Build succeeds

Impact

mcuboot bootloader can't be built.

Logs and console output

Relevant CMake errors:

error: LOG_MINIMAL (defined at subsys/logging/Kconfig.mode:51) is assigned in a configuration file,
but is not directly user-configurable (has no prompt). It gets its value indirectly from other
symbols. See http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_LOG_MINIMAL.html and/or
look up LOG_MINIMAL in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

Environment (please complete the following information):

• OS: Ubuntu 20.04
• Toolchain: Zephyr SDK 0.11.4
• Commit SHA or Version used: 4720585

Additional context

Reverting #31404 fixes the problem

[henrikbrixandersen]

Reverting #31404 should not be necessary. The MCUboot Zephyr just needs to be updated to use the new Kconfig options.

[gmarull]

@henrikbrixandersen I agree, but until then Zephyr master should be in a working state

[gmarull]

Opened mcu-tools/mcuboot#932

[nandojve]

Question: How is possible MCUboot be broken at master? Are tests running to avoid this?
This is not an exception, I believe, and I would like to see something addressed to avoid this in Future.

[nvlsianpu]

Question: How is possible MCUboot be broken at master? Are tests running to avoid this?
This is not an exception, I believe, and I would like to see something addressed to avoid this in Future.

@nandojve #29397
saw that problem, not fixed so fare