public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Vijai Kumar K <vijaikumar.kanagarajan@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: vijaikumar.kanagarajan@gmail.com, isar-users@googlegroups.com,
	henning.schild@siemens.com, ibr@radix50.net
Subject: Re: [PATCH v2] isar-bootstrap: Clear local apt state information
Date: Mon, 25 Nov 2019 12:16:07 +0530	[thread overview]
Message-ID: <20191125064607.GA13796@oxygen> (raw)
In-Reply-To: <bf146bd1-ab41-a690-d800-42358ee59f35@siemens.com>

On Mon, Nov 25, 2019 at 07:38:18AM +0100, Jan Kiszka wrote:
> On 21.11.19 11:05, vijaikumar.kanagarajan@gmail.com wrote:
> > 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/"*
> 
> Normally, you would put the wildcard inside the quotes.
> 
> Jan

Unfortunately file globbing doesnot work under quotes. Another alternative is to use quotes only around
the variable as "${ROOTFSDIR}"/var/lib/apt/lists/*

Thanks,
Vijai Kumar K

> 
> >               mkdir -p "${ROOTFSDIR}/etc/apt/apt.conf.d"
> >               install -v -m644 "${WORKDIR}/isar-apt.conf" \
> >                                "${ROOTFSDIR}/etc/apt/apt.conf.d/50isar.conf"
> > 
> 
> -- 
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux

  reply	other threads:[~2019-11-25  6:46 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     ` [PATCH v2] " vijaikumar.kanagarajan
2019-11-25  6:38       ` Jan Kiszka
2019-11-25  6:46         ` Vijai Kumar K [this message]
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=20191125064607.GA13796@oxygen \
    --to=vijaikumar.kanagarajan@gmail.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