The 4 redbear-firmware-* recipes and redbear-driver-policy declared
[build] dependencies = ["driver-manager-config"], but no such package/recipe
exists anywhere -> repo cook aborts with 'Package driver-manager-config not
found' before building the image. The real driver-infrastructure package is
'driver-manager' (a cargo recipe, present in every config). The '-config' name
was planned but never created; the dep is only an ordering gate (these scripts
stage firmware blobs / policy TOMLs and don't consume config files at build
time). Redirected the dep to the existing 'driver-manager' package.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
vasilito
e2f27778e6