Re: [yocto] Where to add U-Boot argements bootargs and bootcmd?

[JH]

Hi Gabriele,

Thank you for your kind explanations and links, that's great helpful.
Will dig further to learn more.

Cheers.

- jh

On 7/16/19, Gabriele Zampieri  wrote:
> Hi JH,
>
> wks is the extension used by wic to generate different kind of flashable
> (partitioned) images. I never used it, but looking around (
> https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#command-bootloader
> ) I see two relevant arguments:
>
>- *--append *
>- *--configfile*
>
> Check them in the link above.
>
> Here is an example for --append:
> https://github.com/openembedded/openembedded-core/blob/master/scripts/lib/wic/canned-wks/directdisk-multi-rootfs.wks#L22
>
> Digging a bit deeper it seems that you cannot feed a custom config to uboot
> via wic (and again, correct me if I'm wrong), but only for extlinux (see:
> https://github.com/openembedded/openembedded-core/blob/master/scripts/lib/wic/plugins/source/bootimg-partition.py#L110
> )
>
> I do not have time to replicate your environment, so I'm just giving you
> suggestions.
>
> Best regards,
> Gabriele
>
> Il giorno lun 15 lug 2019 alle ore 14:45 JH  ha
> scritto:
>
>> Thanks Gabriele and Maciej, I use meta-freescale for imx6. The u-boot
>> argements seem defined in wks files such as imx-uboot-mxs.wks,
>> imx-uboot-bootpart.wks, not quite sure how to extend or overwrite it.
>> Sorry still learning the Yocto.
>>
>> Thank you.
>>
>> Kind regards,
>>
>> - jh
>>
>> On 7/15/19, Gabriele Zampieri  wrote:
>> > Yes, thanks Maciej for pointing that out! It may be a good starting
>> > point
>> > for JH.
>> >
>> > Gabriele
>> >
>> > Il giorno lun 15 lug 2019 alle ore 10:29 Maciej Pijanowski <
>> > maciej.pijanow...@3mdeb.com> ha scritto:
>> >
>> >>
>> >> On 15.07.2019 08:45, Gabriele Zampieri wrote:
>> >>
>> >> Hi,
>> >>
>> >> as far as I know, there is no mechanism to add custom bootargs and/or
>> >> bootcmd to uboot via Yocto (correct me if I'm wrong). I usually patch
>> the
>> >> upstream uboot to achieve this task.
>> >>
>> >> I also haven't heard of any standardized way. It may depend on the
>> target
>> >> hardware
>> >> and the BSP layer you are using. Apart from patching the U-Boot, there
>> >> also might
>> >> be boot.cmd script to modify or the config.txt in case of the RPI, for
>> >> example.
>> >>
>> >>
>> >> Best regards,
>> >> Gabriele
>> >>
>> >> Il giorno lun 8 lug 2019 alle ore 22:43 JH  ha
>> >> scritto:
>> >>
>> >>> Hi,
>> >>>
>> >>> Which Yocto files and which statement can I add my own U-Boot
>> >>> bootargs
>> >>> and bootcmd?
>> >>>
>> >>> Thank you.
>> >>>
>> >>> - jupiter
>> >>> --
>> >>> ___
>> >>> yocto mailing list
>> >>> yocto@yoctoproject.org
>> >>> https://lists.yoctoproject.org/listinfo/yocto
>> >>>
>> >>
>> >> --
>> >> Maciej Pijanowski
>> >> Embedded Systems Engineerhttps://3mdeb.com | @3mdeb_com
>> >>
>> >> --
>> >> ___
>> >> yocto mailing list
>> >> yocto@yoctoproject.org
>> >> https://lists.yoctoproject.org/listinfo/yocto
>> >>
>> >
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Can't boot to initramfs

[JH]

Thanks Zoran, I have tools to test it, I'll try it, it will be a long
journey though.

Thank you.

- jupter

On 7/16/19, Zoran Stojsavljevic  wrote:
> Hello Jupiter,
>
> I actually continued this topic initiated by Moritz, to find out how
> you and me and somebody else also can build the yocto build system
> with bundled rescue kernel into the rootfs.
>
> My target architecture I am playing with is armv7 A8 (BBB), since I am
> experimenting with it.
>
> I actually built the armv7 A8 (BBB) with the unbundled initramfs,
> where the BSP actually ends up for the testing purposes. All this how
> I did it is described here:
> https://lists.yoctoproject.org/pipermail/yocto/2018-July/041696.html
>
> Here is also latest local.conf for warrior (how I am buillding it):
> https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/local.conf_full
>
> I never built such a system with rescue initramfs, ending with/in
> rootfs on mtd/flash, or SD card, YOCTO wise, so I actually continued
> this topic to find out exactly the same what you asked me above.
>
> You can go over this email thread, and try while building with what we
> all put as collection of patchworks.
>
> I have no time to do this, since I need very urgently to do some other
> important for me stuff on BBB.
>
> Zoran
> ___
>
>
>
>
> On Mon, Jul 15, 2019 at 2:10 PM JH  wrote:
>>
>> Hi Zoran,
>>
>> On 7/12/19, Zoran Stojsavljevic  wrote:
>> > Moritz,
>> >
>> > Thank you very much for this reply. It makes it very clear... What is
>> > the current State of Affairs for the topic.
>> >
>> > Let us see if there will be the improvement to this topic. I'll
>> > document this on one of my private GitHubs. And archive this email.
>>
>> Any chance to access your documents?
>>
>> Thank you.
>>
>> - jupiter
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wic: error when using --rootfs-dir=${IMAGE_ROOTFS}/data

[Belisko Marek]

On Tue, Jul 16, 2019 at 8:54 AM Mittal, Anuj  wrote:
>
> On Tue, 2019-07-16 at 08:38 +0200, Belisko Marek wrote:
> > I have wks file with following content:
> >
> > part ubootenv --ondisk=mmcblk --no-table --size 12
> > part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat
> > --label boot --active --align 1024 --size 16
> > part /root --source rootfs --ondisk mmcblk --fstype=ext4 --label
> > rootA
> > --align 1024 --fixed-size 300 --exclude-path data/
> > part /data --source rootfs --rootfs-dir=${IMAGE_ROOTFS}/data --ondisk
> > "mmcblk" --fstype=ext4 --label data --align 1024 --fixed-size 200
> >
> > Basically I want to create extra data partition with content from
> > rootfs /data directory. When wic image is created I'm getting strange
> > errors like:
> >
> > Couldn't get bitbake variable from
> > /home/marekbelisko/.build/tmp/sysroots/raspberrypi0-
> > wifi/imgdata/${IMAGE_ROOTFS}/data.env.
> >  | File /home/marekbelisko/.build/tmp/sysroots/raspberrypi0-
> > wifi/imgdata/${IMAGE_ROOTFS}/data.env
> > doesn't exist.
>
> If you haven't tried this already, renaming .wks to .wks.in might help.
Thanks that does the trick. But I'm completely confused why? ;) Any
explanation? Thanks.
>
> Thanks,
> Anuj

BR,

marek

-- 
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] wpewebkit, cog and libgles2

