On Wed, Jul 16, 2014 at 02:13:54PM +0200, Martin Jansa wrote:
> * standalone libpostproc recipe depends on libav, but current
> PACKAGES_DYNAMIC indicated
> that libav-9.13 also provides libpostproc
ping
>
> Signed-off-by: Martin Jansa
> ---
> meta/recipes-multimedia/libav/libav.inc |
systemd needs this file to be there because one of its configuration file
in pam.d, systemd-user, requires it. Otherwise, we would have errors like
below.
systemd: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth
Signed-off-by: Chen Qi
---
meta/recipes-extended/pam/libpam/pam.
The following changes since commit 4143f3b0ce0d0c52f5b0babc1bb16ac0ac9610eb:
nativesdk-cmake: Adjust toolchain paths dynamically (2014-10-24 21:59:34
+0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib ChenQi/libpam-systemd
http://cgit.open
On Wednesday 29 of October 2014 17:04:20 Tom Zanussi wrote:
> This patchset fixes a couple serious wic bugs:
>
> [YOCTO #6863] - Wic fails to create a working image for a large file system
> [YOCTO #6290] - Update WIC for gummiboot
>
> I generated core-image-sdk images for each of the wic image t
The following changes since commit 4143f3b0ce0d0c52f5b0babc1bb16ac0ac9610eb:
nativesdk-cmake: Adjust toolchain paths dynamically (2014-10-24 21:59:34
+0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib ChenQi/sysstat-tmpfiles
http://cgit.op
In sysvinit, we create /var/log/sa via populate-volatiles.sh script and
/etc/default/volatile/99_sysstat configuration file.
In systemd, we need to create a corresponding configuration file under
/etc/tmpfiles.d in order to create /var/log/sa.
Signed-off-by: Chen Qi
---
meta/recipes-extended/sy
In distributions where /usr/bin/python points at python3, the check for
python version fails even when python2 is available at /usr/bin/python2.
The usual way to circumvent this is to manually create a fake
environment, where python is a symlink to python2. Since openembedded
already sets up a sem
Since more distributions plan to move to python3, steps should be taken
to support such systems.
My previous attemt was pretty intrusive and changed all occurrences of
/usr/bin/{env ,}python to /usr/bin/env python2. Such apporach might break
on systems with no python2 alias in env, so here is a di
To support yocto on systems with python3 as default version, scripts
should use /usr/bin/env python in the shebang, as this allows the use of
a fake env to mimic python2 as default version.
This patch simply replaces occurrences of #!/usr/bin/python with
#!/usr/bin/env python and was done with th
On 29 October 2014 13:18, Martin Hundebøll wrote:
> I used to use a virtualenv to temporarily set Python 2 as the default
>> for the shell in which I ran bitbake commands. That was a while ago
>> though, all my current builds are running on Ubuntu 12.04/14.04 server
>> instances which I access vi
On 28 October 2014 15:05, Gary Thomas wrote:
> Some previous version of this recipe was errantly removing the pygtk-2.0.pc
> (pkg-config) file. This is needed for other packages to be able to build
> against this library.
>
It's deleting the code generator too. This entire recipe gives me the
On 10/30/14, 7:39 AM, Burton, Ross wrote:
On 29 October 2014 13:18, Martin Hundebøll mailto:mar...@hundeboll.net>> wrote:
I used to use a virtualenv to temporarily set Python 2 as the default
for the shell in which I ran bitbake commands. That was a while ago
though, all
On Wed, Aug 06, 2014 at 01:48:31PM +0200, Martin Jansa wrote:
> On Mon, Jul 28, 2014 at 02:18:30PM +0100, Richard Purdie wrote:
> > On Thu, 2014-07-24 at 17:22 +0200, Martin Jansa wrote:
> > > On Thu, Jul 24, 2014 at 02:52:45PM +0100, Burton, Ross wrote:
> > > > On 24 July 2014 14:42, Martin Jansa
> Op 30 okt. 2014, om 10:08 heeft Chen Qi het volgende
> geschreven:
>
> systemd needs this file to be there because one of its configuration file
> in pam.d, systemd-user, requires it. Otherwise, we would have errors like
> below.
>
>systemd: PAM _pam_load_conf_file: unable to open /etc/p
On Thu, 2014-10-30 at 14:20 +0100, Martin Jansa wrote:
> On Wed, Aug 06, 2014 at 01:48:31PM +0200, Martin Jansa wrote:
> > On Mon, Jul 28, 2014 at 02:18:30PM +0100, Richard Purdie wrote:
> > > On Thu, 2014-07-24 at 17:22 +0200, Martin Jansa wrote:
> > > > On Thu, Jul 24, 2014 at 02:52:45PM +0100, B
I have this base script that builds FPGA bitstreams:
https://github.com/topic-embedded-products/meta-topic/blob/master/recipes-bsp/fpga/fpga-image.inc
Now you can have multiple recipes using it, and as such, it seemed a good idea
to add these lines to that recipe:
+ALTERNATIVE_${PN} = "fpga.
Op 30 okt. 2014, om 14:28 heeft Richard Purdie
het volgende geschreven:
> On Thu, 2014-10-30 at 14:20 +0100, Martin Jansa wrote:
>> On Wed, Aug 06, 2014 at 01:48:31PM +0200, Martin Jansa wrote:
>>> On Mon, Jul 28, 2014 at 02:18:30PM +0100, Richard Purdie wrote:
On Thu, 2014-07-24 at 17:22
On Thu, Oct 30, 2014 at 1:57 PM, Burton, Ross wrote:
>
> On 28 October 2014 15:05, Gary Thomas wrote:
>>
>> Some previous version of this recipe was errantly removing the
>> pygtk-2.0.pc
>> (pkg-config) file. This is needed for other packages to be able to build
>> against this library.
>
>
> It
On 2014-10-30 09:26, Andreas Müller wrote:
On Thu, Oct 30, 2014 at 1:57 PM, Burton, Ross wrote:
On 28 October 2014 15:05, Gary Thomas wrote:
Some previous version of this recipe was errantly removing the
pygtk-2.0.pc
(pkg-config) file. This is needed for other packages to be able to build
Hi Paul,
I too wanted to express my thanks to you for this work!
On 10/28/14 19:33, Paul Barker wrote:
> This would be a great time for someone to step up and
> help move things forward to v0.4.0 and beyond.
Is there a roadmap for opkg somewhere?
Best regards,
Trevor
--
___
On Thu, Oct 30, 2014 at 4:39 PM, Gary Thomas wrote:
>
> Wow, since Jan 2013 and no action?
>
> Was this proposed to OE-core (i.e. sent to the list)?
>
No - my expiereineces sending patches to oe-core are not the best.
Usually they just cause me efforts and aren't applied anyway..
Andreas
--
Signed-off-by: Alexandra Safta
---
.../valgrind/remove-ppc64-tests-failing-build.patch | 16
meta/recipes-devtools/valgrind/valgrind_3.9.0.bb | 3 ++-
2 files changed, 18 insertions(+), 1 deletion(-)
create mode 100644
meta/recipes-devtools/valgrind/valgrind/remov
On Thu, 2014-10-30 at 17:14 +0100, Andreas Müller wrote:
> On Thu, Oct 30, 2014 at 4:39 PM, Gary Thomas wrote:
> >
> > Wow, since Jan 2013 and no action?
> >
> > Was this proposed to OE-core (i.e. sent to the list)?
> >
> No - my expiereineces sending patches to oe-core are not the best.
> Usually
On Thu, 2014-10-30 at 15:17 +0100, Mike Looijmans wrote:
> I have this base script that builds FPGA bitstreams:
>
> https://github.com/topic-embedded-products/meta-topic/blob/master/recipes-bsp/fpga/fpga-image.inc
>
> Now you can have multiple recipes using it, and as such, it seemed a good
> i
On Thu, 2014-10-30 at 17:46 +0100, Alexandra Safta wrote:
> Signed-off-by: Alexandra Safta
This removes the tests for all architectures? Why is that a good idea?
At the very least this needs more explanation.
Cheers,
Richard
> .../valgrind/remove-ppc64-tests-failing-build.patch | 16
Folks,
Just a reminder now that master is open again for patches, now is a
great time to consider doing package Updates. Based on some rough
estimates from 1.7 we did around 300 updates from 34 contributors, that
got us about 73% packages upgrades.
We currently have about 180 packages due
On Thu, Oct 30, 2014 at 11:21 AM, Saul Wold wrote:
>
> Folks,
>
> Just a reminder now that master is open again for patches, now is a great
> time to consider doing package Updates. Based on some rough estimates from
> 1.7 we did around 300 updates from 34 contributors, that got us about 73%
> pa
On 30 October 2014 18:21, Saul Wold wrote:
>
> Folks,
>
> Just a reminder now that master is open again for patches, now is a great
> time to consider doing package Updates. Based on some rough estimates from
> 1.7 we did around 300 updates from 34 contributors, that got us about 73%
> packages u
As Paul mentioned yesterday opkg 0.2.4 is on it's way and 0.2.3 has been
available for 2 months. If there are not any objections, I have an updated
recipe and re-created previous patches that I could send. This should also
modify opkg-colateral to use the new syntax for lists_dir.
I would also at t
Writes build information to target filesystem to help developers
[YOCTO #6770]
Signed-off-by: Alejandro Hernandez
---
meta/classes/buildinfo.bbclass | 90 ++
1 file changed, 90 insertions(+)
create mode 100644 meta/classes/buildinfo.bbclass
diff --git a
On 30 October 2014 19:15, Michael Gloff wrote:
> As Paul mentioned yesterday opkg 0.2.4 is on it's way and 0.2.3 has been
> available for 2 months. If there are not any objections, I have an updated
> recipe and re-created previous patches that I could send. This should also
> modify opkg-colatera
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf
> Of Richard Purdie
> Sent: Thursday, October 30, 2014 19:50
> To: Alexandra Safta
> Cc: openembedded-core@lists.openembedded.org
> Subject:
On 10/30/2014 11:21 AM, Saul Wold wrote:
Folks,
Just a reminder now that master is open again for patches, now is a
great time to consider doing package Updates. Based on some rough
estimates from 1.7 we did around 300 updates from 34 contributors, that
got us about 73% packages upgrades.
W
On 10/30/2014 12:07 PM, Paul Barker wrote:
On 30 October 2014 18:21, Saul Wold wrote:
Folks,
Just a reminder now that master is open again for patches, now is a great
time to consider doing package Updates. Based on some rough estimates from
1.7 we did around 300 updates from 34 contributors
Richard,
I did the changes that you suggest and another small changes adding
LIC_FILES_CHKSUM in some recipes to avoid warnings in manifest creation.
I put together into this branch for review,
https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=alimon/license
Best regards.
On 29/1
Writes build information to target filesystem on /etc/build, such as
enabled layers, their current status and commit, squashspaces and outputvars
functions moved from buidlhistory.bbclass to oe/utils.py, to be used by
different classes and avoid code duplication.
[YOCTO #6770]
Signed-off-by
Change since v1:
add python to PACKAGECONFIG.
The following changes since commit 4faca22b8fe63a86d820990207aaf84b3fa83e01:
ref-manual: Updates to the migrating to YP 1.7 section. (2014-10-28 22:31:18
+)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib chongl
From: Robert Yang
We have libxml2-python for native and nativesdk, but don't have it for
target, and can't find the reason from the git log, libxml2-python is
widely used, after looked into it's configure.in, we can add it
by PACKAGECONFIG.
The previous --with-python=${STAGING_BINDIR}/python is
On 10/30/2014 09:27 PM, Koen Kooi wrote:
Op 30 okt. 2014, om 10:08 heeft Chen Qi het volgende
geschreven:
systemd needs this file to be there because one of its configuration file
in pam.d, systemd-user, requires it. Otherwise, we would have errors like
below.
systemd: PAM _pam_load_conf_
On 10/31/2014 10:59 AM, ChenQi wrote:
On 10/30/2014 09:27 PM, Koen Kooi wrote:
Op 30 okt. 2014, om 10:08 heeft Chen Qi het
volgende geschreven:
systemd needs this file to be there because one of its configuration
file
in pam.d, systemd-user, requires it. Otherwise, we would have errors
like
The service file should be included in bluez4 package, not in plugin package.
This solves the following warning:
WARNING: QA Issue: gst-plugin-bluetooth: Files/directories were installed but
not shipped
/lib
/lib/systemd
/lib/systemd/system
/lib/systemd/system/bluetooth.service [installe
The following changes since commit f19b4e995ea47f9243f152b39337330307453c9f:
bitbake: bitbake: clarify startup message (2014-10-30 13:39:52 +)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib chonglu/gst
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=
42 matches
Mail list logo
