date:20200413

[yocto] What is the recommended method to patch a recipe?

2020-04-13 Thread nus1998

Hi All,


I googled some topics on how to patch a recipe, most of them recommend to 
generate a corresponding .bbappend to apply the patch, I wonder if there 
is already a bbappend file, shall I modify the bbappend file directly, or 
create another layer to overwrite the bbappend file (and including the patchs 
in original bbappend file)?


Thanks in advance
Nus
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49118): https://lists.yoctoproject.org/g/yocto/message/49118
Mute This Topic: https://lists.yoctoproject.org/mt/72982468/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] What is the recommended method to patch a recipe?

2020-04-13 Thread Thomas Goodwin

As with a lot of things, I’m sure it all depends on the scope of the change.  
Personally, if I ‘own’ the original bbappend, then I consider if it’s worth 
establishing an override or some other similar mechanism within that bbappend, 
depending on what I’m developing (an image feature or something 
machine-specific).  If it’s a one-off for a specific build that I can lump 
together with other changes, then I go with a new layer specific those changes.

One thing to keep in mind is that if you create your own layer with a bbappend 
,then layer priority will impact which portions of your bbappend overwrite the 
others and the original recipe.  You can use bitbake -e package-name to get a 
view of how bitbake is overlaying all changes for it.

Cheers,

Thomas

On Apr 13, 2020, 4:20 AM -0400, nus1998 , wrote:
> Hi All,
>
> I googled some topics on how to patch a recipe, most of them recommend to 
> generate a corresponding .bbappend to apply the patch, I wonder if there 
> is already a bbappend file, shall I modify the bbappend file directly, or 
> create another layer to overwrite the bbappend file (and including the patchs 
> in original bbappend file)?
>
> Thanks in advance
> Nus
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49119): https://lists.yoctoproject.org/g/yocto/message/49119
Mute This Topic: https://lists.yoctoproject.org/mt/72982468/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] What is the recommended method to patch a recipe?

2020-04-13 Thread Nicolas Dechesne

On Mon, Apr 13, 2020 at 10:20 AM nus1998  wrote:

> Hi All,
>
> I googled some topics on how to patch a recipe, most of them recommend to
> generate a corresponding .bbappend to apply the patch, I wonder if
> there is already a bbappend file, shall I modify the bbappend file
> directly, or create another layer to overwrite the bbappend file (and
> including the patchs in original bbappend file)?
>

A good rule of thumb is to never modify a metadata that is not yours. That
applies to everything:
* if you need to modify a bb file from a 3rd party library, create a
bbappend file in your layer
* if you need to modify a bbappend from a 3rd party, then create another
bbappend in your layer

And by 3rd party i mean any layer/tree which is not yours (OE-core, or any
other layer your are using).

> Thanks in advance
> Nus
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49120): https://lists.yoctoproject.org/g/yocto/message/49120
Mute This Topic: https://lists.yoctoproject.org/mt/72982468/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] What is the recommended method to patch a recipe?

2020-04-13 Thread Alexander Kanavin

On Mon, 13 Apr 2020 at 12:46, Nicolas Dechesne 
wrote:

> A good rule of thumb is to never modify a metadata that is not yours. That
> applies to everything:
> * if you need to modify a bb file from a 3rd party library, create a
> bbappend file in your layer
> * if you need to modify a bbappend from a 3rd party, then create another
> bbappend in your layer
>
> And by 3rd party i mean any layer/tree which is not yours (OE-core, or any
> other layer your are using).
>

I beg to differ! Bbappends are making it difficult to reason about what the
recipe with all its appends is doing (because they destroy spatial locality
and aren't easily visible), and I would actually discourage using them if
the modification can go to the original recipe.

Is it fixing a problem? Is it adding a build option absent from the
original recipe? Then please take the trouble to submit the change to the
owners of the recipe.

Similarly, if a bbappend is re-setting the component version to something
else (yes, people do that despite my best efforts to prohibit the
practice), then a much cleaner approach is to actually make a fully copy of
the recipe, or go and fix the original.

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49121): https://lists.yoctoproject.org/g/yocto/message/49121
Mute This Topic: https://lists.yoctoproject.org/mt/72982468/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] What is the recommended method to patch a recipe?

