[yocto] [PATCH] nightly-world-lsb.conf: Do world builds for poky-lsb
[YOCTO #7261]
Do world builds for poky-lsb. This patch adds the new nightly-world-lsb buildset
to fix bug #7261. Also added it to the normal nightly.conf trigger
and yoctoAB.conf.
Signed-off-by: Graydon, Tracy
---
buildset-config.controller/nightly-world-lsb.conf | 22 ++
buildset-config.controller/nightly.conf | 2 +-
buildset-config.controller/yoctoAB.conf | 6 +++---
3 files changed, 26 insertions(+), 4 deletions(-)
create mode 100644 buildset-config.controller/nightly-world-lsb.conf
diff --git a/buildset-config.controller/nightly-world-lsb.conf
b/buildset-config.controller/nightly-world-lsb.conf
new file mode 100644
index 000..e9782a9
--- /dev/null
+++ b/buildset-config.controller/nightly-world-lsb.conf
@@ -0,0 +1,22 @@
+[nightly-world-lsb]
+builders: 'example-worker'
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
+ 'branch':'master'}},
+{'meta-qt3':
+{'repourl':'git://git.yoctoproject.org/meta-qt3',
+ 'branch':'master'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'x86_64',
+'buildhistory' : False, 'multilib': True,
+'distro': 'poky-lsb'}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
+{'BuildImages': {'images': 'world'}},
+{'SendErrorReport': {}},
+{'UploadToasterEventlog': {}},
+{'PublishArtifacts': {'artifacts': ['ipk', 'rpm', 'deb']}}]
+
diff --git a/buildset-config.controller/nightly.conf
b/buildset-config.controller/nightly.conf
index e8498f1..cf7c77c 100644
--- a/buildset-config.controller/nightly.conf
+++ b/buildset-config.controller/nightly.conf
@@ -87,7 +87,7 @@ steps: [{'SetDest':{}},
'schedulerNames_nowait' : {'build-appliance': {},
'eclipse-plugin-kepler': {}, 'eclipse-plugin-juno':
{},
'nightly-non-gpl3': {}, 'nightly-oecore': {},
- 'nightly-world':{}, 'nightly-intel-gpl': {},
+ 'nightly-world':{}, 'nightly-world-lsb':{},
'nightly-intel-gpl': {},
'poky-tiny': {}, 'buildtools': {},
'nightly-qa-systemd': {}, 'nightly-qa-extras': {},
'nightly-qa-logrotate': {}, 'nightly-qa-pam': {},
diff --git a/buildset-config.controller/yoctoAB.conf
b/buildset-config.controller/yoctoAB.conf
index 9a07512..5bc369d 100644
--- a/buildset-config.controller/yoctoAB.conf
+++ b/buildset-config.controller/yoctoAB.conf
@@ -5,6 +5,6 @@ order: ['nightly', 'eclipse-plugin-juno',
'nightly-mips-lsb', 'nightly-ppc', 'nightly-ppc-lsb',
'nightly-x86-64', 'nightly-x86-64-lsb', 'nightly-x86',
'nightly-x86-lsb', 'nightly-x32', 'nightly-multilib',
-'nightly-world', 'nightly-non-gpl3', 'nightly-oecore',
-'nightly-intel-gpl', 'poky-tiny', 'build-appliance',
-'nightly-qa-extras', 'nightly-qa-systemd']
+'nightly-world', 'nightly-world-lsb', 'nightly-non-gpl3',
+'nightly-oecore', 'nightly-intel-gpl', 'poky-tiny',
+'build-appliance', 'nightly-qa-extras', 'nightly-qa-systemd']
--
1.9.3
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] populate_sysroot and sstate question
Poky Daisy 1.6.1
I have a custom package of font files and a custom recipe to install then
into ${libdir}/fonts.
I don't want these files in the sysroot, as they are not necessary there,
they are only required on the target, and they make the SDK larger.
In my recipe, I defined an empty populate_sysroot task to override the
default behavior of copying the font files to sysroot (presumably because
they are in ${libdir}).
Today, I came across the fact that this results in an empty populate_sysroot
sstate tarball, which causes a setscene error if I need to use the sstate for
that package later.
Is there a better way to suppress populate_sysroot without breaking
setscene?
MV
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] nightly-world-lsb.conf: Do world builds for poky-lsb
Crap. You are right. There is a change in here that shouldn¹t be. Fixing
that.
Thank you for catching that. I was on the wrong local branch.
-t
On 03/24/15, 2:51 PM, "Randy Witt" wrote:
>On 03/24/2015 03:41 PM, Graydon, Tracy wrote:
>> [YOCTO #7261]
>>
>> Do world builds for poky-lsb. This patch adds the new nightly-world-lsb
>>buildset
>> to fix bug #7261. Also added it to the normal nightly.conf trigger
>> and yoctoAB.conf.
>>
>> Signed-off-by: Graydon, Tracy
>> ---
>> buildset-config.controller/nightly-world-lsb.conf | 22
>>++
>> buildset-config.controller/nightly.conf | 4 +---
>> buildset-config.controller/yoctoAB.conf | 6 +++---
>> 3 files changed, 26 insertions(+), 6 deletions(-)
>> create mode 100644 buildset-config.controller/nightly-world-lsb.conf
>>
>> diff --git a/buildset-config.controller/nightly-world-lsb.conf
>>b/buildset-config.controller/nightly-world-lsb.conf
>> new file mode 100644
>> index 000..e9782a9
>> --- /dev/null
>> +++ b/buildset-config.controller/nightly-world-lsb.conf
>> @@ -0,0 +1,22 @@
>> +[nightly-world-lsb]
>> +builders: 'example-worker'
>> +repos: [{'poky':
>> +{'repourl':'git://git.yoctoproject.org/poky',
>> + 'layerversion':{'core':'meta',
>>'yoctobsp':'meta-yocto-bsp'},
>> + 'branch':'master'}},
>> +{'meta-qt3':
>> +{'repourl':'git://git.yoctoproject.org/meta-qt3',
>> + 'branch':'master'}}]
>> +steps: [{'SetDest':{}},
>> +{'CheckOutLayers': {}},
>> +{'RunPreamble': {}},
>> +{'GetDistroVersion' : {'distro': 'poky'}},
>> +{'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' :
>>'x86_64',
>> +'buildhistory' : False, 'multilib': True,
>> +'distro': 'poky-lsb'}},
>> +{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
>> +{'BuildImages': {'images': 'world'}},
>> +{'SendErrorReport': {}},
>> +{'UploadToasterEventlog': {}},
>> +{'PublishArtifacts': {'artifacts': ['ipk', 'rpm', 'deb']}}]
>> +
>> diff --git a/buildset-config.controller/nightly.conf
>>b/buildset-config.controller/nightly.conf
>> index e8498f1..e422ede 100644
>> --- a/buildset-config.controller/nightly.conf
>> +++ b/buildset-config.controller/nightly.conf
>> @@ -75,10 +75,8 @@ steps: [{'SetDest':{}},
>> {'BuildImages': {'images': 'universe -c fetch'}},
>> {'TriggerBuilds': {'schedulerName': 'main-build',
>>'waitForFinish': 'True',
>> 'schedulerNames': {'minnow': {},
>>'minnow-lsb': {},
>> - 'nightly-arm': {}, 'nightly-arm-lsb': {},
>> 'nightly-fsl-arm': {},
>>'nightly-fsl-arm-lsb': {},
>> 'nightly-fsl-ppc': {},
>>'nightly-fsl-ppc-lsb': {},
>> - 'nightly-mips': {}, 'nightly-mips-lsb': {},
>
>I'll admit that I'm not that familiar with the autobuilder, but this
>looks like
>some builds are being turned off, but the commit message doesn't mention
>that.
>
>> 'nightly-multilib': {}, 'nightly-x32': {},
>> 'nightly-ppc': {}, 'nightly-ppc-lsb': {},
>> 'nightly-x86-64': {},
>>'nightly-x86-64-lsb': {},
>> @@ -87,7 +85,7 @@ steps: [{'SetDest':{}},
>> 'schedulerNames_nowait' :
>>{'build-appliance': {},
>> 'eclipse-plugin-kepler': {},
>>'eclipse-plugin-juno': {},
>> 'nightly-non-gpl3': {}, 'nightly-oecore':
>>{},
>> - 'nightly-world':{}, 'nightly-intel-gpl': {},
>> + 'nightly-world':{}, 'nightly-world-lsb':{},
>>'nightly-intel-gpl': {},
>> 'poky-tiny': {}, 'buildtools': {},
>> 'nightly-qa-systemd': {},
>>'nightly-qa-extras': {},
>> 'nightly-qa-logrotate': {},
>>'nightly-qa-pam': {},
>> diff --git a/buildset-config.controller/yoctoAB.conf
>>b/buildset-config.controller/yoctoAB.conf
>> index 9a07512..c087628 100644
>> --- a/buildset-config.controller/yoctoAB.conf
>> +++ b/buildset-config.controller/yoctoAB.conf
>> @@ -1,10 +1,10 @@
>> [BuildSets]
>> order: ['nightly', 'eclipse-plugin-juno',
>> 'eclipse-plugin-kepler', 'eclipse-plugin-luna',
>> -'nightly-arm', 'nightly-arm-lsb', 'nightly-mips',
>> -'nightly-mips-lsb', 'nightly-ppc', 'nightly-ppc-lsb',
>> +'nightly-ppc', 'nightly-ppc-lsb',
>> 'nightly-x86-64', 'nightly-x86-64-lsb', 'nightly-x86',
>> 'nightly-x86-lsb', 'nightly-x32', 'nightly-multilib',
>> -'nightly-world', 'nightly-non-gpl3', 'nightly-oecore',
>> +'nightly-world', 'nightly-world-lsb',
>> +'nightly-non-gpl3', 'nightly-oecore',
>> 'nightly-intel-gpl', 'poky-tiny', 'build-appliance',
>> 'nightly-
Re: [yocto] nightly-world-lsb.conf: Do world builds for poky-lsb
On 03/24/2015 03:41 PM, Graydon, Tracy wrote:
[YOCTO #7261]
Do world builds for poky-lsb. This patch adds the new nightly-world-lsb buildset
to fix bug #7261. Also added it to the normal nightly.conf trigger
and yoctoAB.conf.
Signed-off-by: Graydon, Tracy
---
buildset-config.controller/nightly-world-lsb.conf | 22 ++
buildset-config.controller/nightly.conf | 4 +---
buildset-config.controller/yoctoAB.conf | 6 +++---
3 files changed, 26 insertions(+), 6 deletions(-)
create mode 100644 buildset-config.controller/nightly-world-lsb.conf
diff --git a/buildset-config.controller/nightly-world-lsb.conf
b/buildset-config.controller/nightly-world-lsb.conf
new file mode 100644
index 000..e9782a9
--- /dev/null
+++ b/buildset-config.controller/nightly-world-lsb.conf
@@ -0,0 +1,22 @@
+[nightly-world-lsb]
+builders: 'example-worker'
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
+ 'branch':'master'}},
+{'meta-qt3':
+{'repourl':'git://git.yoctoproject.org/meta-qt3',
+ 'branch':'master'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'x86_64',
+'buildhistory' : False, 'multilib': True,
+'distro': 'poky-lsb'}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
+{'BuildImages': {'images': 'world'}},
+{'SendErrorReport': {}},
+{'UploadToasterEventlog': {}},
+{'PublishArtifacts': {'artifacts': ['ipk', 'rpm', 'deb']}}]
+
diff --git a/buildset-config.controller/nightly.conf
b/buildset-config.controller/nightly.conf
index e8498f1..e422ede 100644
--- a/buildset-config.controller/nightly.conf
+++ b/buildset-config.controller/nightly.conf
@@ -75,10 +75,8 @@ steps: [{'SetDest':{}},
{'BuildImages': {'images': 'universe -c fetch'}},
{'TriggerBuilds': {'schedulerName': 'main-build', 'waitForFinish':
'True',
'schedulerNames': {'minnow': {}, 'minnow-lsb': {},
- 'nightly-arm': {}, 'nightly-arm-lsb': {},
'nightly-fsl-arm': {}, 'nightly-fsl-arm-lsb': {},
'nightly-fsl-ppc': {}, 'nightly-fsl-ppc-lsb': {},
- 'nightly-mips': {}, 'nightly-mips-lsb': {},
I'll admit that I'm not that familiar with the autobuilder, but this looks like
some builds are being turned off, but the commit message doesn't mention that.
'nightly-multilib': {}, 'nightly-x32': {},
'nightly-ppc': {}, 'nightly-ppc-lsb': {},
'nightly-x86-64': {}, 'nightly-x86-64-lsb': {},
@@ -87,7 +85,7 @@ steps: [{'SetDest':{}},
'schedulerNames_nowait' : {'build-appliance': {},
'eclipse-plugin-kepler': {},
'eclipse-plugin-juno': {},
'nightly-non-gpl3': {}, 'nightly-oecore': {},
- 'nightly-world':{}, 'nightly-intel-gpl': {},
+ 'nightly-world':{}, 'nightly-world-lsb':{},
'nightly-intel-gpl': {},
'poky-tiny': {}, 'buildtools': {},
'nightly-qa-systemd': {}, 'nightly-qa-extras': {},
'nightly-qa-logrotate': {}, 'nightly-qa-pam': {},
diff --git a/buildset-config.controller/yoctoAB.conf
b/buildset-config.controller/yoctoAB.conf
index 9a07512..c087628 100644
--- a/buildset-config.controller/yoctoAB.conf
+++ b/buildset-config.controller/yoctoAB.conf
@@ -1,10 +1,10 @@
[BuildSets]
order: ['nightly', 'eclipse-plugin-juno',
'eclipse-plugin-kepler', 'eclipse-plugin-luna',
-'nightly-arm', 'nightly-arm-lsb', 'nightly-mips',
-'nightly-mips-lsb', 'nightly-ppc', 'nightly-ppc-lsb',
+'nightly-ppc', 'nightly-ppc-lsb',
'nightly-x86-64', 'nightly-x86-64-lsb', 'nightly-x86',
'nightly-x86-lsb', 'nightly-x32', 'nightly-multilib',
-'nightly-world', 'nightly-non-gpl3', 'nightly-oecore',
+'nightly-world', 'nightly-world-lsb',
+'nightly-non-gpl3', 'nightly-oecore',
'nightly-intel-gpl', 'poky-tiny', 'build-appliance',
'nightly-qa-extras', 'nightly-qa-systemd']
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] nightly-world-lsb.conf: Do world builds for poky-lsb
[YOCTO #7261]
Do world builds for poky-lsb. This patch adds the new nightly-world-lsb buildset
to fix bug #7261. Also added it to the normal nightly.conf trigger
and yoctoAB.conf.
Signed-off-by: Graydon, Tracy
---
buildset-config.controller/nightly-world-lsb.conf | 22 ++
buildset-config.controller/nightly.conf | 4 +---
buildset-config.controller/yoctoAB.conf | 6 +++---
3 files changed, 26 insertions(+), 6 deletions(-)
create mode 100644 buildset-config.controller/nightly-world-lsb.conf
diff --git a/buildset-config.controller/nightly-world-lsb.conf
b/buildset-config.controller/nightly-world-lsb.conf
new file mode 100644
index 000..e9782a9
--- /dev/null
+++ b/buildset-config.controller/nightly-world-lsb.conf
@@ -0,0 +1,22 @@
+[nightly-world-lsb]
+builders: 'example-worker'
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
+ 'branch':'master'}},
+{'meta-qt3':
+{'repourl':'git://git.yoctoproject.org/meta-qt3',
+ 'branch':'master'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'x86_64',
+'buildhistory' : False, 'multilib': True,
+'distro': 'poky-lsb'}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
+{'BuildImages': {'images': 'world'}},
+{'SendErrorReport': {}},
+{'UploadToasterEventlog': {}},
+{'PublishArtifacts': {'artifacts': ['ipk', 'rpm', 'deb']}}]
+
diff --git a/buildset-config.controller/nightly.conf
b/buildset-config.controller/nightly.conf
index e8498f1..e422ede 100644
--- a/buildset-config.controller/nightly.conf
+++ b/buildset-config.controller/nightly.conf
@@ -75,10 +75,8 @@ steps: [{'SetDest':{}},
{'BuildImages': {'images': 'universe -c fetch'}},
{'TriggerBuilds': {'schedulerName': 'main-build', 'waitForFinish':
'True',
'schedulerNames': {'minnow': {}, 'minnow-lsb': {},
- 'nightly-arm': {}, 'nightly-arm-lsb': {},
'nightly-fsl-arm': {}, 'nightly-fsl-arm-lsb': {},
'nightly-fsl-ppc': {}, 'nightly-fsl-ppc-lsb': {},
- 'nightly-mips': {}, 'nightly-mips-lsb': {},
'nightly-multilib': {}, 'nightly-x32': {},
'nightly-ppc': {}, 'nightly-ppc-lsb': {},
'nightly-x86-64': {}, 'nightly-x86-64-lsb': {},
@@ -87,7 +85,7 @@ steps: [{'SetDest':{}},
'schedulerNames_nowait' : {'build-appliance': {},
'eclipse-plugin-kepler': {}, 'eclipse-plugin-juno':
{},
'nightly-non-gpl3': {}, 'nightly-oecore': {},
- 'nightly-world':{}, 'nightly-intel-gpl': {},
+ 'nightly-world':{}, 'nightly-world-lsb':{},
'nightly-intel-gpl': {},
'poky-tiny': {}, 'buildtools': {},
'nightly-qa-systemd': {}, 'nightly-qa-extras': {},
'nightly-qa-logrotate': {}, 'nightly-qa-pam': {},
diff --git a/buildset-config.controller/yoctoAB.conf
b/buildset-config.controller/yoctoAB.conf
index 9a07512..c087628 100644
--- a/buildset-config.controller/yoctoAB.conf
+++ b/buildset-config.controller/yoctoAB.conf
@@ -1,10 +1,10 @@
[BuildSets]
order: ['nightly', 'eclipse-plugin-juno',
'eclipse-plugin-kepler', 'eclipse-plugin-luna',
-'nightly-arm', 'nightly-arm-lsb', 'nightly-mips',
-'nightly-mips-lsb', 'nightly-ppc', 'nightly-ppc-lsb',
+'nightly-ppc', 'nightly-ppc-lsb',
'nightly-x86-64', 'nightly-x86-64-lsb', 'nightly-x86',
'nightly-x86-lsb', 'nightly-x32', 'nightly-multilib',
-'nightly-world', 'nightly-non-gpl3', 'nightly-oecore',
+'nightly-world', 'nightly-world-lsb',
+'nightly-non-gpl3', 'nightly-oecore',
'nightly-intel-gpl', 'poky-tiny', 'build-appliance',
'nightly-qa-extras', 'nightly-qa-systemd']
--
1.9.3
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] poky.conf: Flip DISTRO_VERSION for pending 1.8 release
Flipping DISTRO_VERSION for fido.
Signed-off-by: Beth Flanagan
---
meta-yocto/conf/distro/poky.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf
index 66c7b4c..34d4f37 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -1,6 +1,6 @@
DISTRO = "poky"
DISTRO_NAME = "Poky (Yocto Project Reference Distro)"
-DISTRO_VERSION = "1.7+snapshot-${DATE}"
+DISTRO_VERSION = "1.8"
DISTRO_CODENAME = "fido"
SDK_VENDOR = "-pokysdk"
SDK_VERSION := "${@'${DISTRO_VERSION}'.replace('snapshot-${DATE}','snapshot')}"
--
1.9.1
-
Intel Ireland Limited (Branch)
Collinstown Industrial Park, Leixlip, County Kildare, Ireland
Registered Number: E902934
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Embedded Linux Package Management
Hi Prasant, On Fri, 2015-03-20 at 11:14 +, Paul Eggleton wrote: > On Friday 20 March 2015 11:10:39 Paul Eggleton wrote: > > On Friday 20 March 2015 11:26:43 Alex J Lennon wrote: > > > On 20/03/2015 11:15, Prasant J wrote: > > > > On Fri, Mar 20, 2015 at 2:21 PM, Alex J Lennon > > > > > > > > wrote: > > > >> On 20/03/2015 09:34, Prasant J wrote: > > > >> > > > >> Hi, > > > >> > > > >> I'm looking for package management for my embedded linux systems > > > >> (yocto on armv7 iMX6Q) > > > >> > > > >> > > > >> I'm looking for the following features: > > > >> > > > >> (a) Install & remove a package > > > >> (b) Install packages and its dependencies > > > >> (c) Install a package with conflicts, such that the conflicting > > > >> package is force removed > > > >> (d) A local location with packages should serve as a package source > > > >> (e) Remote server package (http file server based) > > > >> (f) List of my packages installed > > > >> (g) List of my packages not installed but available on the http file > > > >> server > > > >> (h) List of my packages that have updates (new version) > > > >> (i) To be able to manage packages for multiple architectures (eg. rpm > > > >> can produce packages for multiple architectures using one spec file) > > > >> This list of requirements you put seem very helpful from the package management standpoint although I believe this can all be done in a couple of scripting lines at the most, if you're with Yum/RPM anyway. > > > >> > > > >> The above features will be invoked by the application GUI. > > > >> Any suggestions: which package management solution would answer all > > > >> the above use cases? > > > >> > > > >> > > > >> > > > >> (e) I use smart + RPM. I have a remote package server setup via this in > > > >> local.conf > > > >> > > > >> FEED_DEPLOYDIR_BASE_URI = "http://packages.foo.bar"; > > > >> > > > >> Then I'm rsyncing the files up to the server after a bitbake > > > >> package-index. > > > >> > > > >> Then smart update / search / install > > > >> > > > >> That seems to work well in my testing. > > > > > > > > Hi Alex, > > > > > > > > Thanks for inputs! > > > > > > > > Is smart development stopped? > > > > > > > > When I look at their mailing list it, the last posts were in Nov 2014. > > > > It looks like no more development for smart package manager. I would > > > > then tend to say that it will not be a right way for me. > > > > > > I don't know. To me the question would be does it do want I need it to > > > do as well as I need it to do it, > > > rather than asking whether there is a lot of activity. One might take > > > the view that if it is doing its job, > > > a lack of activity is a sign that it's a mature piece of software that > > > needs little further development. > > > > > > You'll have to make that decision yourself. > > > > > > My understanding is that smart is the recommended way to do things (at > > > least it was what was > > > recommended to me) - https://wiki.yoctoproject.org/wiki/Smart > > > > FYI, here is some of the thinking that led to the decision to use smart: > > > > https://lists.yoctoproject.org/pipermail/yocto/2012-October/010384.html > > > > Of course that was a few years ago now - we probably ought to look at the > > RPM landscape again (e.g. DNF) and see if any change is warranted. > > I forgot to mention, we do have some basic documentation here on > setting up a feed if you hadn't already seen it: > > http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management > > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Embedded Linux Package Management
On 3/21/15 3:40 AM, Prasant J wrote: > On Fri, Mar 20, 2015 at 4:44 PM, Paul Eggleton > wrote: >> On Friday 20 March 2015 11:10:39 Paul Eggleton wrote: >>> On Friday 20 March 2015 11:26:43 Alex J Lennon wrote: On 20/03/2015 11:15, Prasant J wrote: > On Fri, Mar 20, 2015 at 2:21 PM, Alex J Lennon I don't know. To me the question would be does it do want I need it to do as well as I need it to do it, rather than asking whether there is a lot of activity. One might take the view that if it is doing its job, a lack of activity is a sign that it's a mature piece of software that needs little further development. You'll have to make that decision yourself. My understanding is that smart is the recommended way to do things (at least it was what was recommended to me) - https://wiki.yoctoproject.org/wiki/Smart > > @Alex: > You are correct, it should be able to do what I need. > It did most of the things that I need. > > But I'm not fine in using a package if the development has stopped. > Smart may stop development but other packages continue to develop. > It is important for me to know that the maintainer will continue to provide > compliance as other libraries are actively developed. This is an open source project. The Yocto Project developers will do they're best to stand behind the technology that has been selected and have plans to continue to fix defects, improve (as appropriate), and continue to evaluate options moving forward. But at this time, SmartPM is still the best answer for our present needs, when RPM is selected as the package type. You are welcome to provide your own package management front end, and/or port components like DNF into the environment. There is nothing stopping you other then time and resources (the same constrains we are under.) We do welcome contributions and enhancements from community members, but don't expect us to select technology on a whim. Usually we have a good reason to select something, community input, requirements from members, or simply familiarity with the code. The SmartPM project itself is on a downward swing, however it does everything we need it to do. (One exception would be DeltaRPM support.. but frankly it's been a low priority for people for a while now...) SmartPM also has the advantage that it's python and small. Some of the other technologies, such as Zypper were tried, and failed due to the, IMHO, onerous requirements that it's support libraries, such as Boost and libstdc++, put onto the environment. YUM is simply not easily compatible with RPM5 and their community had been actively hostile to RPM5 development. SmartPM was simple, fast, and easy to modify -- with a community that didn't mind change. (DNF did not yet, exist at the time of the decision -- it was being discussed, but it's only been recently that it has advanced to a point where it can be seriously investigated as a possible alternative.) Also if you don't like SmartPM/RPM, you can always use IPK. But you will give up some of the capabilities that RPM brings to the table. (Note, I believe IPK is a better solution for smaller environments, while RPM is a better solution for medium to large environments.) > >>> >>> FYI, here is some of the thinking that led to the decision to use smart: >>> >>> https://lists.yoctoproject.org/pipermail/yocto/2012-October/010384.html >>> >>> Of course that was a few years ago now - we probably ought to look at the >>> RPM landscape again (e.g. DNF) and see if any change is warranted. > > @Paul: > This is a very important link for me. This posts points out that yum > will not be compatible with rpm ver 5. > This will be a problem for me as my imx6 yocto build uses rpm5. So > technically I cannot use yum. > >> >> I forgot to mention, we do have some basic documentation here on >> setting up a feed if you hadn't already seen it: >> >> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management >> > > > Thanks for inputs. Would like to get more inputs from community. > > Looks like Alex is successful and happy in using smart + rpm. I would > re-consider smart + rpm for my solution. I have no heard any serious complaints about SmartPM, other then concern of community decline. I use SmartPM/RPM5 (and intend to continue for the forseeable future) in supporting on-target field upgrade solutions. So far this has turned out to be much easier to support and work on unique requirements my customers have based on the simplicity of the Smart implementation. --Mark > Anyone else using any other package management solution ? > > > Regards, Pj > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Mar. 24, 2015 8:00 AM US Pacific Time
Attendees: Armin, Stephen, Saul, Beth, Bruce, Mark, Richard, Ross, Paul, Alex, Brendan, Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.8_Status https://wiki.yoctoproject.org/wiki/Yocto_1.8_Schedule https://wiki.yoctoproject.org/wiki/Yocto_1.8_Features YP 1.8 M4 rc1 build should be ready to go into QA by tomorrow. YP 1.6.3 rc2 is coming out of QA soon. But, its release might be delayed due to a recent SSL CVE. Saul and others will review and decide if it need to be held and rebuild and rerun through QA. Might delay this until early May. YP 1.7.2 is planned for May. If 1.6.3 is delayed it might push 1.7.2 until mid/late May. * SWAT team rotation: Saul -> Paul/Ross https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team * Opens - 10 min * Team Sharing - 10 min Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone: (503) 712-0534 *Cell:(208) 244-4460 * Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] make sound work out of the box for raspberrypi2
On 24/03/2015 12:21, Gary Thomas wrote: > On 2015-03-24 02:40, Alex J Lennon wrote: >> >> >> On 24/03/2015 09:21, Alex J Lennon wrote: >>> >>> On 24/03/2015 08:21, Andreas Müller wrote: On Tue, Mar 24, 2015 at 12:14 AM, Gary Thomas wrote: > On 2015-03-23 16:22, Andreas Müller wrote: >> On Mon, Mar 23, 2015 at 10:43 PM, Gary Thomas >> wrote: >>> On 2015-03-23 14:57, Andreas Müller wrote: On Mon, Mar 23, 2015 at 4:59 PM, Gary Thomas wrote: > On 2015-03-22 14:21, Andreas Müller wrote: >> >> Signed-off-by: Andreas Müller >> --- >> ...-during-boot-by-compiling-SND_BCM2835-int.patch | 38 >> ++ >> recipes-kernel/linux/linux-raspberrypi_3.18.bb | 8 >> +++-- >> 2 files changed, 43 insertions(+), 3 deletions(-) >> create mode 100644 >> >> >> recipes-kernel/linux/linux-raspberrypi/0001-start-sound-during-boot-by-compiling-SND_BCM2835-int.patch >> > > > I tried this patch (which downloaded very strangely using > Thunderbird) > and > the > kernel rebuilt fine. I now have the audio detected, but still > no sound > :-( > Again I've tried the internal (phono) speakers as well as HDMI > audio. > > Just to prove a point on the [brand new] hardware, I installed > OpenELEC > (XBMC) > and it works fine using the HDMI audio. Sadly when I tried > Raspbian > and > Ubuntu > there was no sound either... > > Were you (Andreas) able to get any sound with this patch? > Yes but I have used 3.5mm sound output - Should have mentioned that in commit. I guess there is to enable something else in kernel config for HDMI. Will look into that >>> >>> I've tried the 3.5mm jack as well but nothing seems to come out. >>> I even tried booting with the HDMI missing (powered off) in case >>> that was causing some confusion. >>> >>> Did you make any changes to config.txt to get this going? >> No >> Have my standard xfce-image with xfce4-mixer and as mentioned out of >> the box: I can hear sound / change volume... > Would it be possible to share your [bootable] image? > >> What does happen if you start alsamixer - if it is installed on your >> image? > alsamixer looks correct. > > BTW, I've tried this on my RaspberryPi Model B and I don't get any > sound > from it either :-( Again, booting with test_mode=1 shows that the > hardware > is working, just not in Linux. I'm sure I've tried this in the > past with > success so I'm becoming more and more confused... > For sharing I need to create a smaller image - the current one contains all stuff from meta-games, all browsers and more. Hope to get that done tomorrow evening. What is the preferred way of sharing huge files? >>> Circling around this a little, hello_audio built out of vc_graphics >>> works too over the audio jack >>> >>> Alex >>> >> >> OK I got some life from GStreamer and my RPIv2 >> >> Install amixer >> >> modprobe snd_bcm2835 (or presumably use an image with audio built-in) >> >> amixer cset numid=3 1 (to set output to audio jack) >> >> gst-launch-1.0 audiotestsrc ! alsasink >> >> I get a tone out of the audio jack. So some kind of audio routing >> defaults issue. > > Indeed, this does work - tested on RaspberryPi and RaspberryPi2. > > Now, to figure out how to make audio over HDMI work. > I don't have HDMI audio kit with me here but there are some bits and bobs here which might help http://raspberrypi.stackexchange.com/questions/22708/is-there-some-trick-to-getting-aplay-audio-output-working I'd be wont to try |amixer cset numid=3 2| For starters to try to force HDMI output Some other bits and pieces on ALSA in there I see, which might be relevant Cheers, Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] make sound work out of the box for raspberrypi2
On 2015-03-24 02:40, Alex J Lennon wrote: On 24/03/2015 09:21, Alex J Lennon wrote: On 24/03/2015 08:21, Andreas Müller wrote: On Tue, Mar 24, 2015 at 12:14 AM, Gary Thomas wrote: On 2015-03-23 16:22, Andreas Müller wrote: On Mon, Mar 23, 2015 at 10:43 PM, Gary Thomas wrote: On 2015-03-23 14:57, Andreas Müller wrote: On Mon, Mar 23, 2015 at 4:59 PM, Gary Thomas wrote: On 2015-03-22 14:21, Andreas Müller wrote: Signed-off-by: Andreas Müller --- ...-during-boot-by-compiling-SND_BCM2835-int.patch | 38 ++ recipes-kernel/linux/linux-raspberrypi_3.18.bb | 8 +++-- 2 files changed, 43 insertions(+), 3 deletions(-) create mode 100644 recipes-kernel/linux/linux-raspberrypi/0001-start-sound-during-boot-by-compiling-SND_BCM2835-int.patch I tried this patch (which downloaded very strangely using Thunderbird) and the kernel rebuilt fine. I now have the audio detected, but still no sound :-( Again I've tried the internal (phono) speakers as well as HDMI audio. Just to prove a point on the [brand new] hardware, I installed OpenELEC (XBMC) and it works fine using the HDMI audio. Sadly when I tried Raspbian and Ubuntu there was no sound either... Were you (Andreas) able to get any sound with this patch? Yes but I have used 3.5mm sound output - Should have mentioned that in commit. I guess there is to enable something else in kernel config for HDMI. Will look into that I've tried the 3.5mm jack as well but nothing seems to come out. I even tried booting with the HDMI missing (powered off) in case that was causing some confusion. Did you make any changes to config.txt to get this going? No Have my standard xfce-image with xfce4-mixer and as mentioned out of the box: I can hear sound / change volume... Would it be possible to share your [bootable] image? What does happen if you start alsamixer - if it is installed on your image? alsamixer looks correct. BTW, I've tried this on my RaspberryPi Model B and I don't get any sound from it either :-( Again, booting with test_mode=1 shows that the hardware is working, just not in Linux. I'm sure I've tried this in the past with success so I'm becoming more and more confused... For sharing I need to create a smaller image - the current one contains all stuff from meta-games, all browsers and more. Hope to get that done tomorrow evening. What is the preferred way of sharing huge files? Circling around this a little, hello_audio built out of vc_graphics works too over the audio jack Alex OK I got some life from GStreamer and my RPIv2 Install amixer modprobe snd_bcm2835 (or presumably use an image with audio built-in) amixer cset numid=3 1 (to set output to audio jack) gst-launch-1.0 audiotestsrc ! alsasink I get a tone out of the audio jack. So some kind of audio routing defaults issue. Indeed, this does work - tested on RaspberryPi and RaspberryPi2. Now, to figure out how to make audio over HDMI work. -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Iptables kernel mode driver
Hi, I am building with dizzy with hob, a core-image-minimal with machine generic-x86-64 (kernel 3.14) with addition of iptables, iproute2 and some netfilter extensions. I can add the kernel-module-xt-classify, kernel-module-x-tables but i cannot find *kernel-module-xt-physdev *(via the build package). Can someone please help to point me the right direction? Thanks. Regards, Albert. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] make sound work out of the box for raspberrypi2
On 24/03/2015 09:21, Alex J Lennon wrote: > > On 24/03/2015 08:21, Andreas Müller wrote: >> On Tue, Mar 24, 2015 at 12:14 AM, Gary Thomas wrote: >>> On 2015-03-23 16:22, Andreas Müller wrote: On Mon, Mar 23, 2015 at 10:43 PM, Gary Thomas wrote: > On 2015-03-23 14:57, Andreas Müller wrote: >> On Mon, Mar 23, 2015 at 4:59 PM, Gary Thomas wrote: >>> On 2015-03-22 14:21, Andreas Müller wrote: Signed-off-by: Andreas Müller --- ...-during-boot-by-compiling-SND_BCM2835-int.patch | 38 ++ recipes-kernel/linux/linux-raspberrypi_3.18.bb | 8 +++-- 2 files changed, 43 insertions(+), 3 deletions(-) create mode 100644 recipes-kernel/linux/linux-raspberrypi/0001-start-sound-during-boot-by-compiling-SND_BCM2835-int.patch >>> >>> >>> I tried this patch (which downloaded very strangely using Thunderbird) >>> and >>> the >>> kernel rebuilt fine. I now have the audio detected, but still no sound >>> :-( >>> Again I've tried the internal (phono) speakers as well as HDMI audio. >>> >>> Just to prove a point on the [brand new] hardware, I installed OpenELEC >>> (XBMC) >>> and it works fine using the HDMI audio. Sadly when I tried Raspbian >>> and >>> Ubuntu >>> there was no sound either... >>> >>> Were you (Andreas) able to get any sound with this patch? >>> >> Yes but I have used 3.5mm sound output - Should have mentioned that in >> commit. I guess there is to enable something else in kernel config for >> HDMI. Will look into that > > I've tried the 3.5mm jack as well but nothing seems to come out. > I even tried booting with the HDMI missing (powered off) in case > that was causing some confusion. > > Did you make any changes to config.txt to get this going? No Have my standard xfce-image with xfce4-mixer and as mentioned out of the box: I can hear sound / change volume... >>> Would it be possible to share your [bootable] image? >>> What does happen if you start alsamixer - if it is installed on your image? >>> alsamixer looks correct. >>> >>> BTW, I've tried this on my RaspberryPi Model B and I don't get any sound >>> from it either :-( Again, booting with test_mode=1 shows that the hardware >>> is working, just not in Linux. I'm sure I've tried this in the past with >>> success so I'm becoming more and more confused... >>> >> For sharing I need to create a smaller image - the current one >> contains all stuff from meta-games, all browsers and more. Hope to get >> that done tomorrow evening. What is the preferred way of sharing huge >> files? >> > Circling around this a little, hello_audio built out of vc_graphics > works too over the audio jack > > Alex > OK I got some life from GStreamer and my RPIv2 Install amixer modprobe snd_bcm2835 (or presumably use an image with audio built-in) amixer cset numid=3 1 (to set output to audio jack) gst-launch-1.0 audiotestsrc ! alsasink I get a tone out of the audio jack. So some kind of audio routing defaults issue. Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] make sound work out of the box for raspberrypi2
On 24/03/2015 08:21, Andreas Müller wrote: > On Tue, Mar 24, 2015 at 12:14 AM, Gary Thomas wrote: >> On 2015-03-23 16:22, Andreas Müller wrote: >>> On Mon, Mar 23, 2015 at 10:43 PM, Gary Thomas wrote: On 2015-03-23 14:57, Andreas Müller wrote: > > On Mon, Mar 23, 2015 at 4:59 PM, Gary Thomas wrote: >> >> On 2015-03-22 14:21, Andreas Müller wrote: >>> >>> >>> Signed-off-by: Andreas Müller >>> --- >>> ...-during-boot-by-compiling-SND_BCM2835-int.patch | 38 >>> ++ >>> recipes-kernel/linux/linux-raspberrypi_3.18.bb | 8 +++-- >>> 2 files changed, 43 insertions(+), 3 deletions(-) >>> create mode 100644 >>> >>> >>> recipes-kernel/linux/linux-raspberrypi/0001-start-sound-during-boot-by-compiling-SND_BCM2835-int.patch >> >> >> >> I tried this patch (which downloaded very strangely using Thunderbird) >> and >> the >> kernel rebuilt fine. I now have the audio detected, but still no sound >> :-( >> Again I've tried the internal (phono) speakers as well as HDMI audio. >> >> Just to prove a point on the [brand new] hardware, I installed OpenELEC >> (XBMC) >> and it works fine using the HDMI audio. Sadly when I tried Raspbian >> and >> Ubuntu >> there was no sound either... >> >> Were you (Andreas) able to get any sound with this patch? >> > Yes but I have used 3.5mm sound output - Should have mentioned that in > commit. I guess there is to enable something else in kernel config for > HDMI. Will look into that I've tried the 3.5mm jack as well but nothing seems to come out. I even tried booting with the HDMI missing (powered off) in case that was causing some confusion. Did you make any changes to config.txt to get this going? >>> No >>> Have my standard xfce-image with xfce4-mixer and as mentioned out of >>> the box: I can hear sound / change volume... >> >> Would it be possible to share your [bootable] image? >> >>> What does happen if you start alsamixer - if it is installed on your >>> image? >> >> alsamixer looks correct. >> >> BTW, I've tried this on my RaspberryPi Model B and I don't get any sound >> from it either :-( Again, booting with test_mode=1 shows that the hardware >> is working, just not in Linux. I'm sure I've tried this in the past with >> success so I'm becoming more and more confused... >> > For sharing I need to create a smaller image - the current one > contains all stuff from meta-games, all browsers and more. Hope to get > that done tomorrow evening. What is the preferred way of sharing huge > files? > Circling around this a little, hello_audio built out of vc_graphics works too over the audio jack Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] make sound work out of the box for raspberrypi2
On Tue, Mar 24, 2015 at 12:14 AM, Gary Thomas wrote: > On 2015-03-23 16:22, Andreas Müller wrote: >> >> On Mon, Mar 23, 2015 at 10:43 PM, Gary Thomas wrote: >>> >>> On 2015-03-23 14:57, Andreas Müller wrote: On Mon, Mar 23, 2015 at 4:59 PM, Gary Thomas wrote: > > > On 2015-03-22 14:21, Andreas Müller wrote: >> >> >> >> Signed-off-by: Andreas Müller >> --- >> ...-during-boot-by-compiling-SND_BCM2835-int.patch | 38 >> ++ >> recipes-kernel/linux/linux-raspberrypi_3.18.bb | 8 +++-- >> 2 files changed, 43 insertions(+), 3 deletions(-) >> create mode 100644 >> >> >> recipes-kernel/linux/linux-raspberrypi/0001-start-sound-during-boot-by-compiling-SND_BCM2835-int.patch > > > > > I tried this patch (which downloaded very strangely using Thunderbird) > and > the > kernel rebuilt fine. I now have the audio detected, but still no sound > :-( > Again I've tried the internal (phono) speakers as well as HDMI audio. > > Just to prove a point on the [brand new] hardware, I installed OpenELEC > (XBMC) > and it works fine using the HDMI audio. Sadly when I tried Raspbian > and > Ubuntu > there was no sound either... > > Were you (Andreas) able to get any sound with this patch? > Yes but I have used 3.5mm sound output - Should have mentioned that in commit. I guess there is to enable something else in kernel config for HDMI. Will look into that >>> >>> >>> >>> I've tried the 3.5mm jack as well but nothing seems to come out. >>> I even tried booting with the HDMI missing (powered off) in case >>> that was causing some confusion. >>> >>> Did you make any changes to config.txt to get this going? >> >> No >>> >>> >> Have my standard xfce-image with xfce4-mixer and as mentioned out of >> the box: I can hear sound / change volume... > > > Would it be possible to share your [bootable] image? > >> >> What does happen if you start alsamixer - if it is installed on your >> image? > > > alsamixer looks correct. > > BTW, I've tried this on my RaspberryPi Model B and I don't get any sound > from it either :-( Again, booting with test_mode=1 shows that the hardware > is working, just not in Linux. I'm sure I've tried this in the past with > success so I'm becoming more and more confused... > For sharing I need to create a smaller image - the current one contains all stuff from meta-games, all browsers and more. Hope to get that done tomorrow evening. What is the preferred way of sharing huge files? Andreas -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
