[yocto] @#NAME type fields

2014-02-20 Thread Meier, Dennis
Good day everyone,

what is the reason for the "#@TYPE", "#@NAME" and "#@DESCRIPTION" fields in the 
machine-*.conf files? Are they getting parsed somewhere? Are they there for 
historical reasons? Could they be extended (i.e. more fields added) without 
problem?

Regards,
Dennis

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


[yocto] No 'directfb' distro feature

2014-02-20 Thread Yang Chengwei
Hi list,

When I was building a core-image-directfb, bitbake failed like below.

-->8--copied from #yocto@irc.freenode--->8

16:16 < chengwei> $ bitbake core-image-directfb
16:16 < chengwei> Loading cache: 100%
|#|
ETA:  00:00:00
16:16 < chengwei> Loaded 1218 entries from dependency cache.
16:16 < chengwei> ERROR: Nothing PROVIDES 'core-image-directfb'
16:16 < chengwei> ERROR: core-image-directfb was skipped: missing
required distro feature ['directfb'] (not in DISTRO_FEATURES)

>8end--->8-

It complained "directfb" not in DISTRO_FEATURES, and that's true.

From the poky source code, I found that there is a commit introduced
change to meta/recipes-graphics/images/core-image-directfb.bb by using
"distro_feature_check", this *does* break the build though it's not the
one to be blamed, the real bug is as bitbake said "there is no directfb
feature" used by core-image-directfb.bb.

Is there a plan to fix this?

--
Thanks,
Chengwei


signature.asc
Description: Digital signature
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] problem with yocto behind http_proxy

2014-02-20 Thread Federico Vitali
Thank you again Laurentiu. I gave it a try, but unfortunately I get an error
message from socat telling that authentication is not supported with SOCKS4.
Reading the man page I saw that athentication is only supported with TCP.


2014-02-19 15:23 GMT+01:00 Laurentiu Palcu :

> On Wed, Feb 19, 2014 at 02:57:49PM +0100, Federico Vitali wrote:
> > I've alreay tried, it doesn't accept it ...
> Apparently, socat has support for authentication. Try this:
>
> #!/bin/bash
> # $1 = hostname, $2 = port
> PROXY=myproxy.example.com
> exec socat STDIO SOCKS4:$PROXY:$1:$2,proxyauth=user:pass
>
> Above is just an example. You'll probably have to adujust it, depending
> on your proxy type. See the manual for details.
>
> laurentiu
> >
> >
> > 2014-02-19 14:51 GMT+01:00 Laurentiu Palcu :
> >
> > On Wed, Feb 19, 2014 at 02:24:38PM +0100, Federico Vitali wrote:
> > > Thank you Laurentiu. Unfortunately my proxy requires
> authentication via
> > > username and password,
> > > but it seems to me that netcat doesn't support it. Or am I wrong?
> > Well, the BSD netcat (on my Ubuntu 12.04) appears to support it:
> >
> > From the man page:
> >  -P proxy_username
> >   Specifies a username to present to a proxy server
> that
> >   requires authentication.  If no username is
> specified
> >   then authentication will not be attempted.  Proxy
> >   authentication is only supported for HTTP CONNECT
> >   proxies at present.
> >
> > Though I don't know how you specify a password... perhaps
> -Puser:passwd?
> >
> > laurentiu
> > >
> > >
> > > 2014-02-19 13:56 GMT+01:00 Laurentiu Palcu <
> laurentiu.pa...@intel.com>:
> > >
> > > Hi Federico,
> > >
> > > You can find more info about setting up Yocto behind proxies
> here:
> > >
> > >
> https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
> > >
> > > For git, I recommend the 'nc' method. Works fine for me.
> > >
> > > laurentiu
> > >
> > > On Wed, Feb 19, 2014 at 12:12:58PM +0100, Federico Vitali
> wrote:
> > > > sorry I forgot to reply also to yocto@yoctoproject.org.
> This was
> > the
> > > reply
> > > >
> > > > thank you Marco,
> > > > I've tried but I'm still having problems:
> > > >
> > > > WARNING: Failed to fetch URL git://git.yoctoproject.org/
> > > yocto-kernel-tools.git,
> > > > attempting MIRRORS if available
> > > > WARNING: Failed to fetch URL git://git.yoctoproject.org/
> > > linux-yocto-3.10.git;
> > > > bareclone=1;branch=standard/base,meta;name=machine,meta,
> attempting
> > > MIRRORS if
> > > > available
> > > > ERROR: Fetcher failure: Fetch command failed with exit code
> 128,
> > output:
> > > > fatal: unable to connect to git.yoctoproject.org:
> > > > git.yoctoproject.org: Name or service not known
> > > >
> > > > I noticed that the url https://www.yoctoproject.org/sourcesis 
> > not
> > > working.
> > > > So I tried  http://downloads.yoctoproject.org/sources/, but
> I get
> > this
> > > error:
> > > >
> > > > ERROR: Fetcher failure: Fetch command failed with exit code
> 128,
> > output:
> > > > fatal: unable to connect to git.yoctoproject.org:
> > > > git.yoctoproject.org: Name or service not known
> > > >
> > > >
> > > >
> > > > 2014-02-19 11:49 GMT+01:00 Marco :
> > > >
> > > > Il 19/02/2014 11:44, Federico Vitali ha scritto:
> > > >
> > > > Hi,
> > > >
> > > > I have problems using yocto behind a firewall. The
> firewall
> > > blocks git,
> > > > so I've followed the instructions
> > > > given here:
> > > >
> > > > http://www.yoctoproject.org/docs/1.5.1/ref-manual/
> > ref-manual.html
> > > #
> > > >
> > >
> >
> how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server
> > > >
> > > > i.e. adding the following lines to my local.conf:
> > > >
> > > > PREMIRRORS_prepend = "\
> > > >   git://.*/.*
> http://www.yoctoproject.org/sources/  \n \
> > > >   ftp://.*/.*
> http://www.yoctoproject.org/sources/  \n \
> > > >   http://.*/.*
> http://www.yoctoproject.org/sources/  \n
> > \
> > > >   https://.*/.*
> http://www.yoctoproject.org/sources/  \
> > n"
> > > >
> > > >
> > > > BB_FETCH_PREMIRRORONLY = "1"
> > > >
> > > >
> > > > but I still get the following errors:
> > > >
> > > >

