firmware/driver-policy recipes: fix dangling 'driver-manager-config' dep

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>
This commit is contained in:
2026-07-28 16:01:23 +09:00
parent 9487c3bef7
commit e2f27778e6
5 changed files with 5 additions and 5 deletions
@@ -7,7 +7,7 @@ path = "source"
[build]
template = "custom"
dependencies = ["driver-manager-config"]
dependencies = ["driver-manager"]
script = """
set -eo pipefail
@@ -9,7 +9,7 @@ upstream = "https://gitlab.com/kernel-firmware/linux-firmware.git"
[build]
template = "custom"
dependencies = ["driver-manager-config"]
dependencies = ["driver-manager"]
script = """
set -eo pipefail
@@ -9,7 +9,7 @@ upstream = "https://gitlab.com/kernel-firmware/linux-firmware.git"
[build]
template = "custom"
dependencies = ["driver-manager-config"]
dependencies = ["driver-manager"]
script = """
set -eo pipefail
@@ -9,7 +9,7 @@ upstream = "https://gitlab.com/kernel-firmware/linux-firmware.git"
[build]
template = "custom"
dependencies = ["driver-manager-config"]
dependencies = ["driver-manager"]
script = """
set -eo pipefail
@@ -9,7 +9,7 @@ upstream = "https://gitlab.com/kernel-firmware/linux-firmware.git"
[build]
template = "custom"
dependencies = ["driver-manager-config"]
dependencies = ["driver-manager"]
script = """
set -eo pipefail