On Sat, Jan 28, 2023 at 02:28:30PM +0100, Johannes Schauer Marin Rodrigues wrote: >... > Why do people call just accepting that Priority:required packages have to be > part of the buildd chroot the easier solution? We just need to fix debootstrap > bug #837060 and we are done, no?
This is mostly a new problem, a side effect of a different recent change: The efforts to reduce the essential set for enabling smaller installs of Debian. "Priority: required" packages like e2fsprogs and tzdata used to be part of the essential set, tzdata is no longer (transitively) essential since stretch and e2fsprogs no longer essential since buster. It was not an intended goal to remove such packages from the *build* essential set, and they are installed in all reasonable build environments which makes it a non-issue in practice. Adding them to build-essential would just enforce what was enforced differently in the past, and what is still true in practice today. It should at least be discussed first whether packages like tzdata that have been a part of the build essential set should stay there. > Thanks! > > cheers, josch cu Adrian
