On Sat, 25 Apr 2026 17:06:18 +0100 Richard Lewis
<[email protected]> wrote:
> hi, the recent changes to apt-update prevents lintian starting,
>
> I set $apt_update = 0; but now --run-lintian fails with
> Install lintian build dependencies (apt-based resolver)
> ------------------------------------------------------------------------
>
> Installing build dependencies
> Reading package lists...
> E:Building dependency tree...
> Reading state information...
> Unable to locate package sbuild-build-depends-lintian-dummy:amd64
> apt-get failed.
> E: Package installation failed
> Not removing build depends: cloned chroot in use
> ----------------------------------------------------------------
>
> sbuild commit 0a66217d works fine
> sbuild commit f0a66217d fails
oops, apparently i failed to paste the commit ids:
sbuild commit 0a66217d works fine
sbuild commit 1652a2e019b5cd50537f0d77425637ce44c9be44 is the first
that fails
This commit does the following
--- a/lib/Sbuild/ResolverBase.pm
+++ b/lib/Sbuild/ResolverBase.pm
@@ -692,6 +692,11 @@ sub update_archive {
my $apt_update = shift;
if ($apt_update) {
+ if (!$self->get_conf('APT_UPDATE')) {
+ print STDERR "I: skipping apt update as requested\n";
+ return 1;
+ }
+
-- i couldnt work out why this addition was thought to be needed, but
it doesnt seem to be called except for (failing to) run lintian
