Re: [PATCH 0/1] Exit bootstrap with error if apt-get update fails

[Anton Mikanovich <amikan@ilbers.de>]

19.10.2022 07:31, Uladzimir Bely wrote:
> Sometimes we have issues with `deb.debian.org` availability. Usually, it
> results in errors in the related tasks that are understandable, e.g.,
> `Could not connect to deb.debian.org:80` and so on.
>
> But if the issue happens while debootstrapping at the `apt-get update`
> stage, it doesn't produce an error and the following tasks fail instead
> with a pretty weird reason (no any errors in the nearest context).
>
> For example, we can get errors in buildchroot-target:
>
> ```
> E: Package 'make' has no installation candidate
> E: Unable to locate package debhelper
> ...
> ```
> The reason is that `actual` error happened in `bootstrap` task, but it
> didn't fail with error code.
>
> Adding `-o APT::Update::Error-Mode=any` (this is an apt configuration
> equivalent of `--error-on=any` option) makes apt fail in such cases
> during the debootstrapping.
>
> Unfortunatelly, proposed solution doesn't work for `stretch` and
> `buster` while they have older apt versions.
>
> Technically, it's possible support these legacy distros, but it will
> require ugly workarounds with redirecting apt-get output, parcing
> it for `^W` messages (warnings) and generating artificial errors. It
> doesn't looks like something that is worth implementing.
>
> Uladzimir Bely (1):
>    Exit bootstrap with error if apt-get update fails
>
>   meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
Applied to next, thanks.