Re: [yocto] No 'directfb' distro feature

2014-02-20 Thread Paul Eggleton
Hi Chengwei,

On Thursday 20 February 2014 17:27:31 Yang Chengwei wrote:
> When I was building a core-image-directfb, bitbake failed like below.
> 
> -->8--copied from #yocto@irc.freenode--->8
> 
> 16:16 < chengwei> $ bitbake core-image-directfb
> 16:16 < chengwei> Loading cache: 100%
> 
> |###
> |##|
> ETA:  00:00:00
> 16:16 < chengwei> Loaded 1218 entries from dependency cache.
> 16:16 < chengwei> ERROR: Nothing PROVIDES 'core-image-directfb'
> 16:16 < chengwei> ERROR: core-image-directfb was skipped: missing
> required distro feature ['directfb'] (not in DISTRO_FEATURES)
> 
> >8end--->8-
> 
> It complained "directfb" not in DISTRO_FEATURES, and that's true.
> 
> From the poky source code, I found that there is a commit introduced
> change to meta/recipes-graphics/images/core-image-directfb.bb by using
> "distro_feature_check", this *does* break the build though it's not the
> one to be blamed, the real bug is as bitbake said "there is no directfb
> feature" used by core-image-directfb.bb.
> 
> Is there a plan to fix this?

This is not a bug - the intention is that you customise DISTRO_FEATURES to
include the feature if you need it. You may find this section of the manual
useful:

http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#creating-your-own-distribution

Cheers,
Paul


-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] @#NAME type fields

2014-02-20 Thread Paul Eggleton
Hi Dennis,

On Thursday 20 February 2014 09:04:38 Meier, Dennis wrote:
> what is the reason for the "#@TYPE", "#@NAME" and "#@DESCRIPTION" fields in
> the machine-*.conf files? Are they getting parsed somewhere? Are they there
> for historical reasons? Could they be extended (i.e. more fields added)
> without problem?

For a long time I think they were mostly historical - maybe someone else can 
fill in the blanks. I believe the original intention was to provide information 
for other tools that the build system didn't need itself. We are using these 
in a couple of places now that I know of for machine .conf files:

* DESCRIPTION (or NAME, if DESCRIPTION isn't available) are read and used by 
the OpenEmbedded layer index [1]

* I think WEBTITLE is used to specify the title to show up for the BSP when 
listed on the Yocto Project website [2]

Strictly speaking these are just comments, so you could put anything in there 
if you needed to, but if you want something that's going to be adopted by 
other BSP authors it would be worth trying to get some consensus about the 
values used. Currently I don't think we have this documented anywhere, but 
people seem to have been filling in the values because they are there in the 
templates and other BSPs.

Cheers,
Paul

[1] http://layers.openembedded.org/layerindex/branch/master/machines/
[2] https://www.yoctoproject.org/downloads

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] No 'directfb' distro feature

2014-02-20 Thread Yang Chengwei
Hi Paul,

On Thu, Feb 20, 2014 at 10:08:25AM +, Paul Eggleton wrote:
> Hi Chengwei,
> 
> > Is there a plan to fix this?
> 
> This is not a bug - the intention is that you customise DISTRO_FEATURES to
> include the feature if you need it. You may find this section of the manual
> useful:
> 
> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#creating-your-own-distribution

Thank you, I did read developer manual or maybe I missed them? Since
I didn't find 'directfb' as a DISTRO_FEATURES in ref manual, so I
think it's a non-exist feature.  

Is there a way to list all available image features, distro features?

--
Thanks,
Chengwei

