Hi, On Tue, 07 Apr 2026 at 15:03:42 +0200, Jochen Sprickerhof wrote: > * Guilhem Moulin <[email protected]> [2026-04-07 11:32]: >> `sbuild-update -u` no longer works as before on my system ("skipping apt >> update as requested"). >> >> ~$ sudo sbuild-update -u bullseye-amd64-sbuild >> I: Setting up the chroot... >> bullseye-amd64-sbuild: Performing update. >> I: skipping apt update as requested > > I assume you have > > $apt_update = 0 in your sbuild config.
Yep, as I want to control the update process via explicit `sbuild-update -u` calls. >> It seems it's caused by this commit: >> https://salsa.debian.org/debian/sbuild/-/commit/1652a2e019b5cd50537f0d77425637ce44c9be44 >> >> Setting `$apt_update = 1` fixes this, but I precisely don't want to run >> `apt-get update` at the start of each build. Instead I want to control >> the update process via explicit `sbuild-update -u` calls. Shouldn't the >> `-u` flag override $apt_update? > > Somehow I can't reproduce this but can you check if this fixes your problem? > > https://salsa.debian.org/debian/sbuild/-/merge_requests/229 It does, thanks for the quick fix! I now get $ sbuild-update -u bullseye-amd64-sbuild I: Setting up the chroot... bullseye-amd64-sbuild: Performing update. Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease Reading package lists... Done and the build doesn't trigger `apt-get update` calls, just like it used to be :-) Thanks! -- Guilhem.
signature.asc
Description: PGP signature