2020-04-13 Thread Nicolas Dechesne

On Mon, Apr 13, 2020 at 12:55 PM Alexander Kanavin 
wrote:

> On Mon, 13 Apr 2020 at 12:46, Nicolas Dechesne <
> nicolas.deche...@linaro.org> wrote:
>
>> A good rule of thumb is to never modify a metadata that is not yours.
>> That applies to everything:
>> * if you need to modify a bb file from a 3rd party library, create a
>> bbappend file in your layer
>> * if you need to modify a bbappend from a 3rd party, then create another
>> bbappend in your layer
>>
>> And by 3rd party i mean any layer/tree which is not yours (OE-core, or
>> any other layer your are using).
>>
>
> I beg to differ! Bbappends are making it difficult to reason about what
> the recipe with all its appends is doing (because they destroy spatial
> locality and aren't easily visible), and I would actually discourage using
> them if the modification can go to the original recipe.
>

Ok.. you're right. Well at least my answer is not complete ;)

> Is it fixing a problem? Is it adding a build option absent from the
> original recipe? Then please take the trouble to submit the change to the
> owners of the recipe.
>

This is correct. We should encourage everyone to report, and even better
propose a fix, to the relevant layer, when the 'problem' is applicable. I
didn't want to discourage that, for sure!
When developing against master, it's a no brainer. When developing against
a stable branch (like probably many users), it's not as obvious. In that
case I think trying to avoid 'touching' somebody else layer remains a good
advice, since it makes upgrades and maintenance trickier.

>
> Similarly, if a bbappend is re-setting the component version to something
> else (yes, people do that despite my best efforts to prohibit the
> practice), then a much cleaner approach is to actually make a fully copy of
> the recipe, or go and fix the original.
>

Recipes version upgrades (or downgrade) should be done in a dedicated layer
owned by the 'developer', and in that case, I agree that bbappend should be
prohibited, and the entire recipe should be copied.

> Alex
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49122): https://lists.yoctoproject.org/g/yocto/message/49122
Mute This Topic: https://lists.yoctoproject.org/mt/72982468/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2020-04-13 Thread Stephen Jolley

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 309
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "3.1", "3.2, "3.99" and "Future", the more pressing/urgent issues
being in "3.1" and then "3.2".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

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

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49123): https://lists.yoctoproject.org/g/yocto/message/49123
Mute This Topic: https://lists.yoctoproject.org/mt/72991249/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current Top developers on Yocto Project 3.1

2020-04-13 Thread Stephen Jolley

All,

Below is the list as of top 43 developers as of the end of WW15 of who have
open medium or higher bugs and enhancements against YP 3.1.   There are 13
possible work days left until the final release candidates for YP 3.1 needs
to be released.


Who

Count


richard.pur...@linuxfoundation.org

36


liezhi.y...@windriver.com

27


david.re...@windriver.com

21


akuster...@gmail.com

16


bluelightn...@bluelightning.org

13


bruce.ashfi...@gmail.com

11


mark.mor...@windriver.com

11


kai.k...@windriver.com

10


randy.macl...@windriver.com

10


qi.c...@windriver.com

10


r...@burtonini.com

7


timothy.t.orl...@intel.com

7


trevor.gamb...@windriver.com

6


mich...@yoctoproject.org

6


pbar...@konsulko.com

5


jpewhac...@gmail.com

5


changqing...@windriver.com

5


jon.ma...@arm.com

5


alejan...@enedino.org

4


kexin@windriver.com

4


alex.kana...@gmail.com

4


mingli...@windriver.com

4


matthew.z...@windriver.com

3


hongxu@windriver.com

3


mark.ha...@kernel.crashing.org

2


kerg...@gmail.com

2


mostthings...@gmail.com

2


jae...@xilinx.com

2


jpuhl...@mvista.com

2


yang.w...@windriver.com

2


ycnakaj...@gmail.com

2


raj.k...@gmail.com

2


se...@seebs.net

2


limon.ani...@gmail.com

2


rpj...@crashcourse.ca

2


amber.n.ell...@intel.com

1


naveen.kumar.sa...@intel.com

1


