From: vijaikumar.kanagarajan@gmail.com
To: isar-users@googlegroups.com
Cc: henning.schild@siemens.com, ibr@radix50.net,
claudius.heine.ext@siemens.com, jan.kiszka@siemens.com,
Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
Subject: [PATCH v2] isar-bootstrap: Clear local apt state information
Date: Thu, 21 Nov 2019 15:35:32 +0530 [thread overview]
Message-ID: <20191121100532.8491-1-Vijaikumar_Kangarajan@mentor.com> (raw)
In-Reply-To: <20191121095401.GA15048@oxygen>
From: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
Debootstrap's second stage switches to using the default debian mirror.
But the apt state information is renamed and used from the first stage.
This might cause apt-get update to fail with the below error when the
sources list contain both custom and upstream repos.
| Reading package lists...
| E: Failed to fetch http://deb.debian.org/debian/dists/stretch/InRelease \
| Unable to find expected entry 'contrib/source/Sources' in Release file \
| (Wrong sources.list entry or malformed file)
Clear the apt state information before apt-get update.
Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
---
Changes in v2:
- Addressed review comments from Henning.
meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
index d614d9a..9096775 100644
--- a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
+++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
@@ -280,6 +280,7 @@ isar_bootstrap() {
install -v -m644 "${APTSRCS_INIT}" \
"${ROOTFSDIR}/etc/apt/sources-list"
rm -f "${ROOTFSDIR}/etc/apt/sources.list"
+ rm -rf "${ROOTFSDIR}/var/lib/apt/lists/"*
mkdir -p "${ROOTFSDIR}/etc/apt/apt.conf.d"
install -v -m644 "${WORKDIR}/isar-apt.conf" \
"${ROOTFSDIR}/etc/apt/apt.conf.d/50isar.conf"
--
2.17.1
next prev parent reply other threads:[~2019-11-21 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 10:53 [PATCH] " vijaikumar.kanagarajan
2019-11-21 9:22 ` Henning Schild
2019-11-21 9:54 ` Vijai Kumar K
2019-11-21 10:05 ` vijaikumar.kanagarajan [this message]
2019-11-25 6:38 ` [PATCH v2] " Jan Kiszka
2019-11-25 6:46 ` Vijai Kumar K
2019-11-25 7:00 ` Jan Kiszka
2019-11-28 15:21 ` Baurzhan Ismagulov
2019-11-21 11:40 ` [PATCH] " Henning Schild
2019-11-21 12:09 ` Vijai Kumar K
2019-11-21 10:01 ` Jan Kiszka
2019-11-21 10:14 ` Vijai Kumar K
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=20191121100532.8491-1-Vijaikumar_Kangarajan@mentor.com \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=Vijaikumar_Kanagarajan@mentor.com \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--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