From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users <isar-users@googlegroups.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: Is schroot updating external apt databases?
Date: Mon, 24 Oct 2022 11:07:15 +0300 [thread overview]
Message-ID: <2078393.9o76ZdvQCi@hp> (raw)
In-Reply-To: <ca16cae0-8747-9b2e-c2ff-3e6e1ca003d6@siemens.com>
In mail from Mondey, 24 Oct 2022 г. 09:26:10 +03 user Jan Kiszka
wrote:
> Hi all,
>
> while meditating over logs for other reasons, I noticed this:
>
> ...
> +---------------------------------------------------------------------------
> ---+
> | Update chroot
> | |
> +---------------------------------------------------------------------------
> ---+
>
> Get:1
> file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-deb
> ian isar InRelease Ign:1
> file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-deb
> ian isar InRelease Get:2
> file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-deb
> ian isar Release [5105 B] Get:2
> file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-deb
> ian isar Release [5105 B] Get:3
> file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-deb
> ian isar Release.gpg Ign:3
> file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-deb
> ian isar Release.gpg Get:4
> file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-deb
> ian isar/main arm64 Packages [18.2 kB] Get:5
> file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-deb
> ian isar/main armhf Packages [4498 B] Get:6
> file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-deb
> ian isar/main amd64 Packages [5638 B] Hit:7 http://deb.debian.org/debian
> bullseye InRelease
> Get:8 http://deb.debian.org/debian-security bullseye-security InRelease
> [48.4 kB] Get:9 http://deb.debian.org/debian bullseye-updates InRelease
> [44.1 kB] Get:10 http://deb.debian.org/debian-security
> bullseye-security/main Sources [166 kB] Get:11
> http://deb.debian.org/debian-security bullseye-security/main armhf Packages
> [191 kB] Get:12 http://deb.debian.org/debian-security
> bullseye-security/main amd64 Packages [193 kB] Get:13
> http://deb.debian.org/debian-security bullseye-security/main arm64 Packages
> [191 kB] Get:14 http://deb.debian.org/debian bullseye-updates/main
> Sources.diff/Index [14.0 kB] Get:15 http://deb.debian.org/debian
> bullseye-updates/main armhf Packages.diff/Index [14.0 kB] Get:16
> http://deb.debian.org/debian bullseye-updates/main arm64
> Packages.diff/Index [14.0 kB] Get:17 http://deb.debian.org/debian
> bullseye-updates/main amd64 Packages.diff/Index [14.0 kB] Get:18
> http://deb.debian.org/debian bullseye-updates/main Sources
> T-2022-10-21-2017.32-F-2022-10-21-2017.32.pdiff [1848 B] Get:18
> http://deb.debian.org/debian bullseye-updates/main Sources
> T-2022-10-21-2017.32-F-2022-10-21-2017.32.pdiff [1848 B] Get:19
> http://deb.debian.org/debian bullseye-updates/main armhf Packages
> T-2022-10-21-2017.32-F-2022-10-21-2017.32.pdiff [9282 B] Get:19
> http://deb.debian.org/debian bullseye-updates/main armhf Packages
> T-2022-10-21-2017.32-F-2022-10-21-2017.32.pdiff [9282 B] Get:20
> http://deb.debian.org/debian bullseye-updates/main arm64 Packages
> T-2022-10-21-2017.32-F-2022-10-21-2017.32.pdiff [9315 B] Get:20
> http://deb.debian.org/debian bullseye-updates/main arm64 Packages
> T-2022-10-21-2017.32-F-2022-10-21-2017.32.pdiff [9315 B] Get:21
> http://deb.debian.org/debian bullseye-updates/main amd64 Packages
> T-2022-10-21-2017.32-F-2022-10-21-2017.32.pdiff [9785 B] Get:21
> http://deb.debian.org/debian bullseye-updates/main amd64 Packages
> T-2022-10-21-2017.32-F-2022-10-21-2017.32.pdiff [9785 B] Fetched 919 kB in
> 5s (169 kB/s)
>
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Calculating upgrade...
> The following packages will be upgraded:
> libc-bin libc-dev-bin libc-l10n libc6 libc6-dev linux-libc-dev locales
> debconf: delaying package configuration, since apt-utils is not installed
> 7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
>
> Are we pulling newer packages from Debian here? This should not
> happen, obviously. What is done to prevent this?
Yes, sbuild by default updates all the sources before package building.
It has options like `--(no-)apt-update`, `--(no-)apt-upgrade` and `--(no-)apt-
distupgrade` and corresponding config options to tune the behaviour.
We most probably should use them, but, at the same time, still somehow update
'isar-apt' part. For example, in `--chroot-setup-commands` stage
>
> Jan
next prev parent reply other threads:[~2022-10-24 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 6:26 Jan Kiszka
2022-10-24 8:07 ` Uladzimir Bely [this message]
2022-10-24 8:18 ` Baurzhan Ismagulov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2078393.9o76ZdvQCi@hp \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox