[yocto] [layerindex-web][PATCH 6/6] views: fix classic recipe search redirecting to recipe page with single result

If your classic recipe search returned a single result, then since commit c8c25fb641c500354cf36c3c59abb6f9fe96d223 you got a standard recipe page instead of the proper page with fields you can edit. To fix it, just drop the redirection functionality from the classic recipe search, since we don't

[yocto] [layerindex-web][PATCH 5/6] views: fix "layer:" keyword on recipe search page

We were using the layerbranch id to search for the specified layer, which is most likely to return either no results or results for the wrong layer. We can also avoid specifying the id field at all here as the filter() function can handle real objects. Signed-off-by: Paul Eggleton

[yocto] [layerindex-web][PATCH 4/6] update: don't stop on unsatisfied layer dependencies

Unsatisfied layer dependencies shouldn't error out of the script - broken metadata isn't supposed to terminate the index update process. Signed-off-by: Paul Eggleton --- layerindex/update.py | 20 ++-- 1 file changed, 10 insertions(+), 10

[yocto] [layerindex-web][PATCH 2/6] Explicitly handle too-long field values

If you use a traditional database engine (such as MySQL/MariaDB) then maximum character field lengths are enforced, however depending on the configuration this may result in an exception rather than a warning and truncation and will also break the per-layer transaction. To avoid that ugliness, add

[yocto] [layerindex-web][PATCH 3/6] Fix error on publish if no non-root superuser/staff accounts exist

We need to set a default for this variable or you get an UnboundLocalError if no non-root superuser/staff accounts are set up in the database. Signed-off-by: Paul Eggleton --- layerindex/views.py | 1 + 1 file changed, 1 insertion(+) diff --git

[yocto] [layerindex-web][PATCH 0/6] Various fixes

Fix a bunch of issues I found recently working on the layer index. I plan on merging these almost immediately as we need several of these fixes in the live instance on openembedded.org. The following changes since commit fa0b01082fb0596959841e95af8c516ae3f267a7: admin: fix dependency display

[yocto] [layerindex-web][PATCH 1/6] update_layer: fix handling of database errors

If a database error occurs when we save a recipe (e.g. because a database-level constraint is voilated) it will mess up the transaction. Unfortunately that means we need to break out of updating the entire layer rather than catching the error, because if we do catch it we just get errors on every

Re: [yocto] Layer index not updated

On Tuesday, 9 January 2018 1:14:05 AM NZDT Andreas Müller wrote: > > Ping? Still broken (sorry about that!) but Michael and I will be working together on it tomorrow. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto

[linux-yocto] [yocto-4.12][PATCH 3/3] x86/intel_rdt: Turn off most RDT features on Skylake

From: Tony Luck commit d56593eb5eda8f593db92927059697bbf89bc4b3 upstream Errata list is included in this document: https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/6th-gen-x-series-spec-update.pdf with more details in:

[linux-yocto] [yocto-4.12][PATCH 2/3] x86/intel_rdt: Add command line options for resource director technology

From: Tony Luck commit 1d9807fc64c131a83a96917f2b2da1c9b00cf127 upstream Command line options allow us to ignore features that we don't want. Also we can re-enable options that have been disabled on a platform (so long as the underlying h/w actually supports the option). [

[yocto] backporting u-boot fit changes and how to properly capture the changes in yocto

Hello, I'm running yocto Krogoth and I had to backport some updates related to u-boot FIT from the latest yocto version into my version of yocto. The changes are located in: *poky/meta/classes/kernel-fitimage.bbclass* I'd much prefer to put these changes into my own layer so that these changes

Re: [yocto] Kernel configuration problem/confusion

Hi Greg, I'm back at things now, and will fire up a build! Bruce On 2018-01-04 11:39 AM, Greg Wilson-Lindberg wrote: Hi Bruce, Yes I'm still having problems with this. I've attached both my bblayers and local configuration files. Thanks for your help. Regards, Greg

[yocto] Yocto Project Status WW02’18

Current Dev Position: YP 2.5 M2 development Next Deadline: YP 2.5 M2 cut off of 1/15/18 SWAT team rotation: Cal -> Joshua on Jan. 5, 2018. SWAT team rotation: Joshua -> Armin on Jan. 12, 2018. https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: ·

Re: [yocto] running autoreconf during a configuration step