> 
> Cheers,
> Paul
> 
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre


signature.asc
Description: Digital signature
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [PATCH][meta-selinux] audit: fix the permission of configuration file

2014-02-20 Thread rongqing.li
From: Roy Li 

Signed-off-by: Roy Li 
---
 .../audit/fix-auditd.conf-file-s-permission.patch  |   41 
 recipes-security/audit/audit_2.3.2.bb  |4 +-
 2 files changed, 44 insertions(+), 1 deletion(-)
 create mode 100644 
recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch

diff --git 
a/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch 
b/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch
new file mode 100644
index 000..be3412b
--- /dev/null
+++ b/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch
@@ -0,0 +1,41 @@
+From abeb7f0e35a4e77e914fea34ddaf8b30b51e49e3 Mon Sep 17 00:00:00 2001
+From: Roy Li 
+Date: Thu, 20 Feb 2014 20:38:31 +0800
+Subject: [PATCH] fix auditd.conf file and path permission
+
+Upstream-Status: Pending
+
+A ordinary use should not to access auditd configuration files
+
+Signed-off-by: Roy Li 
+---
+ init.d/Makefile.am |8 ++--
+ 1 file changed, 6 insertions(+), 2 deletions(-)
+
+diff --git a/init.d/Makefile.am b/init.d/Makefile.am
+index 521dd1d..50728bc 100644
+--- a/init.d/Makefile.am
 b/init.d/Makefile.am
+@@ -37,13 +37,17 @@ endif
+ 
+ auditdir = $(sysconfdir)/audit
+ auditrdir = $(auditdir)/rules.d
+-dist_audit_DATA = auditd.conf
+-dist_auditr_DATA = audit.rules
++auditconfig = auditd.conf
++auditrconfig = audit.rules
+ sbin_SCRIPTS = augenrules
+ 
+ install-data-hook:
+   $(INSTALL_DATA) -D -m 640 ${srcdir}/${dispconfig} 
${DESTDIR}${dispconfigdir}
+   $(INSTALL_DATA) -D -m 640 ${srcdir}/${libconfig} ${DESTDIR}${sysconfdir}
++  $(INSTALL_DATA) -d -m 750 ${DESTDIR}${auditdir}
++  $(INSTALL_DATA) -d -m 750 ${DESTDIR}${auditrdir}
++  $(INSTALL_DATA) -m 640 ${srcdir}/${auditconfig} ${DESTDIR}${auditdir}
++  $(INSTALL_DATA) -m 640 ${srcdir}/${auditrconfig} ${DESTDIR}${auditrdir}
+ if ENABLE_SYSTEMD
+ else
+   $(INSTALL_DATA) -D -m 640 ${srcdir}/auditd.sysconfig 
${DESTDIR}${sysconfigdir}/auditd
+-- 
+1.7.10.4
+
diff --git a/recipes-security/audit/audit_2.3.2.bb 
b/recipes-security/audit/audit_2.3.2.bb
index edcb881..6e376f8 100644
--- a/recipes-security/audit/audit_2.3.2.bb
+++ b/recipes-security/audit/audit_2.3.2.bb
@@ -14,7 +14,9 @@ SRC_URI = 
"http://people.redhat.com/sgrubb/audit/audit-${PV}.tar.gz \
   file://audit-python-configure.patch \
   file://audit-for-cross-compiling.patch \
   file://auditd \
-  file://fix-swig-host-contamination.patch"
+  file://fix-swig-host-contamination.patch \
+  file://fix-auditd.conf-file-s-permission.patch \
+"
 
 inherit autotools pythonnative update-rc.d
 
-- 
1.7.10.4

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


Re: [yocto] No 'directfb' distro feature

2014-02-20 Thread Paul Eggleton
On Thursday 20 February 2014 20:17:23 Yang Chengwei wrote:
> On Thu, Feb 20, 2014 at 10:08:25AM +, Paul Eggleton wrote:
> > > Is there a plan to fix this?
> > 
> > This is not a bug - the intention is that you customise DISTRO_FEATURES to
> > include the feature if you need it. You may find this section of the
> > manual useful:
> > 
> > http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#creati
> > ng-your-own-distribution
>
> Thank you, I did read developer manual or maybe I missed them? Since
> I didn't find 'directfb' as a DISTRO_FEATURES in ref manual, so I
> think it's a non-exist feature.
> 
> Is there a way to list all available image features, distro features?

We should be listing all of the ones we define in the manual, if we aren't we 
need to fix the manual. There isn't really a way to list them in the code 
(other than searching it with "git grep") because the features are only really 
defined by the checks that are made for them e.g. 
${@base_contains('DISTRO_FEATURES', 'systemd', 'true', 'false', d)}

You are of course free to define your own DISTRO_FEATURES simply by checking 
for them in your recipes (where it makes sense; typically PACKAGECONFIG is 
used for configuration options for individual recipes these days and 
DISTRO_FEATURES is left for features that are controlled system-wide).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [PATCH] Ref-manual: fix typo for XDG_RUNTIME_DIR variable value

