On 8/28/2023 1:25 AM, Alexander Kanavin wrote:
On Mon, 28 Aug 2023 at 08:16, Stephan Mühlstrasser
<stephan.muehlstras...@gmail.com> wrote:
The documentation isn’t perfect. Sometimes it becomes outdated and no one
notices, or it may be inaccurate to begin with. Personally I would never tamper
with content of downloads and preserve it exactly as it is. Doesn’t have to be
git lfs, plain artifact storage options work too.
If it doesn't work as documented, could someone elaborate what is
currently necessary to replicate a build offline? Is it possible to
reproduce a build only with the tarballs or is it actually necessary
to keep the cloned Git repositories in the download directory as well?
It's well possible no one knows the definite answer, and the best
advice is what I said: don't touch the downloads at all. In any case,
if the documentation is not accurate, patches to make it accurate
would be appreciated.
Alex
For the core repositories, few if any use AUTOINC, they almost all
specify the exact has of a git repository, if it is using one. For
rebuilding offline, that works perfectly because you
have a copy of the git tarball or repository in your downloads
direction. However, if you add a repository, as in the case NXP, where
it is using AUTOINC to have a pull from tip of
specific branch recipe, it is required to fetch the current hash for the
branch of that repository just to verify if the hash is in the
downloaded git repository.
When this occurs on releases, we generally take the current value when
we start the build and define the hash value for the recipe, either via
bbappend, or a global override that
sets the value for the recipe, so it does not need to go fetch the
value. That is more or less specifically the error he is running into.
--
Jeremy Puhlman
jpuhl...@mvista.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61817): https://lists.yoctoproject.org/g/yocto/message/61817
Mute This Topic: https://lists.yoctoproject.org/mt/100952497/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