anuj.mit...@intel.com

1


de...@denix.org

1


ee.peng.y...@intel.com

1


ms...@mvista.com

1


apoorv.san...@intel.com

1


kai.ruh...@live.com

1


scott.bran...@broadcom.com

1


yi.z...@windriver.com

1


dl...@gmx.de

1


jonathan.y...@intel.com

1


martin.ja...@gmail.com

1


maxime.roussinbelan...@gmail.com

1

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

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

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49124): https://lists.yoctoproject.org/g/yocto/message/49124
Mute This Topic: https://lists.yoctoproject.org/mt/72991328/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW15!

2020-04-13 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


randy.macl...@windriver.com

7


richard.pur...@linuxfoundation.org

5


timothy.t.orl...@intel.com

2


akus...@mvista.com

2


ee.peng.y...@intel.com

1


changqing...@windriver.com

1


mich...@yoctoproject.org

1


jpuhl...@mvista.com

1


david.re...@windriver.com

1


Grand Total

21

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

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

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49125): https://lists.yoctoproject.org/g/yocto/message/49125
Mute This Topic: https://lists.yoctoproject.org/mt/72991428/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] M+ & H bugs with Milestone Movements WW15

2020-04-13 Thread Stephen Jolley

All,

YP M+ or high bugs which moved to a new milestone in WW15 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


High

  13604

[master-next] Distrodata.test_maintainers  fails

randy.macl...@windriver.com

kai.k...@windriver.com

3.1 M4

3.2 M1


 

  13802

ltp tests fail with ssh connection lost  error intermittently

randy.macl...@windriver.com

yang.w...@windriver.com

3.1 M4

3.2 M1


Medium+

  12090

bitbake resident server reconnect needed ?

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

3.99

3.2 M1


 

  12367

moving or removing tmp breaks persistent bitbake server

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

3.99

3.2 M1


 

  12368

persistent bitbake server does not re-parse if previous build was ctrl+C'd

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

3.99

3.2 M1

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

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

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49126): https://lists.yoctoproject.org/g/yocto/message/49126
Mute This Topic: https://lists.yoctoproject.org/mt/72991506/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Image size reduction

2020-04-13 Thread Randy MacLeod


On 2020-04-04 12:27 p.m., Ajam Ali wrote:

Hi All,

Thanks for your suggestions. I am working on your suggestions.
I will let you know if it did not work for me.


Ajam,


It would be useful if you could reply either way.


If there's still a problem then perhaps someone can help.


If you are able to resolve the issue, then a brief summary

of what you did could help the next person who has a similar

issue.


Thanks,

../Randy




Regards,
Ajam Ali



*From:* yocto@lists.yoctoproject.org  on 
behalf of Gmane Admin via lists.yoctoproject.org 


*Sent:* Saturday, April 4, 2020 9:36 PM
*To:* yocto@lists.yoctoproject.org 
*Subject:* Re: [yocto] Image size reduction
[CAUTION: This Email is from outside the Organization. Do not click 
links or open attachments unless you trust the sender.]


Op 29-03-2020 om 18:28 schreef Ajam Ali:
> Hi All,
>
> Actually my current image size is 3.9GB because of heavy size packages
> required by my project and without project required packages my image
> size in Yocto is 800MB.

So your project adds 3.1GB right

> I want to reduce the image size as maximum as possible.

3.1GB is huge. Compare to f.i. Libreoffice (installed 0.5GB or so).
Either your own code has a lot of fat, or you are pulling in lots of
packages you don't really need. But is there no way to advise you
without knowing more.

> Please suggest the best possible way so that I could reduce the maximum
> possible size(desirable below 1.5 GB).
>
>
> Thanks in advance,
> Ajam Ali
>
>
> Sent from Outlook Mobile 


> ::DISCLAIMER::
> 
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only. E-mail transmission is not
> guaranteed to be secure or error-free as information could be
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
> may contain viruses in transmission. The e mail and its contents (with
> or without referred errors) shall therefore not attach any liability on
> the originator or HCL or its affiliates. Views or opinions, if any,
> presented in this email are solely those of the author and may not
> necessarily reflect the views or opinions of HCL or its affiliates. Any
> form of reproduction, dissemination, copying, disclosure, modification,
> distribution and / or publication of this message without the prior
> written consent of authorized representative of HCL is strictly
> prohibited. If you have received this email in error please delete it
> and notify the sender immediately. Before opening any email and/or
> attachments, please check them for viruses and other defects.
> 
>
>
>