2014-02-20 Thread Rifenbark, Scott M
Chengwei, 

Thanks for reporting this.  I have applied the patch to both the master (1.6) 
and dora branches of the yocto-docs Git repository.  You can see the change at 
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#running-weston
 and at 
http://www.yoctoproject.org/docs/1.5.1/ref-manual/ref-manual.html#running-weston.
 

Scott

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Chengwei Yang
>Sent: Monday, February 17, 2014 6:19 PM
>To: yocto@yoctoproject.org
>Subject: [yocto] [PATCH] Ref-manual: fix typo for XDG_RUNTIME_DIR variable
>value
>
>Signed-off-by: Chengwei Yang 
>---
> documentation/ref-manual/technical-details.xml |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/documentation/ref-manual/technical-details.xml
>b/documentation/ref-manual/technical-details.xml
>index 51b9148..106bb2c 100644
>--- a/documentation/ref-manual/technical-details.xml
>+++ b/documentation/ref-manual/technical-details.xml
>@@ -1005,7 +1005,7 @@
> 
>  mkdir -p /tmp/$USER-weston
>  chmod 0700 /tmp/$USER-weston
>- export XDG_RUNTIME_DIR=/tmp/$USER=weston
>+ export XDG_RUNTIME_DIR=/tmp/$USER-weston
> 
> Launch Weston in the shell:
> 
>--
>1.7.9.5
>
>___
>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] [eclipse-poky-kepler][PATCH] Fix cloning for a Bitbake Commander Project

2014-02-20 Thread Alexandru Georgescu
Previous commit changed the way YoctoCommand sets a command forcing use of bash.
However cloning a git repo passed the repository as argument, which doesn't 
work anymore,
fix it by using a single command string.

