My local linux-yocto-4.4 branch was at that commit ID, and after doing a
git fetch and git status I see the following:
[clsulliv@clsulliv linux-yocto-4.4]$ git st
On branch standard/intel/base
Your branch and 'origin/standard/intel/base' have diverged,
and have 1327 and 325 different commits each, respectively.
(use "git pull" to merge the remote branch into yours)
So something definitely seems wrong.
Now, to add some confusion to the problem, when I build using upstream
meta-intel, it has no issue building with those commit IDs. Even wiping
out my build directory (and thus getting rid of tmp, sstate, and
downloads) it still fetches and builds successfully.
---
Cal
On 10/03/2016 12:38 PM, Patrick Ohly wrote:
On Mon, 2016-10-03 at 12:30 -0700, Saul Wold wrote:
On Mon, 2016-10-03 at 14:42 -0400, Bruce Ashfield wrote:
On Mon, Oct 3, 2016 at 1:07 PM, Cal Sullivan <california.l.sullivan@i
ntel.com> wrote:
+ Bruce
I also can't find that revision on the remote branch...
There were some fixups lately, but yah, I don't see that revision
either. One of the
rebase branches was force updated for those cleanups, but not
standard/intel/base.
So it's not certain yet how this happened? I think it would be
worthwhile to investigate, to ensure that similar mistakes won't happen
again.
Either way, I sent a pull request late last night that has the
revisions I've been testing
so they should work.
Does that bring back 94e5bb30ea onto the standard/intel/base branch?
The problem is that the current and existing Ostro Project is using the
hash in question and so missing it from the existing 4.4 will cause
issues for them.
Not just Ostro - unless I miss something, anyone using the current
meta-intel will be unable to build the 4.4 kernel from upstream sources.
--
_______________________________________________
meta-intel mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-intel
