All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jasper Orschulko <Jasper.Orschulko@iris-sensing.com>
To: "richard.purdie@linuxfoundation.org"
	<richard.purdie@linuxfoundation.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"kweihmann@outlook.com" <kweihmann@outlook.com>,
	"peter.kjellerstedt@axis.com" <peter.kjellerstedt@axis.com>,
	"jasper@fancydomain.eu" <jasper@fancydomain.eu>
Cc: "martin@mko.dev" <martin@mko.dev>,
	Daniel Baumgart <Daniel.Baumgart@iris-sensing.com>,
	"bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
Date: Thu, 11 Nov 2021 15:08:28 +0000	[thread overview]
Message-ID: <699b2927411dbdfdfd01e64ffb16dc057d5bb320.camel@iris-sensing.com> (raw)
In-Reply-To: <64e41080db7642d0b54818bdcf916dac@axis.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Peter,

during this initial fetch it is true, that the repo fetcher has to
download the repo sources from googlesource.com. But during this first
fetch the fetcher also needs to download any sources listed in the repo
manifest anyway, so internet access is a given.

Consequential fetches will only re-run repo if:
a) the SRC_URI or SRCREV has changed within the recipe
b) the SRCREV is set to AUTOREV

Both cases do not apply when reproducing a build offline.

So if you have done this initial fetch of your sources and stash your
working dir away, you can do an offline build.

- -- 

With best regards

Jasper Orschulko
DevOps Engineer

Tel. +49 30 58 58 14 265
Fax +49 30 58 58 14 999
Jasper.Orschulko@iris-sensing.com

• • • • • • • • • • • • • • • • • • • • • • • • • •

iris-GmbH
infrared & intelligent sensors
Schnellerstraße 1-5 | 12439 Berlin

https://iris-sensing.com/





