[OE-core] [oe] Opkg files at /var/lib/opkg/lists

[Eric Bénard]

Hi Aljandro,

copying oe-core's ML as the problem seems related to oe-core and
not to meta-oe.

Le Wed, 12 Nov 2014 12:15:46 -0600,
Alejandro del Castillo <alejandro.delcastillo at ni.com> a écrit :

> Hello,
> 
> I noticed that the OE build process is leaving files at 
> /var/lib/opkg/lists (~1.5 MB on my system), which I believe are the feed 
> content used to build the image. The target opkg.conf file configure 
> lists_dir to be at /var/lib/opkg (instead of the default 
> /var/lib/opkg/lists), so the feed content under /var/lib/opkg/lists is not 
> used at all. 
> 
> Does anyone know if there Is a reason why the files are left over or is 
> this a bug? Shouldn't the image creation process remove the whole 
> directory if it's not going to be used? 
> 
> BTW, Dylan doesn't have this problem, but Daisy and Dizzy do (not sure 
> about Dora).
> 
I was on a similar subject today and this seems broken since :
d950ef40a3eae4b54cc62828e66d84a62d78c447

BTW it seems that FEED_DEPLOYDIR_BASE_URI was replaced by
PACKAGE_FEED_URIS in 9b8811045546ad67b4695d980f09636d5506e50c but the
document is still pointing to the previous one :
http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#runtime-package-management-target-ipk
If the replacement was not intended then there is a problem as
FEED_DEPLOYDIR_BASE_URI doesn't seems to work anymore (tested with
dizzy and package_ipk).

Best regards
Eric