[Andy Pont]

Hello,

I am trying to add wpewebkit and the cog browser on top of a 
core-image-minimal build using Warrior.  When I try to build bitbake 
gives me the following output:


ERROR: Nothing PROVIDES 'virtual/egl' (but 
/home/me/yocto/sources/meta-webkit/recipes-browser/wpewebkit/wpewebkit_2.24.2.bb, 
/home/me/yocto/sources/meta-webkit/recipes-browser/libwpe/libwpe_1.2.0.bb 
DEPENDS on or otherwise requires it). Close matches:

  virtual/kernel
  virtual/perf
  virtual/mesa

I am building for a Microchip (Atmel) SAMA5D2 using meta-atmel.  We 
don’t need OpenGL or 3D support - hence one of the reasons for picking 
the SAMA5D2 which doesn’t have a hardware GPU.


The options appear to be to either add software OpenGL support to the 
configuration to resolve the dependency or tell wpewebkit not to want 
OpenGL support.


Any advice on the easiest way to resolve this would be much appreciated.

-Andy.


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wpewebkit, cog and libgles2

[Burton, Ross]

On Tue, 16 Jul 2019 at 13:53, Andy Pont  wrote:
> I am building for a Microchip (Atmel) SAMA5D2 using meta-atmel.  We don’t 
> need OpenGL or 3D support - hence one of the reasons for picking the SAMA5D2 
> which doesn’t have a hardware GPU.
>
> The options appear to be to either add software OpenGL support to the 
> configuration to resolve the dependency or tell wpewebkit not to want OpenGL 
> support.

