On Mon, 25 May 2026 13:51:24 +0100 Richard Lewis
<[email protected]> wrote:
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
The problem here is that by default, sbuild performs apt clean
after the build. Which clears the lists. And with --no-apt-update,
the lists becomes empty, so now apt does not find any package to
install at all, because now it have to re-download the lists.
When --no-apt-update paired with --no-apt-clean, things works as
expected.
It looks like --no-apt-update should imply --no-apt-clean. This
way, everything works, again, as expected.
I'm not sure why we need --apt-clean in the first place? Maybe
get rid of it entirely?
BTW, in man sbuild.conf, it is said that $APT_CLEAN defaults to 0.
But it looks like it is on by default?
Thanks,
/mjt