--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49127): https://lists.yoctoproject.org/g/yocto/message/49127
Mute This Topic: https://lists.yoctoproject.org/mt/72633147/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Files get sporadically lost for native packages

2020-04-13 Thread Konrad Weihmann


Hi Randy,

I'm trying all day to create an account at bugzilla to file the issue, 
but somehow I don't get any confirmation mail  (although I tried several 
mail accounts today, and no it didn't got stuck in spam;-)) - guess 
that's not how it is supposed to be, right :-)? - I don't know where to 
address such a problem, so take this reply as FYI.


Best
Konrad

On 03.04.20 21:28, Randy MacLeod wrote:

On 2020-04-02 4:44 a.m., Konrad Weihmann wrote:


To answer your others questions... see below

On 02.04.20 05:42, Randy MacLeod wrote:

On 2020-03-28 8:26 a.m., Konrad Weihmann wrote:

Hi,

I'm facing the following error message sporadically on all branches 
I tried so far (master, zeus, warrior and thud)


The stack trace of python calls that resulted in this 
exception/failure was:

File: 'exec_python_func() autogenerated', lineno: 2, function: 
  0001:
  *** 0002:extend_recipe_sysroot(d)
  0003:
File: '/build/poky/meta/classes/staging.bbclass', lineno: 551, 
function: extend_recipe_sysroot

  0547:    dest = newmanifest[l]
  0548:    if l.endswith("/"):
  0549:    staging_copydir(l, targetdir, 
dest, seendirs)

  0550:    continue
  *** 0551:    staging_copyfile(l, targetdir, dest, 
postinsts, seendirs)

  0552:
  0553:    bb.note("Installed into sysroot: %s" % str(msg_adding))
  0554:    bb.note("Skipping as already exists in sysroot: %s" % 
str(msg_exists))

  0555:
File: '/build/poky/meta/classes/staging.bbclass', lineno: 152, 
function: staging_copyfile

  0148:    os.symlink(linkto, dest)
  0149:    #bb.warn(c)
  0150:    else:
  0151:    try:
  *** 0152:    os.link(c, dest)
  0153:    except OSError as err:
  0154:    if err.errno == errno.EXDEV:
  0155:    bb.utils.copyfile(c, dest)
  0156:    else:
Exception: FileNotFoundError: [Errno 2] No such file or directory: 
'/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc' 
-> 
'/build/poky/build/tmp/work/qemux86_64-mine-linux/core-image-minimal-mine/1.0-r0/recipe-sysroot-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc'


I already had a look at the manifest

cat manifest-x86_64-python3-msgcheck-native.populate_sysroot
/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__init__.py 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/po.py 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/msgcheck.py 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/po.cpython-37.pyc 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/msgcheck.cpython-37.pyc 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/dependency_links.txt 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/requires.txt 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/top_level.txt 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/SOURCES.txt 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/PKG-INFO 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/entry_points.txt 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/bin/msgcheck 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/sysroot-providers/python3-msgcheck-native 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/ 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/ 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/ 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/ 

/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/ 

/build/poky/build/tmp/sy

Re: [yocto] Files get sporadically lost for native packages

2020-04-13 Thread Alexander Kanavin

Adding Michael (lack of confirmtation email from bugzilla).

Alex

On Mon, 13 Apr 2020 at 19:59, Konrad Weihmann  wrote:

> Hi Randy,
>
> I'm trying all day to create an account at bugzilla to file the issue,
> but somehow I don't get any confirmation mail  (although I tried several
> mail accounts today, and no it didn't got stuck in spam;-)) - guess
> that's not how it is supposed to be, right :-)? - I don't know where to
> address such a problem, so take this reply as FYI.
>
> Best
> Konrad
>
> On 03.04.20 21:28, Randy MacLeod wrote:
> > On 2020-04-02 4:44 a.m., Konrad Weihmann wrote:
> >>
> >> To answer your others questions... see below
> >>
> >> On 02.04.20 05:42, Randy MacLeod wrote:
> >>> On 2020-03-28 8:26 a.m., Konrad Weihmann wrote:
>  Hi,
> 
>  I'm facing the following error message sporadically on all branches
>  I tried so far (master, zeus, warrior and thud)
> 
>  The stack trace of python calls that resulted in this
>  exception/failure was:
>  File: 'exec_python_func() autogenerated', lineno: 2, function:
> 
>    0001:
>    *** 0002:extend_recipe_sysroot(d)
>    0003:
>  File: '/build/poky/meta/classes/staging.bbclass', lineno: 551,
>  function: extend_recipe_sysroot
>    0547:dest = newmanifest[l]
>    0548:if l.endswith("/"):
>    0549:staging_copydir(l, targetdir,
>  dest, seendirs)
>    0550:continue
>    *** 0551:staging_copyfile(l, targetdir, dest,
>  postinsts, seendirs)
>    0552:
>    0553:bb.note("Installed into sysroot: %s" % str(msg_adding))
>    0554:bb.note("Skipping as already exists in sysroot: %s" %
>  str(msg_exists))
>    0555:
>  File: '/build/poky/meta/classes/staging.bbclass', lineno: 152,
>  function: staging_copyfile
>    0148:os.symlink(linkto, dest)
>    0149:#bb.warn(c)
>    0150:else:
>    0151:try:
>    *** 0152:os.link(c, dest)
>    0153:except OSError as err:
>    0154:if err.errno == errno.EXDEV:
>    0155:bb.utils.copyfile(c, dest)
>    0156:else:
>  Exception: FileNotFoundError: [Errno 2] No such file or directory:
> 
> '/build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc'
>
>  ->
> 
> '/build/poky/build/tmp/work/qemux86_64-mine-linux/core-image-minimal-mine/1.0-r0/recipe-sysroot-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc'
> 
>  I already had a look at the manifest
> 
>  cat manifest-x86_64-python3-msgcheck-native.populate_sysroot
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__init__.py
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/po.py
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/msgcheck.py
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/__init__.cpython-37.pyc
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/po.cpython-37.pyc
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck/__pycache__/msgcheck.cpython-37.pyc
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/dependency_links.txt
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/requires.txt
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/top_level.txt
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/SOURCES.txt
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/PKG-INFO
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/lib/python3.7/site-packages/msgcheck-2.8-py3.7.egg-info/entry_points.txt
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/python3-msgcheck-native/usr/bin/msgcheck
>
> 
> 
> /build/poky/build/tmp/sysroots-components/x86_64/pyth

Re: [yocto] What is the recommended method to patch a recipe?

2020-04-13 Thread Philip Balister

On 4/13/20 10:31 AM, Nicolas Dechesne wrote:
> On Mon, Apr 13, 2020 at 12:55 PM Alexander Kanavin 
> wrote:
> 
>> On Mon, 13 Apr 2020 at 12:46, Nicolas Dechesne <
>> nicolas.deche...@linaro.org> wrote:
>>
>>> A good rule of thumb is to never modify a metadata that is not yours.
>>> That applies to everything:
>>> * if you need to modify a bb file from a 3rd party library, create a
>>> bbappend file in your layer
>>> * if you need to modify a bbappend from a 3rd party, then create another
>>> bbappend in your layer
>>>
>>> And by 3rd party i mean any layer/tree which is not yours (OE-core, or
>>> any other layer your are using).
>>>
>>
>> I beg to differ! Bbappends are making it difficult to reason about what
>> the recipe with all its appends is doing (because they destroy spatial
>> locality and aren't easily visible), and I would actually discourage using
>> them if the modification can go to the original recipe.
>>
> 
> Ok.. you're right. Well at least my answer is not complete ;)
> 
> 
>> Is it fixing a problem? Is it adding a build option absent from the
>> original recipe? Then please take the trouble to submit the change to the
>> owners of the recipe.
>>
> 
> This is correct. We should encourage everyone to report, and even better
> propose a fix, to the relevant layer, when the 'problem' is applicable. I
> didn't want to discourage that, for sure!
> When developing against master, it's a no brainer. When developing against
> a stable branch (like probably many users), it's not as obvious. In that
> case I think trying to avoid 'touching' somebody else layer remains a good
> advice, since it makes upgrades and maintenance trickier.
> 
> 
> 
>>
>> Similarly, if a bbappend is re-setting the component version to something
>> else (yes, people do that despite my best efforts to prohibit the
>> practice), then a much cleaner approach is to actually make a fully copy of
>> the recipe, or go and fix the original.

I just ran across a bbappend that change configure options, but looking
at the original recipe, there is a PACKAGECONFIG option to do the same
thing. So they could have used that mechanism instram of the bbappend.

Philip

>>
> 
> Recipes version upgrades (or downgrade) should be done in a dedicated layer
> owned by the 'developer', and in that case, I agree that bbappend should be
> prohibited, and the entire recipe should be copied.
> 
> 
>> Alex
>>
> 
> 
> 
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49130): https://lists.yoctoproject.org/g/yocto/message/49130
Mute This Topic: https://lists.yoctoproject.org/mt/72982468/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-intel][PATCH] conf:machine: Use weak reference for SERIAL_CONSOLES variable

2020-04-13 Thread Marek Belisko

This add possibility to override in custom layer.

Signed-off-by: Marek Belisko 
---
 conf/machine/intel-core2-32.conf   | 2 +-
 conf/machine/intel-corei7-64.conf  | 2 +-
 conf/machine/intel-skylake-64.conf | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/machine/intel-core2-32.conf b/conf/machine/intel-core2-32.conf
index 20c9872..384ad1e 100644
--- a/conf/machine/intel-core2-32.conf
+++ b/conf/machine/intel-core2-32.conf
@@ -27,7 +27,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \
"
 
 SYSLINUX_OPTS = "serial 0 115200"
-SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyPCH0"
+SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyPCH0"
 APPEND += "rootwait console=ttyS0,115200 console=ttyPCH0,115200 console=tty0"
 
 IMAGE_FSTYPES += "wic"
diff --git a/conf/machine/intel-corei7-64.conf 
b/conf/machine/intel-corei7-64.conf
index 6164bf3..2009537 100644
--- a/conf/machine/intel-corei7-64.conf
+++ b/conf/machine/intel-corei7-64.conf
@@ -32,7 +32,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \
"
 
 SYSLINUX_OPTS = "serial 0 115200"
-SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyS2"
+SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyS2"
 APPEND += "rootwait console=ttyS0,115200 console=tty0"
 
 IMAGE_FSTYPES += "wic"
diff --git a/conf/machine/intel-skylake-64.conf 
b/conf/machine/intel-skylake-64.conf
index e367951..503a982 100644
--- a/conf/machine/intel-skylake-64.conf
+++ b/conf/machine/intel-skylake-64.conf
@@ -25,7 +25,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \
"
 
 SYSLINUX_OPTS = "serial 0 115200"
-SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyS2"
+SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyS2"
 APPEND += "rootwait console=ttyS0,115200 console=tty0"
 
 IMAGE_FSTYPES += "wic"
-- 
2.7.4

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49131): https://lists.yoctoproject.org/g/yocto/message/49131
Mute This Topic: https://lists.yoctoproject.org/mt/73005096/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] meta-intel: Override SERIAL_CONSOLES variable

2020-04-13 Thread Marek Belisko

On Sat, Apr 11, 2020 at 8:09 AM Anuj Mittal  wrote:
>
> Could you send a patch please?
Done: https://lists.yoctoproject.org/g/yocto/message/49131
>
> Thanks,
>
> Anuj
>
> > -Original Message-
> > From: yocto@lists.yoctoproject.org  On Behalf 
> > Of
> > Leon Woestenberg
> > Sent: Saturday, April 11, 2020 04:48 AM
> > To: Marek Belisko 
> > Cc: yocto 
> > Subject: Re: [yocto] meta-intel: Override SERIAL_CONSOLES variable
> >
> > Hi all,
> >
> > On Fri, Apr 10, 2020 at 8:56 AM Marek Belisko  
> > wrote:
> > >
> > > Hi,
> > >
> > > in meta-intel in machine configuration SERIAL_CONSOLES are defined as
> > > : SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyS2"
> > >
> > For a more generic solution, could this be made  a weak assignment?
> >
> > I am on a SMARC x86-64 module which only one serial is useful, so I would 
> > like to
> > downtune this variable as well.
> >
> > Regards,
> >
> > Leon.
> 

