From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7157961463957553152 X-Received: by 2002:a2e:9082:0:b0:276:a8d3:5c8e with SMTP id l2-20020a2e9082000000b00276a8d35c8emr5292412ljg.315.1666598848781; Mon, 24 Oct 2022 01:07:28 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6512:2151:b0:494:6c7d:cf65 with SMTP id s17-20020a056512215100b004946c7dcf65ls430216lfr.2.-pod-prod-gmail; Mon, 24 Oct 2022 01:07:27 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7py6ng2oQEzIdwc8531Rw0NId+HsMlH2kvXk8WUTFZp1GgMD7ZcDzABgfkXLrSziQ89yts X-Received: by 2002:a05:6512:487:b0:4a2:2977:3a83 with SMTP id v7-20020a056512048700b004a229773a83mr11785146lfq.88.1666598847178; Mon, 24 Oct 2022 01:07:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666598847; cv=none; d=google.com; s=arc-20160816; b=k+RrLYxLF7wR+PokvzuSDeCRXOHNBJ+C2nM/4yhAcZEAhx06Rv3wL6OFqYxOepe8O4 xkqYWHM5fZZo9bw53H8iIojPZHWvUvjx65fDXR7a5xU3LEwqlCxN8C9eWeGJWrIgii+b TMjfv8obup3/3JrFipc2+7/pZoTksELuQUwzGeqa7H4sYJ6rR/BvhhwwgbZ0jWcg1kxJ gyT0Nl2oITbFlmrI6zkNscMzxg6RCtqd7PNWGNjnfkA2guG5633bqUcP1vcvatjSVhwC 7iy9+vzwsrAaZ6nqaEtsrrApi71dtoCd5tABKFNv6/pJOkZTXUIr5HfCjENahmJ08Nei By2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=qK6CEtnVHG4i6YWD34hgdLWh1hbVGISFHSgVQBh8X0k=; b=ctlJtpvCkqokAmoaTgj40rxd87SozyokZpkbZM7fteJU/ypGdYBKExSyfgJ9/T9Abd HgHOQ8oZhqbv4uIpUZvNMwQDoSC6Aiy7HJCJDKTBI2s4IR++yTjqWMZtPm0JceLx9G61 Uc+A9LGKAjL3km7Z1WD4zz9kzorJwfIoBEcmqbBZNZkwPKamEYYQSPSuwLNc/kzYc6ZN E/kizOP159UYfOUK3opNQR/l29/0kUpcgAtQUlk6NDd5gHewZV3DjSiaAorNl9+vp7R+ vgQ+Nwa3eXR+aCnBHWitCW5y129jwYqIlk+z2LKyEuaImXS0MTQHp+r4Wt6FAH1ya9qn V1mw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id p9-20020a2eba09000000b0026e8c45cf59si969747lja.8.2022.10.24.01.07.26 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Mon, 24 Oct 2022 01:07:27 -0700 (PDT) Received-SPF: pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Received: from hp.localnet (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPSA id 29O87L2J013147 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 24 Oct 2022 10:07:25 +0200 From: Uladzimir Bely To: isar-users Cc: Jan Kiszka Subject: Re: Is schroot updating external apt databases? Date: Mon, 24 Oct 2022 11:07:15 +0300 Message-ID: <2078393.9o76ZdvQCi@hp> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: wx7iuMMOcZQ5 In mail from Mondey, 24 Oct 2022 =D0=B3. 09:26:10 +03 user Jan Kiszka=20 wrote: > Hi all, >=20 > while meditating over logs for other reasons, I noticed this: >=20 > ... > +------------------------------------------------------------------------= =2D-- > ---+ > | Update chroot = =20 > | | > +------------------------------------------------------------------------= =2D-- > ---+ >=20 > Get:1 > file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-d= eb > ian isar InRelease Ign:1 > file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-d= eb > ian isar InRelease Get:2 > file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-d= eb > ian isar Release [5105 B] Get:2 > file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-d= eb > ian isar Release [5105 B] Get:3 > file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-d= eb > ian isar Release.gpg Ign:3 > file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-d= eb > ian isar Release.gpg Get:4 > file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-d= eb > ian isar/main arm64 Packages [18.2 kB] Get:5 > file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-d= eb > ian isar/main armhf Packages [4498 B] Get:6 > file:/home/builder/k3-rti-wdt/isar-apt/iot2050-debian-arm64/apt/iot2050-d= eb > 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 Packag= es > [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 Packag= es > [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) >=20 > 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. >=20 >=20 > 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-)a= pt- distupgrade` and corresponding config options to tune the behaviour. We most probably should use them, but, at the same time, still somehow upda= te=20 'isar-apt' part. For example, in `--chroot-setup-commands` stage >=20 > Jan