[yocto] Membership in the OpenEmbedded eV

[Philip Balister]

As regular readers of the lists know, we are having an OpenEmbedded
developer meeting in Dublin Friday (tomorrow). Before starting the
developer part of the meeting the OpenEmbedded eV will hold a short
General Assembly per our statutes.

This organization is responsible for overall administration of he
OpenEmbedded project. We elect the Technical Steering Committee, pay for
DNS and domain registration, organize developer functions and other
administrative functions.

At the general assembly we can vote new members into the organization.
Membership is open to anyone with an interest in the project.

To join, please send me a paragraph describing your interest in the
project and we will vote you in.

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

[yocto] Remove my email from your database

[neerajdadhwal1...@gmail.com]

Sir 
Please remove my email id . Iam frustate with ur unwanted mails.


Sent from my Huawei Mobile
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] can any one please tell the difference between DEPENDS and RDEPENDS

[Alex J Lennon]

On 07/10/2015 07:10, Vivek Per wrote:
> Hi,
>  Can any one please tell the what is the exact difference between
> DEPENDS and RDEPENDS . I am not able to get it . How these variables
> are exactly parsed.
>
>

Vivek - does this help ?

https://lists.yoctoproject.org/pipermail/yocto/2013-August/015783.html

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

Re: [yocto] Can any one please tell the what is the exact difference between DEPENDS and RDEPENDS

[Petter Mabäcker]

 

2015-10-08 06:37 skrev Vivek Per: 

> Hi, 
> Can any one please tell
the what is the exact difference between DEPENDS and RDEPENDS . I am not
able to get it . How these variables are exactly parsed. 
> 
> -regards

> vivek

Hi, 

I guess you already have read through the manual about
the variables?


http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-RDEPENDS


http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-DEPENDS


The overall description of the differences are (please someone
correct me if you find my answer incorrect) that DEPENDS specifics
build-time dependencies (e.i. other recipe files) so you should be
guaranteed that all packages listed in the DEPENDS has been built and
installed in the sysroot before your new package starts its configure
task. 

RDEPENDS on the other hand, is a run-time dependency so instead
of other recipe files RDEPENDS lists packages that should have been
installed in order to correctly run your package on target. 

