From: Anton Mikanovich <amikan@ilbers.de>
To: henning.schild@siemens.com, isar-users@googlegroups.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Srinuvasan A <srinuvasan_a@mentor.com>,
vijai kumar <vijaikumar.kanagarajan@gmail.com>
Subject: Re: [PATCH 0/4] apt configuration fixes
Date: Mon, 21 Feb 2022 12:24:09 +0300 [thread overview]
Message-ID: <784ec8bc-c5cb-1094-b4b3-6fee9bfcac6d@ilbers.de> (raw)
In-Reply-To: <20220205151528.9199-1-henning.schild@siemens.com>
5.02.22 18:15, henning.schild@siemens.com wrote:
> This attempts to solve the apt fetch retry problem in a better way. On
> the way it was found that bootstrap leaves a file around, which probably
> should not remain in images.
>
> Henning Schild (4):
> rootfs: configure apt to always retry downloads
> Revert "deb-dl-dir: Retry downloads 3 times for src files"
> Revert "rootfs: Retry downloads 3 times"
> bootstrap: do not leave 50isar.conf in final rootfss
>
> meta/classes/deb-dl-dir.bbclass | 2 +-
> meta/classes/image.bbclass | 1 +
> meta/classes/rootfs.bbclass | 18 +++++++++++++++++-
> .../isar-bootstrap/files/isar-apt.conf | 2 --
> .../isar-bootstrap/isar-bootstrap.inc | 5 +----
> 5 files changed, 20 insertions(+), 8 deletions(-)
> delete mode 100644 meta/recipes-core/isar-bootstrap/files/isar-apt.conf
>
Applied to next, thanks.
next prev parent reply other threads:[~2022-02-21 9:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 15:15 henning.schild
2022-02-05 15:15 ` [PATCH 1/4] rootfs: configure apt to always retry downloads henning.schild
2022-02-05 15:15 ` [PATCH 2/4] Revert "deb-dl-dir: Retry downloads 3 times for src files" henning.schild
2022-02-05 15:15 ` [PATCH 3/4] Revert "rootfs: Retry downloads 3 times" henning.schild
2022-02-05 15:15 ` [PATCH 4/4] bootstrap: do not leave 50isar.conf in final rootfss henning.schild
2022-02-05 15:18 ` [PATCH 0/4] apt configuration fixes Henning Schild
2022-02-21 9:24 ` Anton Mikanovich [this message]
2022-02-21 16:12 ` Henning Schild
2022-02-21 16:51 ` Baurzhan Ismagulov
2022-02-21 18:24 ` Henning Schild
2022-02-21 19:20 ` Jan Kiszka
2022-02-21 20:30 ` Henning Schild
2022-02-22 9:01 ` Bezdeka, Florian
2022-02-22 9:06 ` Jan Kiszka
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=784ec8bc-c5cb-1094-b4b3-6fee9bfcac6d@ilbers.de \
--to=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=srinuvasan_a@mentor.com \
--cc=vijaikumar.kanagarajan@gmail.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