Missing packages on apt run:

daurnimator commented 8 years ago

# dpkg --set-selections < /etc/packages.txt
dpkg: warning: package not in database at line 8: apt-file
dpkg: warning: package not in database at line 38: command-not-found
dpkg: warning: package not in database at line 56: dh-lua
dpkg: warning: package not in database at line 313: libncurses5-dev:amd64
dpkg: warning: package not in database at line 314: libncursesw5-dev:amd64
dpkg: warning: package not in database at line 378: libruby2.2:amd64
dpkg: warning: package not in database at line 456: libxml2-dev:amd64
dpkg: warning: package not in database at line 460: libxslt1-dev:amd64
dpkg: warning: package not in database at line 468: locales-all
dpkg: warning: package not in database at line 675: reptyr
dpkg: warning: package not in database at line 740: weechat-plugins
dpkg: warning: found unknown packages; this might mean the available database
is outdated, and needs to be updated through a frontend method

daurnimator commented 8 years ago

This was a sympton of packages.txt not being commited correctly.

daurnimator commented 8 years ago

No it wasn't.... I think. something weird is happening.

I think we need to run dselect update as part of the sync process.

KellerFuchs commented 8 years ago

We already do, see sync.yml.

That's pretty strange/annoying, though.

daurnimator commented 8 years ago

We already do, see sync.yml.

update != upgrade.

But I added it: https://github.com/hashbang/admin-tools/blob/master/sync.yml#L15 :)

KellerFuchs commented 8 years ago

Oops, yes, misread. We don't need dselect update as far as I can see, since we already update dpkg available packages db.

daurnimator commented 8 years ago

We don't need dselect update as far as I can see, since we already update dpkg available packages db.

Via what?

apt-get has a different package index/cache than dselect.

hashbang / shell-etc

Missing packages on apt run: #44