All this
is explained more in detail in the manual (see above links). Also keep
in mind that DEPENDS works with recipes and RDEPENDS with packages
(which isn't necessary the same). Debug the PACKAGES for a specific
variable
(http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-PACKAGES)
in order to get a clue about what packages a recipe will generate. 

If
you still have a hard to understanding the differences my suggestion is
that you starts playing around a bit with them. Create a project and add
some DEPENDS and RDEPENDS to a recipe(s), build the affected packages
and investigate if they have been built in the expected order. This can
for example be verified by tracking the build output or by looking
through the cooker logs tmp/log/cooker/*. 

BR Petter 

Petter
Mabäcker

Technux 
www.technux.se
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] can any one please tell the difference between DEPENDS and RDEPENDS

[Robert Berger]

On 10/07/2015 09:10 AM, Vivek Per wrote:
> Hi,
>  Can any one please tell the what is the exact difference between
> DEPENDS and RDEPENDS . 

DEPENDS:
http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-DEPENDS

RDEPENDS:
http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-RDEPENDS

> I am not able to get it . How these variables are
> exactly parsed.
> 

Do you need more info?

> 
> regards
> vivek
> 
> 
> -- 
> 

Regards,

Robert


...No matter what the problem is,it's always a people problem.- Jerry
Weinberg

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get=0x90320BF1


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

Re: [yocto] [PATCH 5/7][meta-openembedded] Update nginx to 1.9.5

[Jens Rehsack]

> Am 02.10.2015 um 03:25 schrieb Khem Raj :
> 
> Jens
> 
> 
>> On Oct 1, 2015, at 11:18 AM, Jens Rehsack  wrote:
>> 
>> 
>> many bux-fixes, optmizations and features added:
>> 
>> Changes with nginx 1.9.5 22 Sep 2015
>> 
>> [...]
>>   *) Security: a stack-based buffer overflow might occur in a worker
>>  process while handling a specially crafted request, potentially
>>  resulting in arbitrary code execution (CVE-2013-2028); the bug had
>>  appeared in 1.3.9.
>>  Thanks to Greg MacManus, iSIGHT Partners Labs.
>> 
> 
> 
> This is good info. Although a link to diff in cgit or web view of whatever 
> SCM nginx uses would have done too.

That's simply the Changelog. It's an update, not a fix for a critical issue.
Do you really ask me to list each fixed bug from nginx' ticket list?

>> Signed-off-by: Jens Rehsack 
>> [...]
>> --- a/meta-webserver/recipes-httpd/nginx/nginx_1.4.4.bb
>> +++ /dev/null
> 
> 
> please user git format-patch -M to let git work harder on detecting renames, 
> its way easier to review the changes that way
> this patch belongs to openembedded-devel list so please resend it there with 
> prefixing the layer in meta-openembedded repo [meta-webserver] where the 
> patch is applied.

Sure, will do when I have feedback regarding above question.

Regarding the other 6 patches - is just the right layer and "-M" missing?
Do I have to improve them anyhow (beside what Martin Jansa and Khem criticized: 
missing description here and there)?

>> [...]

Cheers
-- 
Jens Rehsack - rehs...@gmail.com

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

Re: [yocto] [PATCH 5/7][meta-openembedded] Update nginx to 1.9.5

[Khem Raj]

> On Oct 8, 2015, at 7:52 AM, Jens Rehsack  wrote:
> 
> 
>> Am 02.10.2015 um 03:25 schrieb Khem Raj :
>> 
>> Jens
>> 
>> 
>>> On Oct 1, 2015, at 11:18 AM, Jens Rehsack  wrote:
>>> 
>>> 
>>> many bux-fixes, optmizations and features added:
>>> 
>>> Changes with nginx 1.9.5 22 Sep 2015
>>> 
>>> [...]
>>>  *) Security: a stack-based buffer overflow might occur in a worker
>>> process while handling a specially crafted request, potentially
>>> resulting in arbitrary code execution (CVE-2013-2028); the bug had
>>> appeared in 1.3.9.
>>> Thanks to Greg MacManus, iSIGHT Partners Labs.
>>> 
>> 
>> 
>> This is good info. Although a link to diff in cgit or web view of whatever 
>> SCM nginx uses would have done too.
> 
> That's simply the Changelog. It's an update, not a fix for a critical issue.
> Do you really ask me to list each fixed bug from nginx' ticket list?

No, on the contrary, I said if the release published the link for all this 
changes somewhere then just include the link
instead of enumerating changes here.

> 
>>> Signed-off-by: Jens Rehsack 
>>> [...]
>>> --- a/meta-webserver/recipes-httpd/nginx/nginx_1.4.4.bb
>>> +++ /dev/null
>> 
>> 
>> please user git format-patch -M to let git work harder on detecting renames, 
>> its way easier to review the changes that way
>> this patch belongs to openembedded-devel list so please resend it there with 
>> prefixing the layer in meta-openembedded repo [meta-webserver] where the 
>> patch is applied.
> 
> Sure, will do when I have feedback regarding above question.
> 
> Regarding the other 6 patches - is just the right layer and "-M" missing?
> Do I have to improve them anyhow (beside what Martin Jansa and Khem 
> criticized: missing description here and there)?
> 
>>> [...]
> 
> Cheers
> --
> Jens Rehsack - rehs...@gmail.com
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 5/7][meta-openembedded] Update nginx to 1.9.5

[Khem Raj]

> On Oct 8, 2015, at 9:13 AM, Jens Rehsack  wrote:
> 
> 
>> Am 08.10.2015 um 17:05 schrieb Khem Raj :
>> 
 [...]
 This is good info. Although a link to diff in cgit or web view of whatever 
 SCM nginx uses would have done too.
>>> 
>>> That's simply the Changelog. It's an update, not a fix for a critical issue.
>>> Do you really ask me to list each fixed bug from nginx' ticket list?
>> 
>> No, on the contrary, I said if the release published the link for all this 
>> changes somewhere then just include the link
>> instead of enumerating changes here.
> 
> Well, the Changelog changes depending what's published. Currently it's
> http://nginx.org/en/CHANGES - but when a 1.10 or a 2.0 will be released,
> it's going to be http://nginx.org/en/CHANGES-1.9 (but this file currently
> doesn't exists :/)
> 
> Aaand - even if http://nginx.org/en/CHANGES-1.9 would exists, it will
> include even the changes for a potential 1.9.6, 1.9.7 ... regardless
> we have updated to those versions …
> 

sometimes they have them published within the source code repo and that could
be used but if thats not the case its ok.

> I replace the changelog by any URI you prefer - but I favor for
> such circumstances static text ;)
> 

sure.

> Cheers
> --
> Jens Rehsack - rehs...@gmail.com
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 5/7][meta-openembedded] Update nginx to 1.9.5

[Jens Rehsack]

> Am 08.10.2015 um 18:43 schrieb Khem Raj :
> 
>> 
>> On Oct 8, 2015, at 9:13 AM, Jens Rehsack  wrote:
>> 
>> 
>>> Am 08.10.2015 um 17:05 schrieb Khem Raj :
>>> 
> [...]
> This is good info. Although a link to diff in cgit or web view of 
> whatever SCM nginx uses would have done too.
 
 That's simply the Changelog. It's an update, not a fix for a critical 
 issue.
 Do you really ask me to list each fixed bug from nginx' ticket list?
>>> 
>>> No, on the contrary, I said if the release published the link for all this 
>>> changes somewhere then just include the link
>>> instead of enumerating changes here.
>> 
>> Well, the Changelog changes depending what's published. Currently it's
>> http://nginx.org/en/CHANGES - but when a 1.10 or a 2.0 will be released,
>> it's going to be http://nginx.org/en/CHANGES-1.9 (but this file currently
>> doesn't exists :/)
>> 
>> Aaand - even if http://nginx.org/en/CHANGES-1.9 would exists, it will
>> include even the changes for a potential 1.9.6, 1.9.7 ... regardless
>> we have updated to those versions …
>> 
> 
> sometimes they have them published within the source code repo and that could
> be used but if thats not the case its ok.
> 
>> I replace the changelog by any URI you prefer - but I favor for
>> such circumstances static text ;)
>> 
> 
> sure.

So I redo my 7 patches with -M and here and there better description and resent.
Start of next week or so ...

Cheers
-- 
Jens Rehsack - rehs...@gmail.com

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

[yocto] kernel-module- prefix for out-of-tree modules mandatory?

[Daniel.]

Hi all,

Is the kernel-module- prefix mandatory for out-of-tree modules
compiled inside Yocto? And, This prefix applies to package names or
recipe names? Should I rename my recipe file with this prefix or setup
PN stuff?

Cheers,

-- 
"Do or do not. There is no try"
  Yoda Master
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Missing sanity / dependency

[Gary Thomas]

I just ran across this on a [fairly new] system:

$ bitbake meta-toolchain -g -u depexp
Traceback (most recent call last):
  File "/local/poky-cutting-edge/bitbake/bin/bitbake", line 45, in 
cookerdata.CookerConfiguration()))
  File "/local/poky-cutting-edge/bitbake/lib/bb/main.py", line 334, in 
bitbake_main
ui_module = import_extension_module(bb.ui, configParams.ui, 'main')
  File "/local/poky-cutting-edge/bitbake/lib/bb/main.py", line 103, in 
import_extension_module
module = __import__(pkg.__name__, fromlist = [modulename])
  File "/local/poky-cutting-edge/bitbake/lib/bb/ui/depexp.py", line 22, in 

import gtk
ImportError: No module named gtk

Should this have been caught by the sanity checker, or perhaps
handled better?  In my Ubuntu case, I was missing python-gtk2
and friends.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

Re: [yocto] Missing sanity / dependency

[Gary Thomas]

On 2015-10-08 15:40, Burton, Ross wrote:

That bug was fixed some time ago, try updating your clone.  In particular I 
expect your checkout is before poky bb34181b42b62e0476ba9e12f9125ed9f785cf23.


Nope - I'm at master:eac61f37e36099f74485dab398b57f3812826d17 (current tip)
and I still get the same error.


On 8 October 2015 at 21:59, Gary Thomas > wrote:

I just ran across this on a [fairly new] system:

$ bitbake meta-toolchain -g -u depexp
Traceback (most recent call last):
   File "/local/poky-cutting-edge/bitbake/bin/bitbake", line 45, in 
 cookerdata.CookerConfiguration()))
   File "/local/poky-cutting-edge/bitbake/lib/bb/main.py", line 334, in 
bitbake_main
 ui_module = import_extension_module(bb.ui, configParams.ui, 'main')
   File "/local/poky-cutting-edge/bitbake/lib/bb/main.py", line 103, in 
import_extension_module
 module = __import__(pkg.__name__, fromlist = [modulename])
   File "/local/poky-cutting-edge/bitbake/lib/bb/ui/depexp.py", line 22, in 

 import gtk
ImportError: No module named gtk

Should this have been caught by the sanity checker, or perhaps
handled better?  In my Ubuntu case, I was missing python-gtk2
and friends.


--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

Re: [yocto] Missing sanity / dependency

[Burton, Ross]

That bug was fixed some time ago, try updating your clone.  In particular I
expect your checkout is before
poky bb34181b42b62e0476ba9e12f9125ed9f785cf23.

Ross

On 8 October 2015 at 21:59, Gary Thomas  wrote:

> I just ran across this on a [fairly new] system:
>
> $ bitbake meta-toolchain -g -u depexp
> Traceback (most recent call last):
>   File "/local/poky-cutting-edge/bitbake/bin/bitbake", line 45, in 
> cookerdata.CookerConfiguration()))
>   File "/local/poky-cutting-edge/bitbake/lib/bb/main.py", line 334, in
> bitbake_main
> ui_module = import_extension_module(bb.ui, configParams.ui, 'main')
>   File "/local/poky-cutting-edge/bitbake/lib/bb/main.py", line 103, in
> import_extension_module
> module = __import__(pkg.__name__, fromlist = [modulename])
>   File "/local/poky-cutting-edge/bitbake/lib/bb/ui/depexp.py", line 22, in
> 
> import gtk
> ImportError: No module named gtk
>
> Should this have been caught by the sanity checker, or perhaps
> handled better?  In my Ubuntu case, I was missing python-gtk2
> and friends.
>
> --
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Release Candidate Build for yocto-1.7.3.rc1.rc1 now available.

[Poky Build User]

A release candidate build for yocto-1.7.3.rc1 is now available at:

 
http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.3.rc1


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : f9ee1b6139fbc8cadc72278f6ce5ec13c0e74c51 
meta-fsl-arm : db1571f40c375a398a8cdbb42de4c4f272ab0cd1 
meta-minnow : 9c965ef5252e383843d796cd8b50c61b3034b6ae 
meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 
meta-fsl-ppc : 81e39add0400ac7ad547799ada09f5c7475bce95 
poky : b38454c2e3a7a58f5397bb16d59e2b0aa71c4a94 


This is an automated message from
The Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder
Email: elizabeth.flana...@intel.com 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto