Signed-off-by: Martin Jansa
---
meta-systemd/conf/layer.conf |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta-systemd/conf/layer.conf b/meta-systemd/conf/layer.conf
index d07d2ad..9caec69 100644
--- a/meta-systemd/conf/layer.conf
+++ b/meta-systemd/conf/layer.conf
@@
I'm trying to build OE classic for i.MX28, following instructions at:
http://www.imxdev.org/wiki/index.php?title=All_Boards_OpenEmbedded
I'm trying to run:
bitbake bootstrap-image
It is failing on a step do_package_update_index_ipk when calling Python program
opkg-make-index. See error below.
On Thu, May 17, 2012 at 07:34:24AM +, Craig McQueen wrote:
> I'm trying to build OE classic for i.MX28, following instructions at:
> http://www.imxdev.org/wiki/index.php?title=All_Boards_OpenEmbedded
>
> I'm trying to run:
> bitbake bootstrap-image
>
> It is failing on a step do_package_upd
* it was created by volatiles before, but without sysvinit
systemd-update-utmp-runlevel.service fails to start without this
Signed-off-by: Martin Jansa
---
meta-oe/recipes-core/systemd/systemd_git.bb |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/meta-oe/recipes-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Op 17-05-12 11:23, Martin Jansa schreef:
> * it was created by volatiles before,
If it was done by volatiles before shouldn't it be a tmpfile.d/ snippet
instead of do_install_append? /var/run gets clean on boot on a lot of systems.
regards,
Koen
---
On Thu, May 17, 2012 at 6:56 AM, Koen Kooi wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Op 17-05-12 11:23, Martin Jansa schreef:
>> * it was created by volatiles before,
>
> If it was done by volatiles before shouldn't it be a tmpfile.d/ snippet
> instead of do_install_append? /var
Hello,
Our friends at Eukrea has started working at a Chromium specific layer
and to share work in web browser packaging we opted to merge both
layers to host different web browser packages. After this the layer
has been renamed to /meta-browser/.
The meta-browser layer can be used by any project
On Thu, May 17, 2012 at 11:56:22AM +0200, Koen Kooi wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Op 17-05-12 11:23, Martin Jansa schreef:
> > * it was created by volatiles before,
>
> If it was done by volatiles before shouldn't it be a tmpfile.d/ snippet
> instead of do_install_a
On Thursday 17 May 2012 03:18:26 Henning Heinold wrote:
> my second son was born today, so I can not make any promise for the
> linuxtag. So I think it is really better to cancel the whole booth. That is
> really sad, but maybee next time we should ask a lot earlier if we can
> really man the booth
On Thursday 17 May 2012 08:58:39 Martin Jansa wrote:
> * sometimes it leaks from meta-chromium and breaks pidgin build
Does that mean SSL will be unavailable in pidgin after this change?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
On Thu, May 17, 2012 at 12:20:12PM +0100, Paul Eggleton wrote:
> On Thursday 17 May 2012 08:58:39 Martin Jansa wrote:
> > * sometimes it leaks from meta-chromium and breaks pidgin build
>
> Does that mean SSL will be unavailable in pidgin after this change?
No it means that it should always detec
Signed-off-by: Martin Jansa
---
meta-oe/recipes-support/pidgin/pidgin.inc |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-oe/recipes-support/pidgin/pidgin.inc
b/meta-oe/recipes-support/pidgin/pidgin.inc
index 1a35457..db4753e 100644
--- a/meta-oe/recipes-support/
On Thursday 17 May 2012 13:24:46 Martin Jansa wrote:
> On Thu, May 17, 2012 at 12:20:12PM +0100, Paul Eggleton wrote:
> > On Thursday 17 May 2012 08:58:39 Martin Jansa wrote:
> > > * sometimes it leaks from meta-chromium and breaks pidgin build
> >
> > Does that mean SSL will be unavailable in pid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Op 17-05-12 13:04, Martin Jansa schreef:
> On Thu, May 17, 2012 at 11:56:22AM +0200, Koen Kooi wrote: Op 17-05-12
> 11:23, Martin Jansa schreef:
* it was created by volatiles before,
>
> If it was done by volatiles before shouldn't it be a tmpfil
Hi
happy to see this happen I have few questions on what is planned.
In README is written:
> And we're working to break the dependency on this one:
>
> URI: git://git.openembedded.org/meta-openembedded
Maybe it is a misunderstanding but I would expect for contents of this layer
* systemd.bbcla
On Thu, May 17, 2012 at 12:58 AM, Martin Jansa wrote:
> On Thu, May 17, 2012 at 07:34:24AM +, Craig McQueen wrote:
>> I'm trying to build OE classic for i.MX28, following instructions at:
>> http://www.imxdev.org/wiki/index.php?title=All_Boards_OpenEmbedded
>>
>> I'm trying to run:
>> bitbak
> -Original Message-
> From: Denys Dmytriyenko [mailto:de...@denix.org]
> Sent: Monday, May 14, 2012 2:44 PM
> To: openembedded-devel@lists.openembedded.org
> Cc: Maupin, Chase
> Subject: Re: [oe] [2011.03-maintenance] Pull request 20120514
>
> On Mon, May 14, 2012 at 01:09:40PM -0500, Cha
Trying the new layer, when I ran 'bitbake chromium -c fetch', I got this error:
Fetcher failure for URL: 'http://commondatastorage.googleapis.com/chromium-browser-official/chromium-19.0.1049.3.tar.bz2'. The fetch command returned success for url
http://commondatastorage.googleapis.com/chromium-
I am attempting to build Valgrind with mu very minimal package compiling
experience, and unsurprisingly for such a complex program I am stuck! I
will be happy to submit it to meta-oe once it is building and believe it
would be very useful now that it supports ARM (and MIPS to some extent
appare
On Thu, May 17, 2012 at 03:21:05PM +0100, Jack Mitchell wrote:
> I am attempting to build Valgrind with mu very minimal package compiling
> experience, and unsurprisingly for such a complex program I am stuck! I
> will be happy to submit it to meta-oe once it is building and believe it
> would b
On 17/05/12 15:28, Martin Jansa wrote:
On Thu, May 17, 2012 at 03:21:05PM +0100, Jack Mitchell wrote:
I am attempting to build Valgrind with mu very minimal package compiling
experience, and unsurprisingly for such a complex program I am stuck! I
will be happy to submit it to meta-oe once it is
On Thursday 17 May 2012 08:18:47 Gary Thomas wrote:
> Trying the new layer, when I ran 'bitbake chromium -c fetch', I got this
> error: Fetcher failure for URL:
> 'http://commondatastorage.googleapis.com/chromium-browser-official/chromium
> -19.0.1049.3.tar.bz2'. The fetch command returned success
On 2012-05-17 08:37, Paul Eggleton wrote:
On Thursday 17 May 2012 08:18:47 Gary Thomas wrote:
Trying the new layer, when I ran 'bitbake chromium -c fetch', I got this
error: Fetcher failure for URL:
'http://commondatastorage.googleapis.com/chromium-browser-official/chromium
-19.0.1049.3.tar.bz2'
On Thursday 17 May 2012 08:46:08 you wrote:
> On 2012-05-17 08:37, Paul Eggleton wrote:
> > On Thursday 17 May 2012 08:18:47 Gary Thomas wrote:
> >> Trying the new layer, when I ran 'bitbake chromium -c fetch', I got this
> >> error: Fetcher failure for URL:
> >> 'http://commondatastorage.googleapi
On 2012-05-17 09:04, Paul Eggleton wrote:
On Thursday 17 May 2012 08:46:08 you wrote:
On 2012-05-17 08:37, Paul Eggleton wrote:
On Thursday 17 May 2012 08:18:47 Gary Thomas wrote:
Trying the new layer, when I ran 'bitbake chromium -c fetch', I got this
error: Fetcher failure for URL:
'http://c
Hi Gary,
Le Thu, 17 May 2012 09:19:48 -0600,
Gary Thomas a écrit :
> It does look like there's a lot of redirecting going on which is causing the
> wget behaviour:
>
> $ wget
> http://commondatastorage.googleapis.com/chromium-browser-official/chromium-19.0.1049.3.tar.bz2
> --2012-05-17 09:16:0
Le Thu, 17 May 2012 08:46:08 -0600,
Gary Thomas a écrit :
> Of course, but that's a result of the fetcher code - the recipe does not
> have such:
>SRC_URI =
> "http://commondatastorage.googleapis.com/chromium-browser-official/${P}.tar.bz2";
>
it seems that changing the SRC_URI to :
SRC_URI =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Op 17-05-12 15:07, Andreas Müller schreef:
> Hi
>
> happy to see this happen I have few questions on what is planned.
>
> In README is written:
>
>> And we're working to break the dependency on this one:
>>
>> URI: git://git.openembedded.org/meta-o
On Thu, May 17, 2012 at 9:41 PM, Koen Kooi wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Op 17-05-12 15:07, Andreas Müller schreef:
>> Hi
>>
>> happy to see this happen I have few questions on what is planned.
>>
>> In README is written:
>>
>>> And we're working to break the depende
On Thu, May 17, 2012 at 10:18:26PM +0200, Andreas M?ller wrote:
> On Thu, May 17, 2012 at 9:41 PM, Koen Kooi wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Op 17-05-12 15:07, Andreas M?ller schreef:
> >> Hi
> >>
> >> happy to see this happen I have few questions on what is pl
> > >> happy to see this happen I have few questions on what is planned.
BTW, http://git.yoctoproject.org/cgit/cgit.cgi/meta-systemd/
--
Denys
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Op 18-05-12 06:28, Denys Dmytriyenko schreef:
> happy to see this happen I have few questions on what is
> planned.
>
> BTW, http://git.yoctoproject.org/cgit/cgit.cgi/meta-systemd/
Yeah, the words "shameless" and "rip off" come to mind. It e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Op 17-05-12 22:18, Andreas Müller schreef:
> On Thu, May 17, 2012 at 9:41 PM, Koen Kooi
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> Op 17-05-12 15:07, Andreas Müller schreef:
>>> Hi
>>>
>>> happy to see this happen I have few que
33 matches
Mail list logo