This became a problem today, probably after the weekly chroot rebuild:

    E: Unable to locate package dpkg-checkbuilddeps:
    E: Unable to locate package error:
    E: Unable to locate package unmet
    E: Unable to locate package build
    E: Unable to locate package dependencies:

That's due to the following commit on the dpkg side:

    commit 04e4a8129e62a058951f53ff5c349071bab96c95
    Author: Guillem Jover <guil...@debian.org>
    Date:   Fri Dec 13 04:13:15 2024 +0100

        dpkg-checkbuilddeps: Improve unmet dependency error messages

        Lower case them to conform to the overall project error messages style,
        and expand the error for build conflicts to also mention these are
        unmet.

Therefore, accept both variants (unmet and Unmet).

Link: 
https://salsa.debian.org/dpkg-team/dpkg/-/commit/04e4a8129e62a058951f53ff5c349071bab96c95

Signed-off-by: Cyril Brulebois <k...@debian.org>
---
 buildscript | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/buildscript b/buildscript
index 4d5d47d..387d9f7 100755
--- a/buildscript
+++ b/buildscript
@@ -60,7 +60,7 @@ install_build_deps() {
   dd-schroot-cmd -c "$SID" apt-get update
   (
     LANG=C schroot -q -c "$SID" -d "$HOME/di/build/$(basename 
"$INSTALLER_DIR")/checkout/build" -p -r -- dpkg-checkbuilddeps -B 
../debian/control 2>&1 || true
-  ) | sed -e 's%dpkg-checkbuilddeps: \(error: \)*Unmet build dependencies: %%' 
-e 's, *([^)]*),,g' \
+  ) | sed -e 's%dpkg-checkbuilddeps: \(error: \)*[uU]nmet build dependencies: 
%%' -e 's, *([^)]*),,g' \
     | DEBIAN_PRIORITY=critical DEBIAN_FRONTEND=noninteractive xargs 
dd-schroot-cmd -c "$SID" -y apt-get install
 }
 
-- 
2.39.5

Reply via email to