From 1f832f4209dbde6a5b9beb107a2affbeb8e1d2bb Mon Sep 17 00:00:00 2001 From: oxmc Date: Sat, 15 Aug 2026 05:31:22 -0700 Subject: [PATCH] manifest: drop external/update_binary, duplicates bootable/deprecated-ota This AOSP release didn't actually delete applypatch/edify/updater -- it relocated them, still Soong-converted, to bootable/deprecated-ota/. Syncing external_update_binary alongside it produced a hard Soong module-name collision (identical module names, several with matching line numbers -- external_update_binary appears to be a near-verbatim copy). Nothing currently wires either copy's modules into PRODUCT_PACKAGES, so dropping the duplicate is a pure fix. --- common/pawletos.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/common/pawletos.xml b/common/pawletos.xml index b468713..da179e5 100644 --- a/common/pawletos.xml +++ b/common/pawletos.xml @@ -13,8 +13,14 @@ - + vendor/pawlet below, no separate project needed). See NOTES-ota-recovery-ab.md. + + external/update_binary (PawletOS/external_update_binary) is NOT synced: it duplicates + applypatch/edify/updater, which this AOSP release already ships, Soong-converted, at + bootable/deprecated-ota/, confirmed by a hard Soong module-name collision the one time + both were synced together. Nothing in PawletOS currently references either copy's + modules from PRODUCT_PACKAGES; when non-A/B OTA wiring actually happens, point it at + bootable/deprecated-ota's existing modules instead of reviving this project. -->