On Wed, 2021-06-23 at 09:11:55 +0200, Thomas Lange wrote: > >>>>> On Wed, 23 Jun 2021 01:59:43 +0200, Guillem Jover <guil...@debian.org> > >>>>> said: > > * bin/install_packages > > The function mkpackagelist() checks for the presence of the available > > file. The correct interface is «dpkg --root $FAI_ROOT --print-avail», > > which will print nothing if the file is empty or missing. > In my developer version of FAI, this is already replaced by parsing apt-cache > dumpavail. > > > The function create_debian_pkg_list() parses the available file, but > > just as the above one, it should be switched to parse the output from > > «dpkg --root $FAI_ROOT --print-avail». > I've checked on several machines, and it seems that > /var/lib/dpkg/available is not used any more. On one machine it's just > empty, on another machine the content is outdated since some years. > So using dpkg --print-avail does not work any more or gives wrong output.
I had a similar comment initially, as indeed the available db is mostly used nowadays by dselect. But then noticed that (at least the source I downloaded), generates the available file from apt-get's dumpavail, and then cleans it up, so it does not matter whether it previously contained any values. > > * bin/fai-make-nfsroot > > The add_packages_nfsroot() function and the main routine, write into > > the available db directly, these should instead use > This is already removed in my developer version. > > Does a Debian system need /var/lib/dpkg/available at all these days? See above. Thanks, Guillem