Well the libwpe build script says this:

find_package(EGL REQUIRED)

(https://github.com/WebPlatformForEmbedded/libwpe/blob/master/CMakeLists.txt)

Which suggests that you can't build it without EGL.  You should
investigate whether EGL is simply an option, or whether it's used as a
fundamental part of the rendering.  If it's optional then the Mesa
recipe can build a software GL implementation, if the latter then
you'll need a new browser as software GL is *terrible*.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wpewebkit, cog and libgles2

[Andy Pont]

Ross wrote...


Well the libwpe build script says this:

find_package(EGL REQUIRED)

(https://github.com/WebPlatformForEmbedded/libwpe/blob/master/CMakeLists.txt)


I’m confused now as there appears to be two active meta layers that 
support WPE WebKit. The one you reference meta-wpe and the one I was 
originally using meta-webkit (https://github.com/Igalia/meta-webkit) as 
that was the one that included Cog. Is one preferred to the other?



Which suggests that you can't build it without EGL.  You should
investigate whether EGL is simply an option, or whether it's used as a
fundamental part of the rendering.  If it's optional then the Mesa
recipe can build a software GL implementation, if the latter then
you'll need a new browser as software GL is *terrible*.
I’m not wedded to Cog as a browser. I just need something that can 
support HTML5 and Javascript as it will be running a single page 
application (SPA) served from localhost.


-Andy.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wpewebkit, cog and libgles2

[Joshua Watt]

On 7/16/19 8:43 AM, Andy Pont wrote:

Ross wrote...


Well the libwpe build script says this:
find_package(EGL REQUIRED)
(https://github.com/WebPlatformForEmbedded/libwpe/blob/master/CMakeLists.txt)


I’m confused now as there appears to be two active meta layers that 
support WPE WebKit. The one you reference meta-wpe and the one I was 
originally using meta-webkit (https://github.com/Igalia/meta-webkit) 
as that was the one that included Cog. Is one preferred to the other?


AFAIK, meta-webkit is the one you should be using. Its the one currently 
being actively maintained by the WPEWebKit folks.





Which suggests that you can't build it without EGL. You should
investigate whether EGL is simply an option, or whether it's used as a
fundamental part of the rendering. If it's optional then the Mesa
recipe can build a software GL implementation, if the latter then
you'll need a new browser as software GL is *terrible*.
I’m not wedded to Cog as a browser. I just need something that can 
support HTML5 and Javascript as it will be running a single page 
application (SPA) served from localhost.


I've used Cog before. Calling it a "brower" is generous it doesn't 
have any of the normal browers trappings like history, navigation (e.g. 
back button, refresh), tabs, etc. It's probably more accurately 
described as an HTML5 rendering application, which sounds like all you 
really want anyway.


FWIW, I've always been under the assumption that GLES was required for 
WPEWebKit.




-Andy.


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Pre-installing node.js packages

[Andy Pont]

Hello,

Is there a way to add node.js packages into a build?  I’m trying to 
avoid having to include npm and compiler into my target image.


-Andy.

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Pre-installing node.js packages

[Burton, Ross]

The proper way would be to write a recipe for each package you wish to add.

Ross

On Tue, 16 Jul 2019 at 16:04, Andy Pont  wrote:
>
> Hello,
>
> Is there a way to add node.js packages into a build?  I’m trying to
> avoid having to include npm and compiler into my target image.
>
> -Andy.
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Pre-installing node.js packages

[Jean-marie Lemetayer]

Hi,

You can check this link: https://wiki.yoctoproject.org/wiki/TipsAndTricks/NPM

I have recently added some fixes concerning npm. But I still have
some issues using devtool: e.g the lockdown.json generation using
the npm lockdown module is erroneous.

I have no time for now, but I have planned to upstream some fixes.

- Original Message -
From: "Andy Pont" 
To: "Yocto-mailing-list" 
Sent: Tuesday, July 16, 2019 5:03:27 PM
Subject: [yocto] Pre-installing node.js packages

Hello,

Is there a way to add node.js packages into a build?  I’m trying to 
avoid having to include npm and compiler into my target image.

-Andy.

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Pre-installing node.js packages

[Alexander Stein]

If you want to avoid writing those recipes yourself, you can use devtool.
See https://wiki.yoctoproject.org/wiki/TipsAndTricks/NPM

I'm not sure how a proper workflow should be done, to keep the extracted 
sources out of the meta, but it is a starting point.

Alexander

On Tuesday, July 16, 2019, 5:15:19 PM CEST Burton, Ross wrote:
> The proper way would be to write a recipe for each package you wish to add.
> 
> Ross
> 
> On Tue, 16 Jul 2019 at 16:04, Andy Pont  wrote:
> >
> > Hello,
> >
> > Is there a way to add node.js packages into a build?  I?m trying to
> > avoid having to include npm and compiler into my target image.
> >
> > -Andy.
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> 


-- 
Dipl-Inf. Alexander Stein

SYS TEC electronic AG
Am Windrad 2
08468 Heinsdorfergrund
Germany
Tel: +49-3765-38600-0, Fax: +49-3765-38600-4100
Email   : alexander.st...@systec-electronic.com
Internet: http://www.systec-electronic.com

Board of Directors: Dipl.-Ing. Ronald Sieber, Dipl.-Ing. Dirk Bause
Chairman of the Supervisory Board: Dipl.-Phys. Siegmar Schmidt
Commercial registry: Amtsgericht Chemnitz, HRB 32220; USt.-Id Nr. 
DE150534010

--

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen.

Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten haben, informieren Sie bitte sofort den Absender und vernichten 
Sie diese Mail.

Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind 
nicht gestattet.

--

This e-mail may contain confidential and/or privileged information.

If you are not the intended recipient (or have received this e-mail in 
error) please notify the sender immediately and destroy this e-mail.

Any unauthorized copying, disclosure or distribution of the material in 
this e-mail is strictly forbidden.

--


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Patching a file in $WORKDIR

[Siegel, Jeffrey (Nokia - US/Murray Hill)]

Hi,
I am trying to use a bbappend file to patch a file in $WORKDIR. To my 
understanding, the native Yocto patching process only works for patching files 
in $S.
I have come up with a solution:

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI_append =" file://inputrc.ptch"
do_patch_append () {
cmd="patch -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wpewebkit, cog and libgles2

[Andy Pont]

Joshua wrote...


I’m confused now as there appears to be two active meta layers that support WPE 
WebKit. The one you reference meta-wpe and the one I was originally using 
meta-webkit (https://github.com/Igalia/meta-webkit) as that was the one that 
included Cog. Is one preferred to the other?


AFAIK, meta-webkit is the one you should be using. Its the one currently being 
actively maintained by the WPEWebKit folks.
I have gone back to using that one. I think I am being a bit dim (I 
blame the unusually warm UK weather) but I can’t see what bitbake is 
complaining about. Having added:


IMAGE_INSTALL_append = " nodejs wpewebkit”

bitbake reports:

ERROR: Nothing PROVIDES 'libepoxy' (but 
/home/me/yocto/sources/meta-webkit/recipes-browser/wpewebkit/wpewebkit_2.24.2.bb 
DEPENDS on or otherwise requires it)
libepoxy was skipped: missing required distro feature 'opengl' (not in 
DISTRO_FEATURES)


despite my local.conf containing:

DISTRO_FEATURES_append = " opengl libepoxy”

Can someone put me out of my misery?

-Andy.

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wpewebkit, cog and libgles2

[Burton, Ross]

On Tue, 16 Jul 2019 at 18:37, Andy Pont  wrote:
> ERROR: Nothing PROVIDES 'libepoxy' (but 
> /home/me/yocto/sources/meta-webkit/recipes-browser/wpewebkit/wpewebkit_2.24.2.bb
>  DEPENDS on or otherwise requires it)
> libepoxy was skipped: missing required distro feature 'opengl' (not in 
> DISTRO_FEATURES)
>
> despite my local.conf containing:
>
> DISTRO_FEATURES_append = " opengl libepoxy”
>
> Can someone put me out of my misery?

Remove libepoxy from there, DISTRO_FEATURES are abstract and libepoxy
isn't a valid one.

My best suggestion would be:

$ bitbake -e libepoxy | less

Search that until you find the DISTRO_FEATURES= and see if it it
contains opengl.  It presumably doesn't, and above the assignment it
will tell you what removed it (or the absence of something adding it).

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wpewebkit, cog and libgles2

[Andy Pont]

Ross wrote...


Search that until you find the DISTRO_FEATURES= and see if it it
contains opengl.  It presumably doesn't, and above the assignment it
will tell you what removed it (or the absence of something adding it).


The conf/distro/poky-atmel.conf file in meta-atmel contains the 
following line:


DISTRO_FEATURES_remove ?= "opengl wayland x11 3g nfc pulseaudio”

Switching back to the regular DISTRO = “poky” seems to have got it 
building again.


Thanks for your help and guidance!

-Andy.-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW29'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M2

Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Amanda
*   SWAT team rotation: Amanda ->  Anuj on July 19, 2019
*   SWAT team rotation: Anuj -> Paul on July 26, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday July 18th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday August 6th at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday August 13th at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   2.7.1 is cleared for release and will be announced shortly
*   2.6.3 has two remaining issues before it can be built
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   General patch backlog and merging is running back to normal
*   Our numbers of patches in the metadata has been slowly decreasing
and I wanted to mention how much we appreciate anyone doing cleanup of
old/stale data. Over time it is making a significant difference!
*   There are ongoing discussions on a few key topics which are
summarised here for convenience. Please contribute if you have an interest
in these areas:

*   Running the testsuites for glibc/binutils/gcc
*   Moving lsb to its own layer
*   Removing poky-lsb in favour of some configuration fragments
*   Reproducibility
*   Minimising python2 dependencies
*   Configuration of init systems

*   Bitbake changes which change the way runqueue works quite radically
have merged. If people see errors with setscene or normal task execution
people do report them.
*   Runqueue change to optimise sstate usage/sharing in multiconfig
builds merged. Please report if its not working where you'd expect it to.

 

Planned Releases for YP 2.8:

*   M2 Cutoff 14th July
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept
*   2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.1 (Warrior) is ready for release.
*   YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M2

 

Tracking Metrics:

*   WDD 2498 (last week 2496) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1502 (last week 1506)
*   Patches in the Pending State: 630 (42%) [last week 634 (42%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [layerindex-web][PATCH 0/7] Recipe reporting system fixes (cover letter only)

[Paul Eggleton]

A bunch of fixes mostly for the Recipe Reporting System (RRS) part of
the layer index. In particular, 5/7 fixes the RRS for layers in
meta-openembedded.


The following changes since commit ce5141fc39b2b171383fca002b2bc5cf082b31f4:

  RRS: add tool to import/export upstream history data (2019-02-14 10:05:53 
+1300)

are available in the Git repository at:

  git://git.yoctoproject.org/layerindex-web paule/fixes13
  http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/fixes13

Paul Eggleton (7):
  Split out patch status read to a method on the Patch model
  Record patch application order and use as default sorting
  Add admin handling for Patch objects
  RRS: Fix raw SQL statements to use parameters
  RRS: fix showing all recipes for multi-layer maintenance plans
  RRS: move Export button and restore Tools drop-down menu
  RRS: add missing migration

 layerindex/admin.py   |  11 +-
 .../migrations/0027_patch_apply_order.py  |  24 +++
 layerindex/models.py  |  31 
 layerindex/tools/import_otherdistro.py|   5 +-
 layerindex/update_layer.py|  34 +
 .../0019_maintplan_admin_delete_null.py   |  22 +++
 rrs/views.py  | 143 +-
 templates/base.html   |   4 +
 templates/rrs/base_toplevel.html  |   5 +-
 templates/rrs/recipes.html|   2 +
 10 files changed, 173 insertions(+), 108 deletions(-)
 create mode 100644 layerindex/migrations/0027_patch_apply_order.py
 create mode 100644 rrs/migrations/0019_maintplan_admin_delete_null.py

-- 
2.20.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 2.7.1 (Warrior 21.0.1) Released

[Tummalapalli, Vineela]

Hello,

We are pleased to announce the Yocto Project 2.7.1 (warrior-21.0.1) Release is 
now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-2.7.1/poky-warrior-21.0.1.tar.bz2
 
http://mirrors.kernel.org/yocto/yocto/yocto-2.7.1/poky-warrior-21.0.1.tar.bz2 

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-2.7.1/RELEASENOTES 

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-2.7.1/testreport.txt 

Thank you for everyone's contributions to this release.

Vineela Tummalapalli
Yocto Project Build and Release
Vineela Tummalapalli 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 2.7.1 (Warrior 21.0.1) Released

[Scott Rifenbark]

Hi,

"Current" docs symlink now pointing to 2.7.1 release (i.e.
https://yoctoproject.org/docs/current/ref-manual/ref-manual.html).

Thanks,
Scott

On Tue, Jul 16, 2019 at 5:26 PM Tummalapalli, Vineela <
vineela.tummalapa...@intel.com> wrote:

> Hello,
>
> We are pleased to announce the Yocto Project 2.7.1 (warrior-21.0.1)
> Release is now available for download.
>
>
> http://downloads.yoctoproject.org/releases/yocto/yocto-2.7.1/poky-warrior-21.0.1.tar.bz2
>
> http://mirrors.kernel.org/yocto/yocto/yocto-2.7.1/poky-warrior-21.0.1.tar.bz2
>
> A gpg signed version of these release notes is available at:
>
> http://downloads.yoctoproject.org/releases/yocto/yocto-2.7.1/RELEASENOTES
>
> Full Test Report:
>
> http://downloads.yoctoproject.org/releases/yocto/yocto-2.7.1/testreport.txt
>
> Thank you for everyone's contributions to this release.
>
> Vineela Tummalapalli
> Yocto Project Build and Release
> Vineela Tummalapalli 
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Patching a file in $WORKDIR

[Gabriele Zampieri]

Hi Jeffrey,

the extension "ptch" is not treated as patchfile by Yocto (only *.diff and
*.patch). You have two options:

   - Rename your patch in inputrc.patch
   - Adding the apply switch:
   SRC_URI_append =" file://inputrc.ptch;apply=yes"
   In this way you are telling yocto that 'inputrc.ptch' is a patch file

In both cases you can remove your append.
This should be enough.

Best regards,
Gabriele

Il giorno mar 16 lug 2019 alle ore 18:44 Siegel, Jeffrey (Nokia - US/Murray
Hill)  ha scritto:

> Hi,
>
> I am trying to use a bbappend file to patch a file in $WORKDIR. To my
> understanding, the native Yocto patching process only works for patching
> files in $S.
>
> I have come up with a solution:
>
>
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>
> SRC_URI_append =" file://inputrc.ptch"
>
> do_patch_append () {
>
> cmd="patch 
> (exitstatus, output) = oe.utils.getstatusoutput(cmd)
>
> if exitstatus != 0:
>
>raise bb.process.CmdError(cmd, output)
>
> return output
>
> }
>
>
>
> It does work. But I think this is line is not very elegant: cmd="patch
>  being executed is the one from the Yocto environment
> ($BUILDDIR/tmp-glibc/hosttools), not the build host. But I still suspect
> there is a better way. Any suggestions?
>
>
>
> Regards,
>
> Jeff
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto