On 05/03/2016 02:49 AM, Patrick Ohly wrote:
> But how does opkg know that "config file not present" is an error? It
> depends on the the semantic of the file and thus the package providing
> the file. It's not declared explicitly, so it is a fairly arbitrary
> judgment call to treat "missing" as
On Mon, 2016-05-02 at 11:15 -0500, Alejandro del Castillo wrote:
>
> On 05/02/2016 08:39 AM, Patrick Ohly wrote:
> > On Fri, 2016-04-22 at 14:51 +0100, Richard Purdie wrote:
> >> When enabling extra DEBUGFS image generation with opkg, errors are seen
> >> like:
> >>
> >> ERROR:
On 05/02/2016 08:39 AM, Patrick Ohly wrote:
> On Fri, 2016-04-22 at 14:51 +0100, Richard Purdie wrote:
>> When enabling extra DEBUGFS image generation with opkg, errors are seen like:
>>
>> ERROR: core-image-minimal-1.0-r0 do_rootfs: Cannot get the installed
>> packages list. Command
>>
On Fri, 2016-04-22 at 14:51 +0100, Richard Purdie wrote:
> When enabling extra DEBUGFS image generation with opkg, errors are seen like:
>
> ERROR: core-image-minimal-1.0-r0 do_rootfs: Cannot get the installed packages
> list. Command
>
Hi,
* Richard Purdie [160422 15:52]:
> When enabling extra DEBUGFS image generation with opkg, errors are seen like:
> ERROR: core-image-minimal-1.0-r0 do_rootfs: Cannot get the installed packages
> list. Command
>
When enabling extra DEBUGFS image generation with opkg, errors are seen like:
ERROR: core-image-minimal-1.0-r0 do_rootfs: Cannot get the installed packages
list. Command '/media/build1/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg
-f