I screwed up the patch link in my previous email:
http://hastebin.com/yaxisokuqo.py

On Tue, Feb 17, 2015 at 9:45 AM, Werner Grift <sky.captin@gmail.com> wrote:

> Hi Otavio.
>
> I received the recipes (and a working version of it on our build server)
> from a colleague that only introduced the following patch
> <http://c7b9611ad0ead17a624fc73a60c321ff249c2214> to oe at
> rev c7b9611ad0ead17a624fc73a60c321ff249c2214. The rest of the system was
> untouched.
>
> I made a fresh build system on my development machine. My build ran a
> couple of times without above mentioned patch, but broke because it was not
> applied. After applying the patch my build worked, but the copy device tree
> issue remained. (But not on the build server) I then ran ./oebb.sh update
> to make sure everything is cozy (which removed the patch mentioned above
> without me realizing) and miraculously the build continued to succeed, but
> the device tree issue remained. I suspect I broke sstate by doing this. My
> sstate is not shared between dev and build.
>
> Therefor, I suspect that the issue was generated in house. Regardless,
> the rest of create_image.sdcard does not make assumptions as to pwd, so I
> figured the patch is needed for completeness.
>
> Regards,
>
> Werner.
>
>
> On Fri, Feb 13, 2015 at 2:37 AM, Otavio Salvador <otavio@ossystems.com.br>
> wrote:
>
>> Hello Werner,
>>
>> On Wed, Feb 11, 2015 at 7:19 AM, Werner Grift <sky.captin@gmail.com>
>> wrote:
>> > Signed-off-by: Werner Grift <sky.captin@gmail.com>
>>
>> I am wondering how this has been working previously. Any idea what
>> changed which causes the behaviour change?
>>
>> --
>> Otavio Salvador                             O.S. Systems
>> http://www.ossystems.com.br        http://code.ossystems.com.br
>> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>>
>
>