Package: sudo Version: 1.9.13p3-1+deb12u1 Severity: wishlist Dear Maintainer,
I use a debian docker container to build Chromium. As of late, the build process has been failing due to the fact that certain new dependencies require user interaction to resolve (selecting keyboard and languages etc). This shows up despite setting the recommended `DEBIAN_FRONTEND=noninteractive` env variable and using the recommended `--no-prompt` flag provided the `./build/install-build-deps.sh` script provided by Chromium. Based on my understanding, the problem here is caused by the fact that sudo by default will reject and reset all env variables before running apt (Chromium's script effectively runs `sudo apt install -y <packages>`). Given this, itt would be great if `DEBIAN_FRONTEND` could be added to sudo's env whitelist for debian so that it could be passed to apt. P.S: I apologize if the configurations attached to this report are non-standard, I am reporting this bug from inside the aforementioned docker container. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.80-1-MANJARO (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages sudo depends on: ii init-system-helpers 1.65.2 ii libaudit1 1:3.0.9-1 ii libc6 2.36-9+deb12u4 ii libpam-modules 1.5.2-6+deb12u1 ii libpam0g 1.5.2-6+deb12u1 ii libselinux1 3.4-1+b6 ii zlib1g 1:1.2.13.dfsg-1 sudo recommends no packages. sudo suggests no packages. -- no debconf information