BR,

marek
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49132): https://lists.yoctoproject.org/g/yocto/message/49132
Mute This Topic: https://lists.yoctoproject.org/mt/72915847/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-intel][PATCH] conf:machine: Use weak reference for SERIAL_CONSOLES variable

2020-04-13 Thread Anuj Mittal

On Tue, 2020-04-14 at 08:25 +0200, Marek Belisko wrote:
> This add possibility to override in custom layer.
> 
> Signed-off-by: Marek Belisko 
> ---
>  conf/machine/intel-core2-32.conf   | 2 +-
>  conf/machine/intel-corei7-64.conf  | 2 +-
>  conf/machine/intel-skylake-64.conf | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/conf/machine/intel-core2-32.conf b/conf/machine/intel-
> core2-32.conf
> index 20c9872..384ad1e 100644
> --- a/conf/machine/intel-core2-32.conf
> +++ b/conf/machine/intel-core2-32.conf
> @@ -27,7 +27,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \
> "
>  
>  SYSLINUX_OPTS = "serial 0 115200"
> -SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyPCH0"
> +SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyPCH0"

I think having just this would make this statement not do anything as
these machine files includes x86-base.inc which also sets this variable
using a ?=. 

This would probably also need a ??= in x86-base.inc.

Thanks,

Anuj

>  APPEND += "rootwait console=ttyS0,115200 console=ttyPCH0,115200
> console=tty0"
>  
>  IMAGE_FSTYPES += "wic"
> diff --git a/conf/machine/intel-corei7-64.conf b/conf/machine/intel-
> corei7-64.conf
> index 6164bf3..2009537 100644
> --- a/conf/machine/intel-corei7-64.conf
> +++ b/conf/machine/intel-corei7-64.conf
> @@ -32,7 +32,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \
> "
>  
>  SYSLINUX_OPTS = "serial 0 115200"
> -SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyS2"
> +SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyS2"
>  APPEND += "rootwait console=ttyS0,115200 console=tty0"
>  
>  IMAGE_FSTYPES += "wic"
> diff --git a/conf/machine/intel-skylake-64.conf b/conf/machine/intel-
> skylake-64.conf
> index e367951..503a982 100644
> --- a/conf/machine/intel-skylake-64.conf
> +++ b/conf/machine/intel-skylake-64.conf
> @@ -25,7 +25,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \
> "
>  
>  SYSLINUX_OPTS = "serial 0 115200"
> -SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyS2"
> +SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyS2"
>  APPEND += "rootwait console=ttyS0,115200 console=tty0"
>  
>  IMAGE_FSTYPES += "wic"
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49133): https://lists.yoctoproject.org/g/yocto/message/49133
Mute This Topic: https://lists.yoctoproject.org/mt/73005096/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] What is the recommended method to patch a recipe?

Re: [yocto] What is the recommended method to patch a recipe?

Re: [yocto] What is the recommended method to patch a recipe?

Re: [yocto] What is the recommended method to patch a recipe?

Re: [yocto] What is the recommended method to patch a recipe?

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[yocto] Current Top developers on Yocto Project 3.1

[yocto] Enhancements/Bugs closed WW15!

[yocto] M+ & H bugs with Milestone Movements WW15

Re: [yocto] Image size reduction

Re: [yocto] Files get sporadically lost for native packages

Re: [yocto] Files get sporadically lost for native packages

Re: [yocto] What is the recommended method to patch a recipe?

[yocto] [meta-intel][PATCH] conf:machine: Use weak reference for SERIAL_CONSOLES variable

Re: [yocto] meta-intel: Override SERIAL_CONSOLES variable

Re: [yocto] [meta-intel][PATCH] conf:machine: Use weak reference for SERIAL_CONSOLES variable

16 matches

Site Navigation

Mail list logo

Footer information