opkg list-installed is empty

opkg list-installed is empty

[Seth Bollinger]

[-- Attachment #1: Type: text/plain, Size: 554 bytes --]

Hello All,

I'm having a problem with opkg.  When I run the image I've built with the
package-management feature and PACKAGE_CLASS equal to package_ipk, the
image has no installed packages.  They're obviously installed, because it's
running but "opkg list-installed" is empty.  I was expecting a large list
of installed packages.  I don't see anything I would expect to see in
/var/lib/opkg.  I must be missing something fundamental, but after
reviewing the documentation and code, I'm coming up empty.  Please
enlighten me!

Thanks,

Seth

[-- Attachment #2: Type: text/html, Size: 683 bytes --]

Re: opkg list-installed is empty

[Paul Eggleton]

Hi Seth,

On Monday 03 June 2013 06:49:06 Seth Bollinger wrote:
> I'm having a problem with opkg.  When I run the image I've built with the
> package-management feature and PACKAGE_CLASS equal to package_ipk, the
> image has no installed packages.  They're obviously installed, because it's
> running but "opkg list-installed" is empty.  I was expecting a large list
> of installed packages.  I don't see anything I would expect to see in
> /var/lib/opkg.  I must be missing something fundamental, but after
> reviewing the documentation and code, I'm coming up empty.  Please
> enlighten me!

If /var/lib/opkg is empty in your image, it can only be because its contents 
have been deleted; and that could be either because the value of 
IMAGE_FEATURES doesn't end up containing package-management, or alternatively 
remove_packaging_data_files is being added manually to 
ROOTFS_POSTPROCESS_COMMAND (as core-image-minimal does). I'd suggest using 
bitbake -e your-image | less and looking at the values of IMAGE_FEATURES and 
ROOTFS_POSTPROCESS_COMMAND to see what's really going on.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: opkg list-installed is empty

[seth bollinger]

[-- Attachment #1: Type: text/plain, Size: 792 bytes --]


> Paul Eggleton <mailto:paul.eggleton@linux.intel.com>
> June 3, 2013 7:10 47AM
> Hi Seth,
>
> If /var/lib/opkg is empty in your image, it can only be because its 
> contents
> have been deleted; and that could be either because the value of
> IMAGE_FEATURES doesn't end up containing package-management, or 
> alternatively
> remove_packaging_data_files is being added manually to
> ROOTFS_POSTPROCESS_COMMAND (as core-image-minimal does). I'd suggest 
> using
> bitbake -e your-image | less and looking at the values of 
> IMAGE_FEATURES and
> ROOTFS_POSTPROCESS_COMMAND to see what's really going on.
>
> Cheers,
> Paul
>
Thanks Paul!  As usual, you nailed it.  I missed the 
ROOTFS_POSTPROCESS_COMMAND that I pulled in when I copied 
core-image-minimal.

Seth


[-- Attachment #2.1: Type: text/html, Size: 2064 bytes --]

[-- Attachment #2.2: compose-unknown-contact.jpg --]
[-- Type: image/jpeg, Size: 801 bytes --]