
In woofQ, 3buildeasydistro runs sandbox3/rootfs-complete/usr/local/EasyPak/create_db, which downloads the Devuan db files and generates sandbox3/rootfs-complete/usr/local/EasyPak/Packages-devuan-ascii-contrib, Packages-devuan-ascii-main, and Packages-devuan-ascii-non-free.

create_db also generates sandbox3/rootfs-complete/usr/local/EasyPak/invaliddepslist. It is actually debdb2pupdb, called by create_db, that generates invaliddepslist, and it only does so when run in woofQ. When debdb2pupdb runs in a running-Easy, invaliddepslist is epected to be already existing.

roofs-skeleton/usr/local/EasyPak/ in woofQ has these db files already generated:

Packages-devuan-ascii-contrib
Packages-devuan-ascii-main
Packages-devuan-ascii-non-free
updatespkglist-contrib
updatespkglist-main
updatespkglist-non-free
invaliddepslist
PKGS_HOMEPAGES

...for the Devuan 'ascii' release, without updates (with updates, they would be in the Packages-* files). The updatespkglist-* files are empty. 

When run in woofQ, create_db copied PKGS_HOMEPAGES to sandbox3/rootfs-complete/usr/local/EasyPak/, then appends any extra devuan pkg home urls to it.
In the case of Easy "Pyro" series, the original PKGS_HOMEPAGES would have those pkgs from OpenEmbedded.

