Re: [PATCH] sbuild: Don't update apt database on every package build

[Jan Kiszka <jan.kiszka@siemens.com>]

On 24.10.22 15:10, Uladzimir Bely wrote:
> By default, sbuild updates apt database beforethe build. It may cause
> an inconsistency between apt databases for different packages built at
> the different time if external (Debian) mirrors has updated recently.
> 
> With new changes, sbuild will rely on global apt state that was got
> during debootstrap stage.
> 
> Local `isar-apt` repo will still be automatically updated while it is
> passed via `--extra-repository=` argument.

Will that also ensure upgrades, e.g. from essential debian packages to
self-built ones hosted in isar-apt? We had a few of such cases in the
past already in downstream layers, and I recall permitting upgrades to
the old buildchroot for that.

Jan

> 
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
>  meta/classes/dpkg.bbclass | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
> index c92ea7db..a55b5776 100644
> --- a/meta/classes/dpkg.bbclass
> +++ b/meta/classes/dpkg.bbclass
> @@ -90,6 +90,7 @@ dpkg_runbuild() {
>      sbuild -A -n -c ${SBUILD_CHROOT} --extra-repository="${ISAR_APT_REPO}" \
>          --host=${PACKAGE_ARCH} --build=${SBUILD_HOST_ARCH} ${profiles} \
>          --no-run-lintian --no-run-piuparts --no-run-autopkgtest --resolve-alternatives \
> +        --no-apt-update --no-apt-upgrade --no-apt-distupgrade \
>          --chroot-setup-commands="rm -f /var/log/dpkg.log" \
>          --chroot-setup-commands="cp -n --no-preserve=owner ${ext_deb_dir}/*.deb -t ${deb_dir}/ || :" \
>          --finished-build-commands="rm -f ${deb_dir}/sbuild-build-depends-main-dummy_*.deb" \

-- 
Siemens AG, Technology
Competence Center Embedded Linux