Date   

zypper and poky architectures

Qing He <qing.he@...>
 

I recently reported several zypper bugs specifically for arm, after
some deeper investigation, the problem seems to be of higher level than
I originally thought.

The root cause is that zypper and poky use different way to represent
architectures, as we are putting them together, these two ways are
not compatible, causing many minor glitches that need to modify at
least one of them.

Poky has three kinds of representations in a single target image, which
are independent, cpu-dependent and machine-dependent (all, armv5te,
qemuarm, respectively), e.g.

update-rc.d-0.7-r3.all.rpm
curl-7.21.0-r0.armv5te.rpm
task-base-1.0-r69.qemuarm.rpm

(note that armv5te is the same with gcc's -march option, meaning little
endian)

This is natural until zypper is involved. Zypper supports only one arch
at one time (and this arch should not be changed in fly), and use the
idea of arch compatibility (e.g. _noarch is compatible with _i586), it
then hardcodes the available archs in a different way than poky does,
thus creating several problems:
1. what uses for independent packages is called "noarch", "all" is not
recognized, something depends on update-rc.d won't be installed
because of missing dependency
2. the arch automatic detection system uses "uname -m", thus producing
armv5tejl, which can only be resolved as armv5tel, conflicting with
"armv5te" in rpm
3. many archs are missing in zypper, like mips, armeb, etc.
4. there is no concept of machine-dependent packages (task-base) in
zypper, although we can work around.

Currently, at least zypper is broken on all of mips, arm, ppc, with
slightly different problems.

The ideal situation is to use consistent arch specification, the
following can be a solution:
1. rename *.all.rpm to *.noarch.rpm
2. removing the concept of machine-dependent packages, change all
*.qemuarm.rpm to *.armv5te.rpm
3. enhance zypper arch module, make the addition more flexible,
allowing arch alias (e.g. armv5te = armv5tel = armel = arm)

That would be some work to do, maybe 1.0 is a good time to get zypper
and package upgrade truely working.

Any ideas and comments?

Thanks,
Qing


Please verify the fixed bug in bugzilla.

You, Yongkang <yongkang.you@...>
 

Hi all,

I just had a quick search in bugzilla and found a lot of bugs are resolved but not verified. We'd better to verify the fix before 0.9 launch.

The M4 resolved (but not verified) bugs (88):
http://bugzilla.pokylinux.org/buglist.cgi?bug_status=RESOLVED&query_format=advanced&target_milestone=0.9%20M4&query_based_on=&columnlist=bug_severity%2Creporter%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cproduct%2Ccomponent

All resolved (but not verified) bugs (198):
http://bugzilla.pokylinux.org/buglist.cgi?query_format=advanced&bug_status=RESOLVED

Thanks,
Yongkang


Re: Release checklist

Tian, Kevin <kevin.tian@...>
 

From: Richard Purdie
Sent: Wednesday, October 20, 2010 9:07 PM

Coming up to launch there are going to be some technical things that
need to be done, I'm aiming to write these down and assign owners so we
remember them all and that they all happen:

* Remove password protection from yoctoproject.org (sub)domains [RP]
* Swap default site redirection and name for lists.* and wiki.* [RP]
does this include the content movement from old wiki to the new place?

Thanks
Kevin

* Make meta-demo public [RP]
* Remove password protection from autobuilder [ScottG]
* Upload final version of the eclipse plugin [Jessica]
* Upload final Yocto release images and tarballs [???]

What date and time are we going to actually do these things?

Cheers,

Richard


Re: UPnP demo - call for testing

Xu, Dongxiao <dongxiao.xu@...>
 

Xu, Dongxiao wrote:
I'd also like to have a try, and building the demo image now.

Thanks,
Dongxiao

Joshua Lock wrote:
Hi all,

I've successfully tested the UPnP demo in my office but would
appreciate someone else taking a bash.

Unfortunately you currently need my branch from poky-contrib
(josh/demo) and the corresponding branch from meta-demo (josh/demo).

