Quoting Ansgar (2023-01-28 14:41:31) > Johannes Schauer Marin Rodrigues writes: > > I think the much more interesting question is in what environment we want to > > build our packages in. Currently, on buildds, we build them in a chroot that > > has Priority:required and build-essential because of (what I think is) a bug in > > debootstrap: #837060 > > I would rather say: The build-essential packages are those installed by > debootstrap's buildd profile. At least that seems to be current practice > for a long time. Do you agree that the software in our archive should agree on which packages are needed to build a source package? Currently, they do not. dose3 requires only Essential:yes and build-essential being installed. Who is buggy? If you think that dose3 is buggy, who is writing the dose3 patch? Is it not easier to just fix debootstrap so that debootstraps buildd profile does the same thing as most other pieces of software resolving build dependencies in the archive? I know of no other build dependency resolving software in Debian that considers Priority:required packages to be required for building source packages other than debootstrap. Do you? > > So there are two ways forward: > > > > 1. accept that Priority:required is needed for building source packages > > > > - adapt Debian policy accordingly > > AFAIU it would not need changes? Policy doesn't seem to explicitly state > what packages are actually build-essential... I'm not sure. But I also find the policy question less interesting. I find it more interesting to first agree how the final solution should look like and then change policy accordingly (if needed). > > - revert the changes to packages made due to Santiago's bugs - change > > all tools that do build dependency resolution to now also consider > > Priority:required packages > > Why would they need changes? Do they explicitly include essential > packages too? Of course they do not do so explicitly, because all Essential:yes packages are dependencies (and build dependencies) of all packages already *implicitly*. > > 2. make sure that packages are built without Priority:required packages > > > To me it seems that we nearly are already at (2). > > I think we are already at (1) given everything works already? Aha. Try running "apt-get build-dep" on a system without tzdata nor e2fsprogs and witness how apt will not install tzdata nor e2fsprogs. The only reason this usually works right now is because debootstrap installs Priority:required by default in all situations including the buildd variant. My proposal is to fix debootstrap #837060 (patch is in the bug report) so that it only installs Essential:yes, build-essential and apt and discuss if it makes sense to have packages like tzdata or e2fsprogs in a buildd chroot or not and if yes, add those packages as dependencies of the build-essential package. I do not propose to do this before bookworm release. Thanks! cheers, josch
Attachment:
signature.asc
Description: signature