opkg problem
Something has changed recently in my images:
# opkg update Collected errors: * opkg_conf_load: Could not create lock file /var/lib/opkg/lock: No such file or directory. Actually, it seems that the whole of /var/lib/opkg (databases, etc) have gone missing. Shouldn't this get populated as the rootfs image is created?
In any case, any ideas where /var/lib/opkg might have vanished to?
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 10 lines · Gary Thomas
Something has changed recently in my images:
# opkg update Collected errors: * opkg_conf_load: Could not create lock file /var/lib/opkg/lock: No such file or directory. Actually, it seems that the whole of /var/lib/opkg (databases, etc) have gone missing. Shouldn't this get populated as the rootfs image is created?In any case, any ideas where
/var/lib/opkgmight have vanished to?
Gary,
Depending on what image you are building, you may need to add "package-managment" into your IMAGE_FEATURES list. This is due the to the change from Phil B. (87780fc09b066525e47d0f50ee5497db54d304cd).
Sau!
Quoted 2 lines
Thanks
Quoted 9 lines · Saul Wold
Quoted 8 lines · Gary Thomas
Something has changed recently in my images:
# opkg update Collected errors: * opkg_conf_load: Could not create lock file /var/lib/opkg/lock: No such file or directory. Actually, it seems that the whole of /var/lib/opkg (databases, etc) have gone missing. Shouldn't this get populated as the rootfs image is created?
Quoted 6 lines
Quoted 2 lines
In any case, any ideas where
/var/lib/opkgmight have vanished to?Gary,
Depending on what image you are building, you may need to add "package-managment" into your
IMAGE_FEATURESlist. This is due the to the change from Phil B. (87780fc09b066525e47d0f50ee5497db54d304cd).
Yes, it does fix my problem. I think that change is a bit incomplete though, as it has deleted the databases used by opkg, but opkg still remains. One gets the same error as above when just booting in this case. It would seem to me that if package-management is turned off (and hence the databases removed), then the tool(s) should be removed as well.
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------