From: Trevor Woerner <twoerner@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi] Current master broken
Date: Tue, 6 Dec 2016 16:32:24 -0500 [thread overview]
Message-ID: <20161206213224.GA22102@openSUSE-i7.site> (raw)
In-Reply-To: <19a9d76a-2c15-551a-2fce-55d8b8cfe1d0@mlbassoc.com>
Just to clarify, in the last couple days, there have been *two* major issues
that have independently broken raspi builds:
1) the rebase of the raspi kernel repository at
git://github.com/raspberrypi/linux.git
2) a bug in a recent commit to oe-core's kernel tools
Andrei pushed patches today to update the src revs so, as of this moment, the
SRC_URIs in meta-raspberrypi should be valid.
A patch for the kernel tools in oe-core is on the mailing list; hopefully it
will be pushed to master soon. Incidentally, this same bad commit also
included a second bug that made it impossible for two different users on the
same machine to perform OE builds. The fix addresses both issues.
prev parent reply other threads:[~2016-12-06 21:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 7:33 [meta-raspberrypi] Current master broken Gary Thomas
2016-12-03 14:16 ` Paul Barker
2016-12-05 0:54 ` Andrei Gherzan
2016-12-05 6:03 ` Gary Thomas
2016-12-05 16:50 ` Khem Raj
2016-12-06 15:29 ` Andrei Gherzan
2016-12-06 18:04 ` ***SPAM*** " Herve Jourdain
2016-12-06 18:11 ` Andrei Gherzan
2016-12-06 21:21 ` Herve Jourdain
2016-12-06 23:00 ` Paul Barker
2016-12-07 2:17 ` Trevor Woerner
2016-12-07 7:25 ` Paul Barker
2016-12-07 7:42 ` Paul Barker
2016-12-07 10:54 ` Andreas Müller
2016-12-06 22:50 ` Paul Barker
2016-12-07 15:19 ` Andrea Galbusera
2016-12-07 15:23 ` Andrei Gherzan
2016-12-03 20:18 ` Herve Jourdain
2016-12-06 21:32 ` Trevor Woerner [this message]
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=20161206213224.GA22102@openSUSE-i7.site \
--to=twoerner@gmail.com \
--cc=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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.