From: <Mikko.Rapeli@bmw.de>
To: <mark.hatle@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] Fix gitsm networking and mirroring
Date: Fri, 21 Sep 2018 07:02:20 +0000 [thread overview]
Message-ID: <20180921070220.GR9430@hiutale> (raw)
In-Reply-To: <20180921001815.18248-1-mark.hatle@windriver.com>
Looks good from what I understand of the patch, but I have a question about
git/gitsm fetchers:
Is it possible that two recipes end up modifying the same file e.g. via
hard links when they use git submodules and share one of the repositories?
I'm seeing very odd build failures on sumo and it looks like
recipes are either mixing up files in their sysroots or seeing each others
patches on top of the shared git submodule tree. These happen when building
the whole system and rebuilding affected recipes alone makes the problem
go away.
With svn fetcher we see the same, but that's one of the problems we knew about
from past. svn fetcher does not lock the download cached tree correctly
and if multiple recipes use the same repo, one of them can see the repo
in an inconsistent state and fail with various errors. Our workaround
is to switch to http/s fetcher instead.
-Mikko
next prev parent reply other threads:[~2018-09-21 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 0:18 [PATCH] Fix gitsm networking and mirroring Mark Hatle
2018-09-21 0:18 ` [PATCH] fetch2/gitsm.py: Rework the git submodule fetcher Mark Hatle
2018-09-21 7:02 ` Mikko.Rapeli [this message]
2018-09-21 14:04 ` [PATCH] Fix gitsm networking and mirroring Mark Hatle
2018-09-21 14:15 ` Mikko.Rapeli
2018-09-21 15:05 ` Mark Hatle
2018-09-21 15:09 ` Mikko.Rapeli
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=20180921070220.GR9430@hiutale \
--to=mikko.rapeli@bmw.de \
--cc=bitbake-devel@lists.openembedded.org \
--cc=mark.hatle@windriver.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 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.