Hi
Why does yocto .gitignpre include meta-*/. Why would we possibly want to
ignore custom layers ?
--
Søren Holm
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hi Nicolas,
On Friday 29 November 2013 17:31:40 Nicolas Dechesne wrote:
> On Fri, Nov 29, 2013 at 4:58 PM, Paul Eggleton <
> paul.eggle...@linux.intel.com> wrote:
> > * It requires root to run, since it mounts the images temporarily and
> > modifies the contents. We've done quite a lot to avoid ha
Paul,
On Fri, Nov 29, 2013 at 4:58 PM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:
> LAVA
> -
>
> A number of people had suggested I look at LAVA [1]. It is split into
> different
> components for each function, some of which should be usable independently
> so
> you don't have to
Hi folks,
(warning - long email ahead)
As I've talked about recently, one of the things I'm looking into at the
moment is how to do automated QA for Yocto Project releases on real hardware.
The Yocto Project QA team does tests on the supported reference platforms for
each architecture for ever
Hello,
Here is the RFC version of the Yocto 1.6 Overall Testing Plan:
https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan. It will be
presented on the next Technical Team meeting to the community. Please take some
time for review!
Regards,
--
Alexandru Georgescu
Yocto QA Engineer
SSG
On Fri, Nov 29, 2013 at 09:02:47AM +, Guenzel, Robert wrote:
> Hello,
>
> I am currently starting to work with Yocto and I am having a bit of a hard
> time to figure out how the two documented versions of WORKDIR come into
> existence.
>
> The doc states:
> """
> For packages that are not d
Hi Robert,
On Friday 29 November 2013 15:28:28 Robert Yang wrote:
> I can reproduce the similar problem now, I think that it should be a
> bug of e2fsprogs, it seems the debugfs can't know the free space
> correctly, and thus it appears no free blocks, I'm sorry to say that
> I can't fix it in a s
Hello,
I am currently starting to work with Yocto and I am having a bit of a hard time
to figure out how the two documented versions of WORKDIR come into existence.
The doc states:
"""
For packages that are not dependent on a particular machine, WORKDIR is defined
as follows:
${TMPDIR}/work/
