Re: [OE-core] [PATCH] image.bbclass: Use deltask instead of noexec for package_write_rpm

On 03/05/2018 07:52 AM, Jason Wessel wrote: On 03/03/2018 09:50 AM, Richard Purdie wrote: On Sat, 2018-03-03 at 12:46 -0300, Otavio Salvador wrote: On Fri, Mar 2, 2018 at 5:27 PM, Jason Wessel wrote: If you install an image into another image (this is the case

Re: [OE-core] [PATCH] image.bbclass: Use deltask instead of noexec for package_write_rpm

On 03/03/2018 09:50 AM, Richard Purdie wrote: On Sat, 2018-03-03 at 12:46 -0300, Otavio Salvador wrote: On Fri, Mar 2, 2018 at 5:27 PM, Jason Wessel wrote: If you install an image into another image (this is the case for custom initrd for example), it will fail

Re: [OE-core] [PATCH] image.bbclass: Use deltask instead of noexec for package_write_rpm

On Sat, 2018-03-03 at 12:46 -0300, Otavio Salvador wrote: > On Fri, Mar 2, 2018 at 5:27 PM, Jason Wessel com> wrote: > > > > If you install an image into another image (this is the case for > > custom initrd for example), it will fail with a non obvious python > >

Re: [OE-core] [PATCH] image.bbclass: Use deltask instead of noexec for package_write_rpm

On Fri, Mar 2, 2018 at 5:27 PM, Jason Wessel wrote: > If you install an image into another image (this is the case for > custom initrd for example), it will fail with a non obvious python > backtrace. This patch modifies the package_manager.py print which > package

[OE-core] [PATCH] image.bbclass: Use deltask instead of noexec for package_write_rpm

If you install an image into another image (this is the case for custom initrd for example), it will fail with a non obvious python backtrace. This patch modifies the package_manager.py print which package causes the failure for the future, if it is missing a manifest. The error you get looks