From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "Schild, Henning" <henning.schild@siemens.com>
Cc: "Bovensiepen, Daniel (bovi)" <daniel.bovensiepen@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH 1/1] fix apt-retry spec used by apt running in rootfs
Date: Sat, 19 Nov 2022 13:14:18 +0000 [thread overview]
Message-ID: <bf672ed46d5a392f10ed8e0e833be3c8237eccd3.camel@siemens.com> (raw)
In-Reply-To: <20221118213520.46248ac7@md1za8fc.ad001.siemens.net>
On Fri, 2022-11-18 at 21:35 +0100, Henning Schild wrote:
> Did not try but LGTM
This is anyways hard to try.
You have to simulate a broken network and then check the logs for
traces. But in CN we quite consistently saw build failures due to
instable connections to local mirrors (or rate-limiting...).
With the fix, everything is running smooth so far.
>
> If that never worked you could include a "Fixes" on the blame to get
> better story telling.
Done. Sent out a v2. Actually the issue was introduced when moving the
apt config from the cli to a file.
Felix
>
> Henning
>
> Am Fri, 18 Nov 2022 10:18:52 +0100
> schrieb Felix Moessbauer <felix.moessbauer@siemens.com>:
>
> > The configuration to let apt retry failed downloads belongs to the
> > 'Acquire' group but not to the 'APT' group of apt.conf.
> > Previously this had been placed in the invalid group and hence did
> > not have any effect.
> >
> > According to the manpage of apt.conf, the new location is at least
> > valid from debian stretch on and from ubuntu bionic on. By that,
> > all distros supported by ISAR are covered. The same configuration
> > entry can also be seen in the debrebuild script in /usr/bin.
> >
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > ---
> > meta/classes/rootfs.bbclass | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/classes/rootfs.bbclass
> > b/meta/classes/rootfs.bbclass
> > index bbb5ac0a..d19ac037 100644
> > --- a/meta/classes/rootfs.bbclass
> > +++ b/meta/classes/rootfs.bbclass
> > @@ -107,7 +107,7 @@ rootfs_configure_apt() {
> >
> > mkdir -p '${ROOTFSDIR}/etc/apt/apt.conf.d'
> > {
> > - echo 'APT::Acquire::Retries "3";'
> > + echo 'Acquire::Retries "3";'
> > echo 'APT::Install-Recommends "0";'
> > echo 'APT::Install-Suggests "0";'
> > } > '${ROOTFSDIR}/etc/apt/apt.conf.d/50isar'
>
prev parent reply other threads:[~2022-11-19 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 9:18 Felix Moessbauer
2022-11-18 20:35 ` Henning Schild
2022-11-19 13:14 ` Moessbauer, Felix [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bf672ed46d5a392f10ed8e0e833be3c8237eccd3.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=daniel.bovensiepen@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox