On 8/12/19 5:32 PM, Richard Purdie wrote:
> On Fri, 2019-08-09 at 00:12 +0100, richard.pur...@linuxfoundation.org
> wrote:
>> I've just seen this with dnf on the autobuilders and an rpm build.
>> The most interesting bit was:
>>
>> [pokybuild@centos7-ty-1 temp]$ pwd
>>
On Fri, 2019-08-09 at 00:12 +0100, richard.pur...@linuxfoundation.org
wrote:
> I've just seen this with dnf on the autobuilders and an rpm build.
> The most interesting bit was:
>
> [pokybuild@centos7-ty-1 temp]$ pwd
> /home/pokybuild/yocto-worker/genericx86-
>
On Thu, 2019-08-08 at 10:18 +, Jacob Kroon wrote:
> Checking for built ipk packages I see:
>
> [jkroon@manatarms-greyskull ]$ find
> /tmp/ramdisk//deploy/ipk/|grep eudev
> /tmp/ramdisk//deploy/ipk/i686/eudev-dbg_3.2.8-r0_i686.ipk
> /tmp/ramdisk//deploy/ipk/i686/eudev-dev_3.2.8-r0_i686.ipk
>
On Thu, 2019-08-08 at 10:18 +, Jacob Kroon wrote:
> Hi,
>
> On 8/2/19 5:53 PM, Richard Purdie wrote:
> > This has been talked about in a lot of the project meetings but I
> > wanted to ensure its on the mailing list too.
> >
> > master-next (and hopefully soon, master) now contain patches
Hi,
On 8/2/19 5:53 PM, Richard Purdie wrote:
> This has been talked about in a lot of the project meetings but I
> wanted to ensure its on the mailing list too.
>
> master-next (and hopefully soon, master) now contain patches which
> enable "hash equivalency" support in runqueue in bitbake. That
On 8/5/19 2:21 AM, mikko.rap...@bmw.de wrote:
Hi,
On Fri, Aug 02, 2019 at 05:17:21PM +0100, Richard Purdie wrote:
On Fri, 2019-08-02 at 16:53 +0100, Richard Purdie wrote:
With the patches in master-next and this configuration in local.conf:
BB_HASHSERVE = "localhost:0"
BB_SIGNATURE_HANDLER
Hi,
On Fri, Aug 02, 2019 at 05:17:21PM +0100, Richard Purdie wrote:
> On Fri, 2019-08-02 at 16:53 +0100, Richard Purdie wrote:
> > With the patches in master-next and this configuration in local.conf:
> >
> > BB_HASHSERVE = "localhost:0"
> > BB_SIGNATURE_HANDLER = "OEEquivHash"
> >
> > $
On Fri, 2019-08-02 at 16:53 +0100, Richard Purdie wrote:
> With the patches in master-next and this configuration in local.conf:
>
> BB_HASHSERVE = "localhost:0"
> BB_SIGNATURE_HANDLER = "OEEquivHash"
>
> $ bitbake core-image-sato
> $ bitbake m4-native -c install -f
> $ bitbake core-image-sato
>
This has been talked about in a lot of the project meetings but I
wanted to ensure its on the mailing list too.
master-next (and hopefully soon, master) now contain patches which
enable "hash equivalency" support in runqueue in bitbake. That doesn't
sound so interesting until I explain what this