The renderer and controller are installed together in the
poky-image-rygel image (I've been using the -live variant).

I needed to use amixer to enable the soundcard and increase the
volume on the netbook I was using.

"amixer set Master on
amixer set Master 75"

Run rygel from a terminal and launch gupnp-av-cp and you should be
able to set play music from a content store on the device. I haven't
tested video...
I just setup the environment and gupnp-av-cp could play music from another host within the network. However it seems that video doesn't work yet. Does gupnp-av-cp supports video play?

Thanks,
Dongxiao


I need to tweak the recipes some more so that:
* Rygel is configured and started automatically at boot on the rygel
image
* All of the required recipes are self contained in the master
branch meta-demo overlay.

I think this may mean using bbappend to extend recipes where I've
currently modified them in the main meta overlay, rather than
replication a recipe with the same PN and PV.

I'll probably work on this tomorrow.

Cheers,
Joshua
_______________________________________________
yocto mailing list
yocto@...
https://lists.pokylinux.org/listinfo/yocto


How to create a Blacksand Image with source tarball

Saul Wold <saul.wold@...>
 

Richard, Scott:

Here is what I did to create the blacksand sdk live image with a source tarball. I still need to include the docs and release notes at the top level, but we now have the basic infrastructure in place.

2 changes where required, first to the local.conf file to include the serial port changes (with one additional tweak):

SYSLINUX_OPTS_atom-pc = "serial 0 115200"
SERIAL_CONSOLE_atom-pc = "115200 ttyS0"
APPEND_atom-pc = "console=ttyS0,115200 console=tty0"


And then a new image, that I named poky-image-spec-live, pretty straight forward, we just need to edit the build_src_tarball_bin to include the docs and release notes.

diff --git a/meta/recipes-sato/images/poky-image-spec-live.bb b/meta/recipes-sato/images/poky-image-spec-live.bb
new file mode 100644
index 0000000..1abeb95
--- /dev/null
+++ b/meta/recipes-sato/images/poky-image-spec-live.bb
@@ -0,0 +1,23 @@
+DESCRIPTION = "Bootable Live SDK Image for Atom-PC Board"
+
+require recipes-core/images/poky-image-live.inc
+
+LABELS += "boot install"
+
+ROOTFS = "${DEPLOY_DIR_IMAGE}/poky-image-spec-${MACHINE}.ext3"
+
+LICENSE = "MIT"
+
+PR = "r0"
+
+do_bootimg[depends] += "poky-image-sdk:do_rootfs"
+
+build_src_tarball_bin () {
+ install -d ${S}/hdd/boot
+ (cd ${OEROOT}; git archive HEAD | bzip2 > "${S}/hdd/boot/poky4.tar.bz2")
+}
+
+python do_bootimg_prepend () {
+ import bb
+ bb.build.exec_func('build_src_tarball_bin', d)
+}


Re: UPnP demo - call for testing

Bruce Ashfield <bruce.ashfield@...>
 

On 10-10-20 10:53 PM, Tian, Kevin wrote:
From: Joshua Lock
Sent: Thursday, October 21, 2010 1:19 AM

Hi all,

I've successfully tested the UPnP demo in my office but would appreciate
someone else taking a bash.

Unfortunately you currently need my branch from poky-contrib (josh/demo)
and the corresponding branch from meta-demo (josh/demo).

The renderer and controller are installed together in the
poky-image-rygel image (I've been using the -live variant).

I needed to use amixer to enable the soundcard and increase the volume
on the netbook I was using.

"amixer set Master on
amixer set Master 75"

Run rygel from a terminal and launch gupnp-av-cp and you should be able
to set play music from a content store on the device. I haven't tested
video...

I need to tweak the recipes some more so that:
* Rygel is configured and started automatically at boot on the rygel
image
* All of the required recipes are self contained in the master branch
meta-demo overlay.

I think this may mean using bbappend to extend recipes where I've
currently modified them in the main meta overlay, rather than
replication a recipe with the same PN and PV.

I'll probably work on this tomorrow.
I'd like to understand a full picture of this demo just in case others are
also interested in the test. From what I read so far:
Mark works on an NAS server
Darren covers a media server with mediatomb
Josh sits on UPnP renderer/controller with rygel and gupnp tools

So is the demo chained as below:

NAS server provides media contents which are then found and exported
by mediatomb which then are found by UPnP controller which then points to
the UPnP renderer for final output. Here UPnP controller and renderer may
or may not be the same board.

what Josh wants people to test here is self-contained in one image which
contains both renderer/controller and server (local media files), which hasn't
been connected to other bits yet.

Is above understanding correct?
That matches my understanding.

Bruce


Thanks,
Kevin
_______________________________________________
yocto mailing list
yocto@...
https://lists.pokylinux.org/listinfo/yocto


Re: UPnP demo - call for testing

Tian, Kevin <kevin.tian@...>
 

From: Joshua Lock
Sent: Thursday, October 21, 2010 1:19 AM

Hi all,

I've successfully tested the UPnP demo in my office but would appreciate
someone else taking a bash.

Unfortunately you currently need my branch from poky-contrib (josh/demo)
and the corresponding branch from meta-demo (josh/demo).

The renderer and controller are installed together in the
poky-image-rygel image (I've been using the -live variant).

I needed to use amixer to enable the soundcard and increase the volume
on the netbook I was using.

"amixer set Master on
amixer set Master 75"

Run rygel from a terminal and launch gupnp-av-cp and you should be able
to set play music from a content store on the device. I haven't tested
video...

I need to tweak the recipes some more so that:
* Rygel is configured and started automatically at boot on the rygel
image
* All of the required recipes are self contained in the master branch
meta-demo overlay.

I think this may mean using bbappend to extend recipes where I've
currently modified them in the main meta overlay, rather than
replication a recipe with the same PN and PV.

I'll probably work on this tomorrow.
I'd like to understand a full picture of this demo just in case others are
also interested in the test. From what I read so far:
Mark works on an NAS server
Darren covers a media server with mediatomb
Josh sits on UPnP renderer/controller with rygel and gupnp tools

So is the demo chained as below:

NAS server provides media contents which are then found and exported
by mediatomb which then are found by UPnP controller which then points to
the UPnP renderer for final output. Here UPnP controller and renderer may
or may not be the same board.

what Josh wants people to test here is self-contained in one image which
contains both renderer/controller and server (local media files), which hasn't
been connected to other bits yet.

Is above understanding correct?

Thanks,
Kevin


Re: UPnP demo - call for testing

Xu, Dongxiao <dongxiao.xu@...>
 

I'd also like to have a try, and building the demo image now.

Thanks,
Dongxiao

Joshua Lock wrote:

Hi all,

I've successfully tested the UPnP demo in my office but would
appreciate someone else taking a bash.

Unfortunately you currently need my branch from poky-contrib
(josh/demo) and the corresponding branch from meta-demo (josh/demo).

The renderer and controller are installed together in the
poky-image-rygel image (I've been using the -live variant).

I needed to use amixer to enable the soundcard and increase the
volume on the netbook I was using.

"amixer set Master on
amixer set Master 75"

Run rygel from a terminal and launch gupnp-av-cp and you should be
able to set play music from a content store on the device. I haven't
tested video...

I need to tweak the recipes some more so that:
* Rygel is configured and started automatically at boot on the rygel
image
* All of the required recipes are self contained in the master branch
meta-demo overlay.

I think this may mean using bbappend to extend recipes where I've
currently modified them in the main meta overlay, rather than
replication a recipe with the same PN and PV.

I'll probably work on this tomorrow.

Cheers,
Joshua


Re: UPnP demo - call for testing

Darren Hart <dvhart@...>
 

On 10/20/2010 05:07 PM, Tom Zanussi wrote:
On Wed, 2010-10-20 at 16:48 -0700, Darren Hart wrote:
On 10/20/2010 03:09 PM, Joshua Lock wrote:
On Wed, 2010-10-20 at 18:18 +0100, Joshua Lock wrote:
Hi all,

I've successfully tested the UPnP demo in my office but would appreciate
someone else taking a bash.

Unfortunately you currently need my branch from poky-contrib (josh/demo)
and the corresponding branch from meta-demo (josh/demo).
I've just pushed one change to poky/master and merged a tidied up
changeset into the master branch of meta-demo. So you should now be able
to test with latest poky and meta-demo master.

Cheers,
Joshua
I have added the COMMERCIAL_LICENSE bits to my local.conf and mediatomb
built after that.

building poky-image-rygel-live, gupnp-dlna do_configure is failing with:

configure: error: Package requirements (gstreamer-0.10>=
0.10.29.2) were not met:

No package 'gstreamer-0.10' found

Have you seen that?
I did get that, but IIRC it was because I didn't have the latest
josh/demo branch. Do you have the latest?
He said we should now be able to build from master and meta-demo/master - I refreshed those since he posted that.


Tom

--
Darren Hart
Embedded Linux Kernel


Re: UPnP demo - call for testing

Tom Zanussi <tom.zanussi@...>
 

On Wed, 2010-10-20 at 16:48 -0700, Darren Hart wrote:
On 10/20/2010 03:09 PM, Joshua Lock wrote:
On Wed, 2010-10-20 at 18:18 +0100, Joshua Lock wrote:
Hi all,

I've successfully tested the UPnP demo in my office but would appreciate
someone else taking a bash.

Unfortunately you currently need my branch from poky-contrib (josh/demo)
and the corresponding branch from meta-demo (josh/demo).
I've just pushed one change to poky/master and merged a tidied up
changeset into the master branch of meta-demo. So you should now be able
to test with latest poky and meta-demo master.

Cheers,
Joshua
I have added the COMMERCIAL_LICENSE bits to my local.conf and mediatomb
built after that.

building poky-image-rygel-live, gupnp-dlna do_configure is failing with:

configure: error: Package requirements (gstreamer-0.10 >=
0.10.29.2) were not met:

No package 'gstreamer-0.10' found

Have you seen that?
I did get that, but IIRC it was because I didn't have the latest
josh/demo branch. Do you have the latest?

Tom


Re: UPnP demo - call for testing

Darren Hart <dvhart@...>
 

On 10/20/2010 03:09 PM, Joshua Lock wrote:
On Wed, 2010-10-20 at 18:18 +0100, Joshua Lock wrote:
Hi all,

I've successfully tested the UPnP demo in my office but would appreciate
someone else taking a bash.

Unfortunately you currently need my branch from poky-contrib (josh/demo)
and the corresponding branch from meta-demo (josh/demo).
I've just pushed one change to poky/master and merged a tidied up
changeset into the master branch of meta-demo. So you should now be able
to test with latest poky and meta-demo master.

Cheers,
Joshua
I have added the COMMERCIAL_LICENSE bits to my local.conf and mediatomb built after that.

building poky-image-rygel-live, gupnp-dlna do_configure is failing with:

configure: error: Package requirements (gstreamer-0.10 >=
0.10.29.2) were not met:

No package 'gstreamer-0.10' found

Have you seen that?

--
Darren Hart
Embedded Linux Kernel


Re: UPnP demo - call for testing

Joshua Lock <josh@...>
 

On Wed, 2010-10-20 at 18:18 +0100, Joshua Lock wrote:
Hi all,

I've successfully tested the UPnP demo in my office but would appreciate
someone else taking a bash.

Unfortunately you currently need my branch from poky-contrib (josh/demo)
and the corresponding branch from meta-demo (josh/demo).
I've just pushed one change to poky/master and merged a tidied up
changeset into the master branch of meta-demo. So you should now be able
to test with latest poky and meta-demo master.

Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre


Re: Release checklist

Scott Garman <scott.a.garman@...>
 

On 10/20/2010 09:47 AM, Zhang, Jessica wrote:
Richard Purdie wrote:
Coming up to launch there are going to be some technical things that
need to be done, I'm aiming to write these down and assign owners so
we remember them all and that they all happen:

* Remove password protection from yoctoproject.org (sub)domains [RP]
* Swap default site redirection and name for lists.* and wiki.* [RP]
* Make meta-demo public [RP]
* Remove password protection from autobuilder [ScottG]
* Upload final version of the eclipse plugin [Jessica]
* Upload final Yocto release images and tarballs [???]
Quick question which I think Scott R needs the URLs for his user manual, so
the eclipse plugin will be:
http://yoctoproject.org/downloads/Eclipse-Plugin/

What about everything else, they'll be http://yoctoproject.org/downloads any
subdirectories underneath that?
I've asked these questions among several others in a new thread.

Scott


Re: UPnP demo - call for testing

Kamble, Nitin A <nitin.a.kamble@...>
 

Great job Josh!!! I would have like to give it a try but I don't have a netbook to try. Looks like the drivers will not work on qemu.

Thanks,
Nitin

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Joshua Lock
Sent: Wednesday, October 20, 2010 10:19 AM
To: yocto@...
Subject: [yocto] UPnP demo - call for testing

Hi all,

I've successfully tested the UPnP demo in my office but would appreciate
someone else taking a bash.

Unfortunately you currently need my branch from poky-contrib (josh/demo)
and the corresponding branch from meta-demo (josh/demo).

The renderer and controller are installed together in the
poky-image-rygel image (I've been using the -live variant).

I needed to use amixer to enable the soundcard and increase the volume
on the netbook I was using.

"amixer set Master on
amixer set Master 75"

Run rygel from a terminal and launch gupnp-av-cp and you should be able
to set play music from a content store on the device. I haven't tested
video...

I need to tweak the recipes some more so that:
* Rygel is configured and started automatically at boot on the rygel
image
* All of the required recipes are self contained in the master branch
meta-demo overlay.

I think this may mean using bbappend to extend recipes where I've
currently modified them in the main meta overlay, rather than
replication a recipe with the same PN and PV.

I'll probably work on this tomorrow.

Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre

_______________________________________________
yocto mailing list
yocto@...
https://lists.pokylinux.org/listinfo/yocto


UPnP demo - call for testing

Joshua Lock <josh@...>
 

Hi all,

I've successfully tested the UPnP demo in my office but would appreciate
someone else taking a bash.

Unfortunately you currently need my branch from poky-contrib (josh/demo)
and the corresponding branch from meta-demo (josh/demo).

The renderer and controller are installed together in the
poky-image-rygel image (I've been using the -live variant).

I needed to use amixer to enable the soundcard and increase the volume
on the netbook I was using.

"amixer set Master on
amixer set Master 75"

Run rygel from a terminal and launch gupnp-av-cp and you should be able
to set play music from a content store on the device. I haven't tested
video...

I need to tweak the recipes some more so that:
* Rygel is configured and started automatically at boot on the rygel
image
* All of the required recipes are self contained in the master branch
meta-demo overlay.

I think this may mean using bbappend to extend recipes where I've
currently modified them in the main meta overlay, rather than
replication a recipe with the same PN and PV.

I'll probably work on this tomorrow.

Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre


Re: Release checklist

Dirk Hohndel <hohndel@...>
 

On Wed, 20 Oct 2010 14:07:21 +0100, Richard Purdie <rpurdie@...> wrote:
Coming up to launch there are going to be some technical things that
need to be done, I'm aiming to write these down and assign owners so we
remember them all and that they all happen:

* Remove password protection from yoctoproject.org (sub)domains [RP]
* Swap default site redirection and name for lists.* and wiki.* [RP]
* Make meta-demo public [RP]
* Remove password protection from autobuilder [ScottG]
* Upload final version of the eclipse plugin [Jessica]
* Upload final Yocto release images and tarballs [???]
While not exactly technical, these should be tracked as well:

* post announcement email to LWN [RP or DH]
* post announcement email to... (where else?)
* prior to announcement distribute Q&A inside Intel [TE]

What date and time are we going to actually do these things?
- We should open everything up 4pm UK time on Wednesday
- Post announcements AFTER dinner (so 8pm UK time)

/D


Re: Release checklist

Saul Wold <saul.wold@...>
 

On 10/20/2010 06:07 AM, Richard Purdie wrote:
Coming up to launch there are going to be some technical things that
need to be done, I'm aiming to write these down and assign owners so we
remember them all and that they all happen:

* Remove password protection from yoctoproject.org (sub)domains [RP]
* Swap default site redirection and name for lists.* and wiki.* [RP]
* Make meta-demo public [RP]
* Remove password protection from autobuilder [ScottG]
* Upload final version of the eclipse plugin [Jessica]
* Upload final Yocto release images and tarballs [???]
This should be ScottG also.

What date and time are we going to actually do these things?

Cheers,

Richard



_______________________________________________
yocto mailing list
yocto@...
https://lists.pokylinux.org/listinfo/yocto


Re: Release checklist

Zhang, Jessica
 

Richard Purdie wrote:
Coming up to launch there are going to be some technical things that
need to be done, I'm aiming to write these down and assign owners so
we remember them all and that they all happen:

* Remove password protection from yoctoproject.org (sub)domains [RP]
* Swap default site redirection and name for lists.* and wiki.* [RP]
* Make meta-demo public [RP]
* Remove password protection from autobuilder [ScottG]
* Upload final version of the eclipse plugin [Jessica]
* Upload final Yocto release images and tarballs [???]
Quick question which I think Scott R needs the URLs for his user manual, so
the eclipse plugin will be:
http://yoctoproject.org/downloads/Eclipse-Plugin/

What about everything else, they'll be http://yoctoproject.org/downloads any
subdirectories underneath that?

Thanks,
Jessica


Re: New issue with git fetcher?

Richard Purdie <rpurdie@...>
 

On Wed, 2010-10-20 at 16:20 +0800, Tian, Kevin wrote:
I tried "bitbake poky-image-sdk -c fetchall" both with an existing source directory
and with a fresh new download. Everything works fine.
Thanks for testing and the feedback!

Cheers,

Richard


Release checklist

Richard Purdie <rpurdie@...>
 

Coming up to launch there are going to be some technical things that
need to be done, I'm aiming to write these down and assign owners so we
remember them all and that they all happen:

* Remove password protection from yoctoproject.org (sub)domains [RP]
* Swap default site redirection and name for lists.* and wiki.* [RP]
* Make meta-demo public [RP]
* Remove password protection from autobuilder [ScottG]
* Upload final version of the eclipse plugin [Jessica]
* Upload final Yocto release images and tarballs [???]

What date and time are we going to actually do these things?

Cheers,

Richard

58601 - 58620 of 58675