From: Chen Qi
The buildhistory.bbclass always records PV instead of PKGV. However,
the buildhistory-diff script treats PKGV as a monitored variable
instead of PV.
If a recipe's PV changes, for example, hello_1.0.bb is renamed to
hello_2.0.bb, then buildhistory-diff reports nothing because PV is
From: Chen Qi
The following changes since commit 4d8ab87d25ea6e59dc88375813ef88ee0ac813d0:
build-appliance: Update SRCREV (2013-09-24 18:09:12 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/buildhistory
http://git.pokylinux.org/cgit.cgi/poky-co
On 13-09-25 4:59 PM, Richard Purdie wrote:
The existing -cpu host option caused kernel panics when people attempted to use
the kvm option. After research and discussion, the best options appear to
be the kvm32/kvm64 cpu types so lets use these instead. These resolve
the kernel issues for me.
La
From: Jackie Huang
The following changes since commit 821037700ae61fff6a63d4cdb68559c5fcc96fde:
build-appliance: Update SRCREV (2013-09-24 18:08:48 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib jhuang0/d_missing_xz_0926_0
http://git.pokylinux.org/cgi
From: Jackie Huang
xz is required on the target filesystem since it's needed
to unpack some of the bootstrap packages.
Signed-off-by: Jackie Huang
---
.../packagegroups/packagegroup-self-hosted.bb |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/meta/recipes-core/p
From: Roy Li
The default value of SFTPSERVER_PATH is "/usr/libexec/sftp-server" defined in
dropbear-2013.58/option.h, but after commit 406bd38b423[bitbake.conf: change
libexecdir to ${libdir}/${BPN}], sftp-server is provided by openssh package,
and is installed into ${libdir}/openssh, so we pass
On Wed, Sep 25, 2013 at 3:00 PM, Richard Purdie
wrote:
> On Wed, 2013-09-25 at 14:34 -0700, Khem Raj wrote:
>> On Wed, Sep 25, 2013 at 1:59 PM, Richard Purdie
>> wrote:
>> > The existing -cpu host option caused kernel panics when people attempted
>> > to use
>> > the kvm option. After research a
On Wed, 2013-09-25 at 14:34 -0700, Khem Raj wrote:
> On Wed, Sep 25, 2013 at 1:59 PM, Richard Purdie
> wrote:
> > The existing -cpu host option caused kernel panics when people attempted to
> > use
> > the kvm option. After research and discussion, the best options appear to
> > be the kvm32/kvm6
On Wed, Sep 25, 2013 at 1:59 PM, Richard Purdie
wrote:
> The existing -cpu host option caused kernel panics when people attempted to
> use
> the kvm option. After research and discussion, the best options appear to
> be the kvm32/kvm64 cpu types so lets use these instead. These resolve
> the kern
On Wed, 2013-09-25 at 22:09 +0100, Richard Purdie wrote:
> On Wed, 2013-09-25 at 14:05 -0700, Darren Hart wrote:
> > On Wed, 2013-09-25 at 21:59 +0100, Richard Purdie wrote:
> > > The existing -cpu host option caused kernel panics when people attempted
> > > to use
> > > the kvm option. After rese
On Wed, 2013-09-25 at 14:05 -0700, Darren Hart wrote:
> On Wed, 2013-09-25 at 21:59 +0100, Richard Purdie wrote:
> > The existing -cpu host option caused kernel panics when people attempted to
> > use
> > the kvm option. After research and discussion, the best options appear to
> > be the kvm32/kv
On Wed, 2013-09-25 at 21:59 +0100, Richard Purdie wrote:
> The existing -cpu host option caused kernel panics when people attempted to
> use
> the kvm option. After research and discussion, the best options appear to
> be the kvm32/kvm64 cpu types so lets use these instead. These resolve
> the ker
The existing -cpu host option caused kernel panics when people attempted to use
the kvm option. After research and discussion, the best options appear to
be the kvm32/kvm64 cpu types so lets use these instead. These resolve
the kernel issues for me.
[YOCTO #3908]
Signed-off-by: Richard Purdie
--
Richard/Saul,
The patch says it all for this one:
Bumping the 3.10 meta branch SRCREV to import the following config changes
for tghe sugarbay and common-pc wifi fragments.
dad2b7e common-pc-64: add kernel CONFIG options for sugarbay platform
37c617d common-pc-wifi.cfg:
Bumping the 3.10 meta branch SRCREV to import the following config changes
for tghe sugarbay and common-pc wifi fragments.
dad2b7e common-pc-64: add kernel CONFIG options for sugarbay platform
37c617d common-pc-wifi.cfg: add support for broadcom wifi drivers
[YOCTO #5117]
[YOCTO #5238]
Sig
On Sep 25, 2013, at 8:52 AM, Paul Eggleton
wrote:
> On Wednesday 25 September 2013 20:03:19 Muhammad Shakeel wrote:
>> On 09/19/2013 06:03 PM, Shakeel, Muhammad wrote:
>>> From: Muhammad Shakeel
>>>
>>> In some situations ca-certificates are required along with openssl
>>> to communicate secu
busybox 1.21.1 's mdev has changed the way the device's name is
reported so now we get input/event0 instead of event0.
I think this commit is responsible of this new behaviour :
http://git.busybox.net/busybox/commit/util-linux/mdev.c?id=c3cf1e30a3022453311a7e9fe11d94c7a381640e
Update mdev.conf acc
On Wednesday 25 September 2013 20:03:19 Muhammad Shakeel wrote:
> On 09/19/2013 06:03 PM, Shakeel, Muhammad wrote:
> > From: Muhammad Shakeel
> >
> > In some situations ca-certificates are required along with openssl
> > to communicate securely, i.e. curl trying to fetch contents through https.
>
On Wednesday, September 25, 2013, Richard Purdie wrote:
> On Wed, 2013-09-25 at 07:27 -0700, Khem Raj wrote:
> > On Tuesday, September 24, 2013, wrote:
> > From: Roy Li >
> >
> > It is correct behaviours to output help and version
> > information,
> > and should ret
The following changes since commit 4d8ab87d25ea6e59dc88375813ef88ee0ac813d0:
build-appliance: Update SRCREV (2013-09-24 18:09:12 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib lpalcu/b5231_b5259_adt_installer_fixes
http://git.yoctoproject.org/cgit.c
Since the MACHINE can now be specified in adt-installer.conf, in order to
install the proper toolchain and environment script for the given
machine, add a sanity checking at the beginning to make sure MACHINE is
set for the wanted architecture.
Also:
* uncomment the x86 target variables, in adt-i
Currently, if SDK is installed in a directory that needs sudo
preivileges, the target sysroot is also installed with sudo, even though
the location is in users's home directory.
This patch reuses the ownership checking code and uses it to check if
sudo is needed for target sysroot too.
[YOCTO #52
On 09/19/2013 06:03 PM, Shakeel, Muhammad wrote:
From: Muhammad Shakeel
In some situations ca-certificates are required along with openssl
to communicate securely, i.e. curl trying to fetch contents through https.
Signed-off-by: Muhammad Shakeel
---
meta/recipes-connectivity/openssl/openssl
On Wed, 2013-09-25 at 07:27 -0700, Khem Raj wrote:
> On Tuesday, September 24, 2013, wrote:
> From: Roy Li
>
> It is correct behaviours to output help and version
> information,
> and should return 0;
> When input parameter is invalid, print help in
On Tuesday, September 24, 2013, wrote:
> From: Roy Li >
>
> It is correct behaviours to output help and version information,
> and should return 0;
> When input parameter is invalid, print help information and exit.
This can cause gripes for systems who have scripted the old behavior
And since i
We switched to using os.mkdir with the file creation mode specified as the
second parameter. Python masks this with umask behind the scenes which isn't
what we want, we really want the permissions we specify.
To avoid this we zero the umask beforehand and restore afterwards. Other
solutions are po
If sed-native is built before these programs, hardcoded paths to sed-native
can end up in scripts and other parts of the system which may cause issues
if they are later used from sstate and sed-native is not installed.
To avoid this, this patch changes the global site configuration to
specify that
Instead of considering that ping test passed after 1 reply,
wait for at least 5 consecutive replies in 60 seconds (which should
be enough time for connman to reconfigure the interface in systemd
images and help with the fake ssh/tests fails.)
Signed-off-by: Stefan Stanacar
---
meta/lib/oeqa/runt
On 09/25/2013 12:03 PM, Richard Purdie wrote:
On Tue, 2013-09-24 at 16:30 +0200, David Nyström wrote:
I'm have a question about this though.
diff --git a/meta/recipes-extended/shadow/shadow.inc
b/meta/recipes-extended/shadow/shadow.inc
index 4df5e5e..75b0afc 100644
--- a/meta/recipes-extended/s
This is a second in a series of patches to enable
offline rootfs creation from a package repository.
Some postinstall cmds are Yocto specific and needed to create a
rootfs with pre and post install hooks successfully run,
using only the toolchain tarball + a package repo.
End goal is to create a
Add useradd, groupadd et.c. since all target packages
which inherits useradd will have a postinstall hook
dependecy against the yocto specific groupadd.
Signed-off-by: David Nyström
---
meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb | 1 +
1 file changed, 1 insertion(+)
diff
On Tue, 2013-09-24 at 16:30 +0200, David Nyström wrote:
> I'm have a question about this though.
>
> diff --git a/meta/recipes-extended/shadow/shadow.inc
> b/meta/recipes-extended/shadow/shadow.inc
> index 4df5e5e..75b0afc 100644
> --- a/meta/recipes-extended/shadow/shadow.inc
> +++ b/meta/recipe
Strings in Python 3, by default, are assumed to contain unicode
characters. In previous versions of python (<3), unicode strings are
explicitly declared with u"abc". If not, than they're automatically
converted to bytes. This doesn't happen anymore in Python 3.
Since we're dealing with binary file
Tests done:
* installed meta-toolchain using both python 2.7 and 3.2;
* compiled iptables with the installed toolchain;
Thanks,
Laurentiu
The following changes since commit 4d8ab87d25ea6e59dc88375813ef88ee0ac813d0:
build-appliance: Update SRCREV (2013-09-24 18:09:12 +0100)
are available in
34 matches
Mail list logo
