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] isar-bootstrap: Clear local apt state information
Date: Thu, 21 Nov 2019 15:44:15 +0530	[thread overview]
Message-ID: <20191121101415.GA8610@oxygen> (raw)
In-Reply-To: <ed6a0a83-7189-d260-2df1-e7b0378ccd76@siemens.com>

On Thu, Nov 21, 2019 at 11:01:31AM +0100, Jan Kiszka wrote:
> On 20.11.19 11:53, 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.
> 
> I had problems the other day with bootstrapping behind our proxy when there
> was both a local and the upstream repo involved:
> 
> Reading package lists...
> 
> 
> 
> E: Repository 'http://cdn-fastly.deb.debian.org/debian buster InRelease'
> changed its 'Origin' value from '' to 'Debian'
> 
> 
> E: Repository 'http://cdn-fastly.deb.debian.org/debian buster InRelease'
> changed its 'Label' value from '' to 'Debian'
> 
> 
> E: Repository 'http://cdn-fastly.deb.debian.org/debian buster InRelease'
> changed its 'Suite' value from '' to 'stable'
> 
> 
> 
> Would that be resolved by your patch as well? Can reproduce ATM, that's why
> I'm asking.

Possibily. But, I am not sure. You could give it a try.

Thanks,
Vijai Kumar K

> 
> Jan
> 
> > 
> > Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
> > ---
> >   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..5a379f7 100644
> > --- a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> > +++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> > @@ -320,6 +320,7 @@ isar_bootstrap() {
> >                   chroot "${ROOTFSDIR}" /usr/bin/dpkg --add-architecture ${DISTRO_ARCH}
> >               fi
> > +            rm -rf "${ROOTFSDIR}/var/lib/apt/lists/"*
> >               chroot "${ROOTFSDIR}" /usr/bin/apt-get update -y
> >               chroot "${ROOTFSDIR}" /usr/bin/apt-get install -y -f
> >               chroot "${ROOTFSDIR}" /usr/bin/apt-get dist-upgrade -y \
> > 
> 
> 
> -- 
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
> 
> -- 
> You received this message because you are subscribed to the Google Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/ed6a0a83-7189-d260-2df1-e7b0378ccd76%40siemens.com.

      reply	other threads:[~2019-11-21 10:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 10:53 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
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 [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=20191121101415.GA8610@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