From: Vijai Kumar K <vijaikumar.kanagarajan@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: vijai kumar <vijaikumar.kanagarajan@gmail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: DISTRO_APT_PREMIRRORS broken?
Date: Fri, 22 Nov 2019 15:04:36 +0530 [thread overview]
Message-ID: <20191122093436.GA26366@oxygen> (raw)
In-Reply-To: <22d60f40-8824-19d6-d94b-18e4a747f47b@siemens.com>
On Fri, Nov 22, 2019 at 09:58:51AM +0100, Jan Kiszka wrote:
> On 22.11.19 09:52, vijai kumar wrote:
> > Hi All,
> >
> >
> > DISTRO_APT_PREMIRRORS has no effect on the final wic image.
> > buildchroot-target/host & isar-bootstrap-target/host has the preferred
> > mirrors as specified in DISTRO_APT_PREMIRRORS but the final image does
> > not seem to have it.
> >
> > Steps to reproduce:
> > Add the following lines to conf/local.conf
> > DISTRO_APT_PREMIRRORS = "http://deb.debian.org/debian
> > http://ftp.debian.org/debian"
> > bitbake mc:qemuamd64-buster:isar-image-base
> >
> >
> > I tested with the v0.7 release and it works there. So indeed broken in
> > the latest master?
> >
> >
> > Github issue link: https://github.com/ilbers/isar/issues/62
> >
>
> I wonder why the local premirror settings, often build system related,
> should end up on the target? If you want different settings for the target,
> change DISTRO_APT_SOURCES, I would say.
>
> Jan
I agree. The way it is now makes more sense.
If thats the case, then I believe we should capture this in documentation.
Thanks,
Vijai Kumar K
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-11-22 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 8:52 vijai kumar
2019-11-22 8:58 ` Jan Kiszka
2019-11-22 9:34 ` Vijai Kumar K [this message]
2019-11-25 5:38 ` [PATCH] user_manual: Make usage of DISTRO_APT_PREMIRRORS clear vijaikumar.kanagarajan
2019-11-25 6:37 ` Jan Kiszka
2019-12-08 15:56 ` Baurzhan Ismagulov
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=20191122093436.GA26366@oxygen \
--to=vijaikumar.kanagarajan@gmail.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