On 04/01/18 20:39, Rail Shafigulin wrote: > Ross, > > Thanks for the help. Really appreciate it. > There is also already a recipe for libsoc in meta-oe. http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/libsoc/libsoc_0.8.2.bb?h=master Regards, Jack. > On Thu, Jan 4,

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 01/08/2018 02:31 PM, Martin Hundebøll wrote: On 2018-01-08 13:19, Alexander Kanavin wrote: The problem is that in Yocto 2.4 then any build which requires on-target postinstallation script is going to trigger warning, even if it is completely correct. Is there no way around this? Is there a

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 2018-01-08 13:19, Alexander Kanavin wrote: The problem is that in Yocto 2.4 then any build which requires on-target postinstallation script is going to trigger warning, even if it is completely correct. Is there no way around this? Is there a way to at least hide them? You can set

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 01/08/2018 01:44 PM, Diaz de Grenu, Jose wrote: Thanks for the information. I guess this fix will be for Yocto 2.5? Maybe; I'm working right now on the patchset, and will post it to oe-core list later today. Last time it was a bit controversial, so I'd appreciate if you a) try and test it;

Re: [yocto] Layer index not updated

On Mon, Nov 20, 2017 at 9:12 PM, Paul Eggleton < paul.eggle...@linux.intel.com> wrote: > On Friday, 10 November 2017 8:32:36 AM NZDT Paul Eggleton wrote: > > On Thursday, 9 November 2017 9:36:26 PM NZDT Andreas Müller wrote: > > > did not find any heads up here so: Layer index stopped updating

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

-Original Message- From: Alexander Kanavin [mailto:alexander.kana...@linux.intel.com] On 01/08/2018 11:14 AM, Diaz de Grenu, Jose wrote: > Nope, 'exit 1' is the currently correct way to defer to first boot. On the > other hand, it's also a correct way to indicate that the script has

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 01/08/2018 11:14 AM, Diaz de Grenu, Jose wrote: I am trying to create a recipe with a post installation script. I am using the following fragment of code (as documented in http://www.yoctoproject.org/docs/2.4/mega-manual/mega-manual.html#new-recipe-post-installation-scripts ):

Re: [yocto] [PATCH] beaglebone: Fix serial console device node

Hi Marek, On 2018-01-07 17:16, Marek Vasut wrote: The serial console on BBB is on /dev/ttyS0 , not /dev/ttyO0 . This changed again, so fix this. Signed-off-by: Marek Vasut Cc: Joshua Lock Cc: Richard Purdie ---

[yocto] [PATCH] beaglebone: Fix serial console device node

The serial console on BBB is on /dev/ttyS0 , not /dev/ttyO0 . This changed again, so fix this. Signed-off-by: Marek Vasut Cc: Joshua Lock Cc: Richard Purdie --- meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +-

Re: [yocto] Smart Project Manager

Yeah, indeed, the manufacturer of the boards officially provides BSP only for 2.0-based releases. That sucks, but that's how it works. At least they're not gonna make BSP individually for our needs :) Actually smartpm covers the things I need. That's sad to know that it's abandoned. 2018-01-05

Re: [yocto] Smart Project Manager

Thanks for advice, but at the moment it's a bit of a problem, I'm stuck with poky2.0.3 bound to a specific board, so I will keep up with smart. But what's the benefit of dnf? 2018-01-05 16:02 GMT+01:00 Alexander Kanavin < alexander.kana...@linux.intel.com>: > On 12/28/2017 01:37 PM, Kirill

[yocto] yocto-2.5_M1.rc3 failed at runqemu for x86

Hi Joshua, I noticed for 2.5 M1 rc3, nightly-x86 failed during testimage (Sanity Test), due to runqemu error. Is this expected? Shall QA move on to initialize the QA for this rc3? Thank you very much for your attention and help! Thanks, Yeoh Ee Peng

[yocto] Release Candidate Build for yocto-2.5_M1.rc3 now available.

A release candidate build for yocto-2.5_M1.rc3 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.5_M1.rc3 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 1580913674bc84c8e6c10cf855dbf38d2ee8f3d2 meta-qt4 :

[yocto] Postinstallation script warnings in Yocto 2.4 Rocko

Hi, I posted this question in the poky mailing list, but I realize now that this may be the correct place for it. Sorry for reposting. I am trying to create a recipe with a post installation script. I am using the following fragment of code (as documented in