On Thu, 2021-11-11 at 14:11 +0000, Peter Kjellerstedt wrote:
> > -----Original Message-----
> > From: Jasper Orschulko <Jasper.Orschulko@iris-sensing.com>
> > Sent: den 11 november 2021 13:10
> > To: richard.purdie@linuxfoundation.org; openembedded-
> > core@lists.openembedded.org; kweihmann@outlook.com; Peter
> > Kjellerstedt
> > <peter.kjellerstedt@axis.com>; jasper@fancydomain.eu
> > Cc: martin@mko.dev; Daniel Baumgart
> > <Daniel.Baumgart@iris-sensing.com>;
> > bitbake-devel@lists.openembedded.org
> > Subject: Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial
> > recipe
> > for repo 2.17.3
> > 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> > 
> > Hi Peter,
> > 
> > > However, this means
> > > that only the source for the repo wrapper is available in DL_DIR.
> > > So
> > > when the repo wrapper executes it will try to go on the Internet
> > > to
> > > fetch the rest of the repo source, which will fail.
> > 
> > just to clearify: Are we talking about installing repo on a target,
> > or
> > are we talking about the repo fetcher?
> 
> The repo fetcher, i.e., when repo is used by bitbake.
> 
> > When installing repo on the target, we do not call any "repo"
> > command
> > within the bitbake build process. We just clone the git repo
> > containing
> > the wrapper script and install the wrapper script into the sysroot.
> > At
> > that point the bitbake build process is finished and the user ends
> > up
> > with just the wrapper script on his device. Just as he would when
> > installing repo from the system repositories on debian, arch, etc.
> > 
> > When using the fetcher, the repo sources are fetched during the
> > initial
> > do_fetch (this also works with `bitbake --runonly=do_fetch`) and
> > placed
> > into the DL_DIR (in the .repo folder, next to the sources as
> > described
> > in the repo manifest). So unless the user changes something fetcher
> > related in the recipe or deletes his DL_DIR, he can use this build
> > environment for an offline build.
> 
> How can it work? The repo source, which is fetched by the repo
> wrapper, 
> will not be in DL_DIR or handled by bitbake at all. This means the 
> repo wrapper will try to contact googlesource.com directly and fetch
> it 
> when it is run by bitbake, which cannot work since the host is 
> disconnected from the network. How or from where would it be able to 
> get the sources it needs?
> 
> > You can try this for yourself, if you like:
> > 
> > 1) clone https://github.com/Jasper-Ben/demo-kas
> > 2) (with docker and docker-compose installed) run `make offline-
> > build`
> > 
> > - --
> > With best regards
> > 
> > Jasper Orschulko
> > DevOps Engineer
> > 
> > Tel. +49 30 58 58 14 265
> > Fax +49 30 58 58 14 999
> > Jasper.Orschulko@iris-sensing.com
> > 
> > • • • • • • • • • • • • • • • • • • • • • • • • • •
> > 
> > iris-GmbH
> > infrared & intelligent sensors
> > Schnellerstraße 1-5 | 12439 Berlin
> > 
> > https://iris-sensing.com/
> 
> //Peter
> 
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE4WyPMIC5Ap4+Ooo1Ygqew07VMNUFAmGNMesACgkQYgqew07V
MNU//Af+IFFqmbtV/k3SscMUWYRNDpnSeK6elwfpwnDi84tQHjRo66Xtrzi12D+H
zzya3H87unVY3BWqWnQIE3K4aShquz+p9tQA7zuzlARImCyqAsDQzKddD7hhK7AI
4toNobOqNoJZ2D1kJQyu7o7VsnvbiyvYz8Z8l+t4FF35+bwU26aE0iCFF63toZSi
GLvmTzLigYNAu9UUW+UgSUAhHVsaCyOolnGwBdHEJW3NliCZEOLDf8omDygG3xDp
UOKcX2Q238sGN2fCwAeS2ABC4ffMNDfrpzAS0Q1qy2WVmheWmmtGoaksW2z3sDZk
FKxLlRWNQvPWOy/tY2JLyB1QNyedyg==
=c20l
-----END PGP SIGNATURE-----

  reply	other threads:[~2021-11-11 15:08 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 13:31 [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3 Jasper Orschulko
2021-11-05 13:31 ` [oe-core][PATCH 2/2] base.bbclass: Add sysroot deps for repo fetcher Jasper Orschulko
2021-11-05 13:35 ` [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3 Konrad Weihmann
2021-11-05 13:47   ` Jasper Orschulko
2021-11-05 14:09     ` Jasper Orschulko
2021-11-05 14:20       ` Konrad Weihmann
2021-11-05 14:53         ` Jasper Orschulko
2021-11-05 15:34         ` Jasper Orschulko
2021-11-06  9:43       ` Richard Purdie
2021-11-09 11:26         ` Jasper Orschulko
2021-11-10 12:46           ` Richard Purdie
2021-11-10 13:52             ` Jasper Orschulko
2021-11-10 16:33               ` Richard Purdie
2021-11-11 11:42                 ` Jasper Orschulko
2021-11-24 16:04                   ` Jasper Orschulko
2021-11-10 23:55           ` Peter Kjellerstedt
2021-11-11 10:04             ` Jasper Orschulko
2021-11-11 11:34               ` Peter Kjellerstedt
2021-11-11 12:10                 ` Jasper Orschulko
2021-11-11 14:11                   ` Peter Kjellerstedt
2021-11-11 15:08                     ` Jasper Orschulko [this message]
2021-11-11 19:20                       ` Alexander Kanavin
2021-11-12 12:22                         ` Jasper Orschulko
2021-11-15 12:59                         ` Jasper Orschulko
2021-11-15 13:05                           ` Alexander Kanavin
2021-11-15 13:12                             ` Jasper Orschulko
2021-11-05 14:20 ` Alexander Kanavin
2021-11-05 15:04   ` Alexander Kanavin
2021-11-05 15:24   ` Jasper Orschulko
2021-11-05 17:46     ` Alexander Kanavin
2021-11-05 18:05       ` Jasper Orschulko
2021-11-05 18:45         ` Alexander Kanavin
2021-11-05 20:32           ` Jasper Orschulko
2021-11-06  6:39             ` Alexander Kanavin
2021-11-07  9:05 ` Richard Purdie
2021-11-08 11:55   ` Jasper Orschulko
2021-11-08 12:48     ` Fwd: " Richard Purdie
2021-11-09  9:29       ` [docs] " Quentin Schulz
2021-11-09 10:40       ` Fwd: " Michael Opdenacker
2021-11-10  8:47         ` Michael Opdenacker
2021-11-11 10:49           ` Richard Purdie

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=699b2927411dbdfdfd01e64ffb16dc057d5bb320.camel@iris-sensing.com \
    --to=jasper.orschulko@iris-sensing.com \
    --cc=Daniel.Baumgart@iris-sensing.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=jasper@fancydomain.eu \
    --cc=kweihmann@outlook.com \
    --cc=martin@mko.dev \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    --cc=richard.purdie@linuxfoundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.