[YOCTO #5757]

Signed-off-by: Alexandru Georgescu 
---
 .../src/org/yocto/bc/ui/wizards/install/InstallWizard.java   | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git 
a/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/InstallWizard.java
 
b/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/InstallWizard.java
index 32a0b4d..f64401c 100644
--- 
a/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/InstallWizard.java
+++ 
b/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/InstallWizard.java
@@ -148,11 +148,10 @@ public class InstallWizard extends FiniteStateWizard 
implements
CommandResponseHandler cmdHandler = new 
CommandResponseHandler(RemoteHelper.getConsole(connection));
IWizardContainer container = this.getContainer();
if (((Boolean)options.get(GIT_CLONE)).booleanValue()) {
-   String cmd = "/usr/bin/git clone --progress";
-   String args = 
"git://git.yoctoproject.org/poky.git " + uri.getPath();
+   String cmd = "git clone --progress 
git://git.yoctoproject.org/poky.git " + uri.getPath();
String taskName = "Checking out Yocto git 
repository";
 
-   YoctoRunnableWithProgress adapter = new 
YoctoRunnableWithProgress(new YoctoCommand(cmd, "", args));
+   YoctoRunnableWithProgress adapter = new 
YoctoRunnableWithProgress(new YoctoCommand(cmd, "", ""));
 
adapter.setRemoteConnection(remoteConnection);
adapter.setRemoteServices(remoteServices);
-- 
1.8.5.3

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


Re: [yocto] [eclipse-poky-kepler][PATCH] Fix cloning for a Bitbake Commander Project

2014-02-20 Thread Zhang, Jessica
Merged to eclipse-poky-kepler master.

Thanks,
Jessica

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Alexandru Georgescu
Sent: Thursday, February 20, 2014 7:11 AM
To: yocto@yoctoproject.org
Subject: [yocto] [eclipse-poky-kepler][PATCH] Fix cloning for a Bitbake 
Commander Project

Previous commit changed the way YoctoCommand sets a command forcing use of bash.
However cloning a git repo passed the repository as argument, which doesn't 
work anymore, fix it by using a single command string.

[YOCTO #5757]

Signed-off-by: Alexandru Georgescu 
---
 .../src/org/yocto/bc/ui/wizards/install/InstallWizard.java   | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git 
a/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/InstallWizard.java
 
b/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/InstallWizard.java
index 32a0b4d..f64401c 100644
--- 
a/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/InstallWizard.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/Instal
+++ lWizard.java
@@ -148,11 +148,10 @@ public class InstallWizard extends FiniteStateWizard 
implements
CommandResponseHandler cmdHandler = new 
CommandResponseHandler(RemoteHelper.getConsole(connection));
IWizardContainer container = this.getContainer();
if (((Boolean)options.get(GIT_CLONE)).booleanValue()) {
-   String cmd = "/usr/bin/git clone --progress";
-   String args = 
"git://git.yoctoproject.org/poky.git " + uri.getPath();
+   String cmd = "git clone --progress 
+git://git.yoctoproject.org/poky.git " + uri.getPath();
String taskName = "Checking out Yocto git 
repository";
 
-   YoctoRunnableWithProgress adapter = new 
YoctoRunnableWithProgress(new YoctoCommand(cmd, "", args));
+   YoctoRunnableWithProgress adapter = new 
+YoctoRunnableWithProgress(new YoctoCommand(cmd, "", ""));
 
adapter.setRemoteConnection(remoteConnection);
adapter.setRemoteServices(remoteServices);
--
1.8.5.3

___
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] [yocto-autobuilder][PATCH] buildsets: add a new buildset to run builds on target

2014-02-20 Thread Stefan Stanacar
Builds core-image-sato-sdk for each qemu arch and
runs tests building sudoku/cvs/iptables.
These do take a while, so they shouldn't be added to nightly!

Signed-off-by: Stefan Stanacar 
---
 .../nightly-qa-targetbuilds.conf   | 26 ++
 1 file changed, 26 insertions(+)
 create mode 100644 buildset-config.master/nightly-qa-targetbuilds.conf

diff --git a/buildset-config.master/nightly-qa-targetbuilds.conf 
b/buildset-config.master/nightly-qa-targetbuilds.conf
new file mode 100644
index 000..a95db78
--- /dev/null
+++ b/buildset-config.master/nightly-qa-targetbuilds.conf
@@ -0,0 +1,26 @@
+[nightly-qa-targetbuilds]
+builders: 'builder1'
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
+ 'branch':'master'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'x86_64', 
'distro': 'poky'}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
+{'BuildImages': {'images': 'core-image-sato-sdk'}},
+{'RunSanityTests': {'images': 'core-image-sato-sdk', 'suites' : 'ping 
ssh buildsudoku buildcvs buildiptables'}},
+{'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'x86_64', 
'distro': 'poky'}},
+{'BuildImages': {'images': 'core-image-sato-sdk'}},
+{'RunSanityTests': {'images': 'core-image-sato-sdk', 'suites' : 'ping 
ssh buildsudoku buildcvs buildiptables'}},
+{'CreateAutoConf': {'machine': 'qemuarm', 'SDKMACHINE' : 'x86_64', 
'distro': 'poky'}},
+{'BuildImages': {'images': 'core-image-sato-sdk'}},
+{'RunSanityTests': {'images': 'core-image-sato-sdk', 'suites' : 'ping 
ssh buildsudoku buildcvs buildiptables'}},
+{'CreateAutoConf': {'machine': 'qemuppc', 'SDKMACHINE' : 'x86_64', 
'distro': 'poky'}},
+{'BuildImages': {'images': 'core-image-sato-sdk'}},
+{'RunSanityTests': {'images': 'core-image-sato-sdk', 'suites' : 'ping 
ssh buildsudoku buildcvs buildiptables'}},
+{'CreateAutoConf': {'machine': 'qemumips', 'SDKMACHINE' : 'x86_64', 
'distro': 'poky'}},
+{'BuildImages': {'images': 'core-image-sato-sdk'}},
+{'RunSanityTests': {'images': 'core-image-sato-sdk', 'suites' : 'ping 
ssh buildsudoku buildcvs buildiptables'}}]
-- 
1.8.5.3

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


[yocto] [yocto-autobuilder][PATCH] Add buildstep and buildset for oe-selftest script

2014-02-20 Thread Stefan Stanacar
This will run the oe-selftest script which has been
available in master for a while. The scripts run a series
of bitbake tests and takes care of it's own config.
Because some of the tests mess up with sstate we
want to use the default sstate dir, so a nosstate option
was added to CreateAutoConf.

Signed-off-by: Stefan Stanacar 
---
 buildset-config.master/nightly-oe-selftest.conf| 15 +
 .../autobuilder/buildsteps/CreateAutoConf.py   |  7 --
 .../autobuilder/buildsteps/RunOeSelftest.py| 26 ++
 3 files changed, 46 insertions(+), 2 deletions(-)
 create mode 100644 buildset-config.master/nightly-oe-selftest.conf
 create mode 100644 
lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py

diff --git a/buildset-config.master/nightly-oe-selftest.conf 
b/buildset-config.master/nightly-oe-selftest.conf
new file mode 100644
index 000..42bccde
--- /dev/null
+++ b/buildset-config.master/nightly-oe-selftest.conf
@@ -0,0 +1,15 @@
+[nightly-oe-selftest]
+builders: 'builder1'
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
+ 'branch':'master'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'x86_64', 
'distro': 'poky', 'nosstate': True, 'packages': 'rpm'}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
+{'BuildImages': {'images': 'core-image-minimal'}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto', 'layerdirs': 
['meta-selftest']}},
+{'RunOeSelftest': {}}]
diff --git 
a/lib/python2.7/site-packages/autobuilder/buildsteps/CreateAutoConf.py 
b/lib/python2.7/site-packages/autobuilder/buildsteps/CreateAutoConf.py
index 116ee14..bec221a 100644
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/CreateAutoConf.py
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/CreateAutoConf.py
@@ -38,6 +38,7 @@ class CreateAutoConf(ShellCommand):
 self.factory = factory
 self.buildappsrcrev = "${AUTOREV}"
 self.initmgr=None
+self.nosstate=False
 self.kwargs = kwargs
 for k, v in argdict.iteritems():
 if type(v) is bool:
@@ -100,9 +101,11 @@ class CreateAutoConf(ShellCommand):
 elif self.multilib == "lib64":
 fout = fout + 'MULTILIBS = "multilib:lib64" \n'
 fout = fout + 'DEFAULTTUNE_virtclass-multilib-lib64 = 
"x86-64" \n'
-fout = fout + 'SSTATE_DIR ?= "' + os.environ.get("SSTATE_DIR") 
+ '/multilib" \n'
+if not self.nosstate:
+fout = fout + 'SSTATE_DIR ?= "' + 
os.environ.get("SSTATE_DIR") + '/multilib" \n'
 else:
-fout = fout + 'SSTATE_DIR ?= "' + os.environ.get("SSTATE_DIR") 
+ '/" \n'
+if not self.nosstate:
+fout = fout + 'SSTATE_DIR ?= "' + 
os.environ.get("SSTATE_DIR") + '/" \n'
 if self.gplv3 == "False":
 fout = fout + 'INCOMPATIBLE_LICENSE = "GPLv3" \n'
 if self.x32 == "True":
diff --git 
a/lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py 
b/lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py
new file mode 100644
index 000..0efddd7
--- /dev/null
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py
@@ -0,0 +1,26 @@
+'''
+__author__ = "Stefan Stanacar"
+__copyright__ = "Copyright 2014 Intel Corporation"
+__credits__ = ["Stefan Stanacar"]
+__license__ = "GPL"
+__version__ = "2.0"
+__maintainer__ = "Stefan Stanacar"
+__email__ = "stefanx.stana...@intel.com"
+'''
+
+
+from buildbot.steps.shell import ShellCommand
+
+class RunOeSelftest(ShellCommand):
+haltOnFailure = False
+flunkOnFailure = True
+name = "Running oe-selftest"
+def __init__(self, factory, argdict=None, **kwargs):
+self.factory = factory
+for k, v in argdict.iteritems():
+setattr(self, k, v)
+self.description = "Running oe-selftest"
+self.timeout = 10
+kwargs['timeout']=self.timeout
+self.command = "if [ -d meta-selftest ]; then . ./oe-init-build-env; 
oe-selftest; else echo 'Skipping step - no meta-selftest layer here'; fi"
+ShellCommand.__init__(self, **kwargs)
-- 
1.8.5.3

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


[yocto] OEDAM: OpenEmbedded Developers (Americas) Meeting

2014-02-20 Thread Philip Balister
The OpenEmbedded Project is holding a developers meeting May 2-3,
2014, in Santa Clara, CA. This meeting is immediately after the Embedded
Linux Conference North America. All active OpenEmbedded and Yocto
Project developers are invited to attend.

NOTE: this is a development meeting for the project itself, not a
training session.

May 2-3, 2014
time TBD

Ettus Research/National Instruments
4600 Patrick Henry Drive
Santa Clara, CA 95054 USA

Lunch will be provided on both days.

For more information and to add yourself to the list of attendees, see
the wiki page at
http://openembedded.org/wiki/OEDAM

Here are a couple of photos from 2009:

http://www.flickr.com/photos/32615155@N00/sets/72157622653686647/

I'd like to thank Jefro for help with this announcement. Any errors are
mine though.

Philip, OpenEmbedded eV Chair.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [PATCH][meta-selinux] audit: fix the permission of configuration file

2014-02-20 Thread Pascal Ouyang

于 14-2-20 下午8:59, rongqing...@windriver.com 写道:

From: Roy Li 

Signed-off-by: Roy Li 
---
  .../audit/fix-auditd.conf-file-s-permission.patch  |   41 
  recipes-security/audit/audit_2.3.2.bb  |4 +-
  2 files changed, 44 insertions(+), 1 deletion(-)
  create mode 100644 
recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch

diff --git 
a/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch 
b/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch
new file mode 100644
index 000..be3412b
--- /dev/null
+++ b/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch
@@ -0,0 +1,41 @@
+From abeb7f0e35a4e77e914fea34ddaf8b30b51e49e3 Mon Sep 17 00:00:00 2001
+From: Roy Li 
+Date: Thu, 20 Feb 2014 20:38:31 +0800
+Subject: [PATCH] fix auditd.conf file and path permission
+
+Upstream-Status: Pending
+
+A ordinary use should not to access auditd configuration files
+
+Signed-off-by: Roy Li 
+---
+ init.d/Makefile.am |8 ++--
+ 1 file changed, 6 insertions(+), 2 deletions(-)
+
+diff --git a/init.d/Makefile.am b/init.d/Makefile.am
+index 521dd1d..50728bc 100644
+--- a/init.d/Makefile.am
 b/init.d/Makefile.am
+@@ -37,13 +37,17 @@ endif
+
+ auditdir = $(sysconfdir)/audit
+ auditrdir = $(auditdir)/rules.d
+-dist_audit_DATA = auditd.conf
+-dist_auditr_DATA = audit.rules
++auditconfig = auditd.conf
++auditrconfig = audit.rules
+ sbin_SCRIPTS = augenrules
+
+ install-data-hook:
+   $(INSTALL_DATA) -D -m 640 ${srcdir}/${dispconfig} 
${DESTDIR}${dispconfigdir}
+   $(INSTALL_DATA) -D -m 640 ${srcdir}/${libconfig} ${DESTDIR}${sysconfdir}
++  $(INSTALL_DATA) -d -m 750 ${DESTDIR}${auditdir}
++  $(INSTALL_DATA) -d -m 750 ${DESTDIR}${auditrdir}
++  $(INSTALL_DATA) -m 640 ${srcdir}/${auditconfig} ${DESTDIR}${auditdir}
++  $(INSTALL_DATA) -m 640 ${srcdir}/${auditrconfig} ${DESTDIR}${auditrdir}
+ if ENABLE_SYSTEMD
+ else
+   $(INSTALL_DATA) -D -m 640 ${srcdir}/auditd.sysconfig 
${DESTDIR}${sysconfigdir}/auditd
+--
+1.7.10.4
+
diff --git a/recipes-security/audit/audit_2.3.2.bb 
b/recipes-security/audit/audit_2.3.2.bb
index edcb881..6e376f8 100644
--- a/recipes-security/audit/audit_2.3.2.bb
+++ b/recipes-security/audit/audit_2.3.2.bb
@@ -14,7 +14,9 @@ SRC_URI = 
"http://people.redhat.com/sgrubb/audit/audit-${PV}.tar.gz \
   file://audit-python-configure.patch \
   file://audit-for-cross-compiling.patch \
   file://auditd \
-  file://fix-swig-host-contamination.patch"
+  file://fix-swig-host-contamination.patch \
+  file://fix-auditd.conf-file-s-permission.patch \
+"

  inherit autotools pythonnative update-rc.d




chmod in do_install is enough, please do not use a patch.

Thanks. :)

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


Re: [yocto] [PATCH][meta-selinux] audit: fix the permission of configuration file

2014-02-20 Thread Rongqing Li



On 02/21/2014 01:53 PM, Pascal Ouyang wrote:

于 14-2-20 下午8:59, rongqing...@windriver.com 写道:

From: Roy Li 

Signed-off-by: Roy Li 
---
  .../audit/fix-auditd.conf-file-s-permission.patch  |   41

  recipes-security/audit/audit_2.3.2.bb  |4 +-
  2 files changed, 44 insertions(+), 1 deletion(-)
  create mode 100644
recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch

diff --git
a/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch
b/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch
new file mode 100644
index 000..be3412b
--- /dev/null
+++
b/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch
@@ -0,0 +1,41 @@
+From abeb7f0e35a4e77e914fea34ddaf8b30b51e49e3 Mon Sep 17 00:00:00 2001
+From: Roy Li 
+Date: Thu, 20 Feb 2014 20:38:31 +0800
+Subject: [PATCH] fix auditd.conf file and path permission
+
+Upstream-Status: Pending
+
+A ordinary use should not to access auditd configuration files
+
+Signed-off-by: Roy Li 
+---
+ init.d/Makefile.am |8 ++--
+ 1 file changed, 6 insertions(+), 2 deletions(-)
+
+diff --git a/init.d/Makefile.am b/init.d/Makefile.am
+index 521dd1d..50728bc 100644
+--- a/init.d/Makefile.am
 b/init.d/Makefile.am
+@@ -37,13 +37,17 @@ endif
+
+ auditdir = $(sysconfdir)/audit
+ auditrdir = $(auditdir)/rules.d
+-dist_audit_DATA = auditd.conf
+-dist_auditr_DATA = audit.rules
++auditconfig = auditd.conf
++auditrconfig = audit.rules
+ sbin_SCRIPTS = augenrules
+
+ install-data-hook:
+ $(INSTALL_DATA) -D -m 640 ${srcdir}/${dispconfig}
${DESTDIR}${dispconfigdir}
+ $(INSTALL_DATA) -D -m 640 ${srcdir}/${libconfig}
${DESTDIR}${sysconfdir}
++$(INSTALL_DATA) -d -m 750 ${DESTDIR}${auditdir}
++$(INSTALL_DATA) -d -m 750 ${DESTDIR}${auditrdir}
++$(INSTALL_DATA) -m 640 ${srcdir}/${auditconfig}
${DESTDIR}${auditdir}
++$(INSTALL_DATA) -m 640 ${srcdir}/${auditrconfig}
${DESTDIR}${auditrdir}
+ if ENABLE_SYSTEMD
+ else
+ $(INSTALL_DATA) -D -m 640 ${srcdir}/auditd.sysconfig
${DESTDIR}${sysconfigdir}/auditd
+--
+1.7.10.4
+
diff --git a/recipes-security/audit/audit_2.3.2.bb
b/recipes-security/audit/audit_2.3.2.bb
index edcb881..6e376f8 100644
--- a/recipes-security/audit/audit_2.3.2.bb
+++ b/recipes-security/audit/audit_2.3.2.bb
@@ -14,7 +14,9 @@ SRC_URI =
"http://people.redhat.com/sgrubb/audit/audit-${PV}.tar.gz \
 file://audit-python-configure.patch \
 file://audit-for-cross-compiling.patch \
 file://auditd \
-   file://fix-swig-host-contamination.patch"
+   file://fix-swig-host-contamination.patch \
+   file://fix-auditd.conf-file-s-permission.patch \
+"

  inherit autotools pythonnative update-rc.d




chmod in do_install is enough, please do not use a patch.



Why ?

-Roy


Thanks. :)



--
Best Reagrds,
Roy | RongQing Li
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [PATCH][meta-selinux] audit: fix the permission of configuration file

2014-02-20 Thread Pascal Ouyang

于 14-2-21 下午3:42, Rongqing Li 写道:



On 02/21/2014 01:53 PM, Pascal Ouyang wrote:

于 14-2-20 下午8:59, rongqing...@windriver.com 写道:

From: Roy Li 

Signed-off-by: Roy Li 
---
  .../audit/fix-auditd.conf-file-s-permission.patch  |   41

  recipes-security/audit/audit_2.3.2.bb  |4 +-
  2 files changed, 44 insertions(+), 1 deletion(-)
  create mode 100644
recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch

diff --git
a/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch
b/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch
new file mode 100644
index 000..be3412b
--- /dev/null
+++
b/recipes-security/audit/audit/fix-auditd.conf-file-s-permission.patch
@@ -0,0 +1,41 @@
+From abeb7f0e35a4e77e914fea34ddaf8b30b51e49e3 Mon Sep 17 00:00:00 2001
+From: Roy Li 
+Date: Thu, 20 Feb 2014 20:38:31 +0800
+Subject: [PATCH] fix auditd.conf file and path permission
+
+Upstream-Status: Pending
+
+A ordinary use should not to access auditd configuration files
+
+Signed-off-by: Roy Li 
+---
+ init.d/Makefile.am |8 ++--
+ 1 file changed, 6 insertions(+), 2 deletions(-)
+
+diff --git a/init.d/Makefile.am b/init.d/Makefile.am
+index 521dd1d..50728bc 100644
+--- a/init.d/Makefile.am
 b/init.d/Makefile.am
+@@ -37,13 +37,17 @@ endif
+
+ auditdir = $(sysconfdir)/audit
+ auditrdir = $(auditdir)/rules.d
+-dist_audit_DATA = auditd.conf
+-dist_auditr_DATA = audit.rules
++auditconfig = auditd.conf
++auditrconfig = audit.rules
+ sbin_SCRIPTS = augenrules
+
+ install-data-hook:
+ $(INSTALL_DATA) -D -m 640 ${srcdir}/${dispconfig}
${DESTDIR}${dispconfigdir}
+ $(INSTALL_DATA) -D -m 640 ${srcdir}/${libconfig}
${DESTDIR}${sysconfdir}
++$(INSTALL_DATA) -d -m 750 ${DESTDIR}${auditdir}
++$(INSTALL_DATA) -d -m 750 ${DESTDIR}${auditrdir}
++$(INSTALL_DATA) -m 640 ${srcdir}/${auditconfig}
${DESTDIR}${auditdir}
++$(INSTALL_DATA) -m 640 ${srcdir}/${auditrconfig}
${DESTDIR}${auditrdir}
+ if ENABLE_SYSTEMD
+ else
+ $(INSTALL_DATA) -D -m 640 ${srcdir}/auditd.sysconfig
${DESTDIR}${sysconfigdir}/auditd
+--
+1.7.10.4
+
diff --git a/recipes-security/audit/audit_2.3.2.bb
b/recipes-security/audit/audit_2.3.2.bb
index edcb881..6e376f8 100644
--- a/recipes-security/audit/audit_2.3.2.bb
+++ b/recipes-security/audit/audit_2.3.2.bb
@@ -14,7 +14,9 @@ SRC_URI =
"http://people.redhat.com/sgrubb/audit/audit-${PV}.tar.gz \
 file://audit-python-configure.patch \
 file://audit-for-cross-compiling.patch \
 file://auditd \
-   file://fix-swig-host-contamination.patch"
+   file://fix-swig-host-contamination.patch \
+   file://fix-auditd.conf-file-s-permission.patch \
+"

  inherit autotools pythonnative update-rc.d




chmod in do_install is enough, please do not use a patch.



Why ?

-Roy


Thanks. :)





Because more patches need more maintain work. It is not unnecessary if 
simple bb modify also work.


Thanks. :)

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