On Sat, Dec 1, 2018 at 3:16 AM Elimar Riesebieter <riese...@lxtec.de> wrote: > > * Mike Fedyk <mikefe...@gmail.com> [2018-12-01 03:04 -0600]: > > > Hi, > > > [...] > > > > > Then I run dpkg as requested: > > > > (test-buster)root@localhost:/# dpkg -l | egrep "(libasou|alsa)" > > ii alsa-utils 1.1.7-1 armhf > > Utilities for configuring and using ALSA > > ii libasound2:armhf 1.1.7-1+b1 armhf > > shared library for ALSA applications > > ii libasound2-data 1.1.7-1 all > > Configuration files and profiles for ALSA drivers > > ii libasound2-dev:armhf 1.1.7-1+b1 armhf > > shared library for ALSA applications -- development files > > > > Confirmation the directory is missing: > > > > (test-buster)root@localhost:/# ls -lhd /usr/share/alsa/alsa.conf.d > > ls: cannot access '/usr/share/alsa/alsa.conf.d': No such file or directory > > /u/s/a/alsa.conf is installed by libasound2-plugins. Please install > libasound2-plugins and test again. >
I know /u/s/a/alsa.conf.d is installed by libasound2-plugins, and I referenced the other bug in my original report to say as much. I know how to work around the problem, and I already have on one of my systems. I'm filing this bug report to keep from having to work around the problem on other machines, and for others as well then they eventually use buster with crouton. In order to install libasound2-plugins during the chroot build, I would have to patch crouton. While I could do that, the build doesn't need anything in libasound2-plugins besides the /u/s/a/alsa.conf.d directory. Why must libasound2-plugins be installed when the only thing required from it is directory creation? That goes against minimal installs "only install what is needed, and no more" philosophy. Please put /u/s/a/alsa.conf.d back in libasound2-data so that minimal installs can be minimal.
