On Sat, Feb 13, 2021 at 5:01 AM Andreas Henriksson wrote: > > For systems where awk is not yet installed (chroots), installation of > > dash will currently fail since it's postinst calls add-shell from > > debianutils. > > Please share details about how to reproduce this situation! > > You say you don't have awk when dash postinst runs, but that would also > mean you don't have base-files (since it pre-depends on awk), which > means you're lacking essential packages while you're configuring > dash! > > Sounds to me like you're doing something very peculiar and likely > completely unsupported to be able to trigger this issue. Atleast I can't > think of any obvious way how to trigger it.
Yes, I am doing something quite peculiar. I am trying to install the absolute minimal system possible, just enough to be able to run a shell (dash). In fact without even base-files. # mmdebstrap --verbose --variant=custom --include=sed,grep,libc-bin,dash,diffutils,coreutils unstable unstable [...] /usr/sbin/add-shell: 20: awk: not found Either another instance of /usr/sbin/add-shell is running, or it was previously interrupted. Please examine /etc/shells.tmp to see if it should be moved onto /etc/shells. dpkg: error processing package dash (--install): installed dash package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dash I can add mawk to the list of packages to make it work, but that isn't quite so minimal ;) # mmdebstrap --verbose --variant=custom --include=sed,mawk,grep,libc-bin,dash,diffutils,coreutils unstable unstable > Replacing using awk with cat whenever possible sounds like a good thing > to do, so for the record I'm not against that. My skepticism is more > at why this is not a wishlist bug report (that would be much better to > adress early in a development cycle, rather than when we're already in > the bullseye freeze). Given the peculiarity and simple work around, I am ok with any severity. Best wishes, Mike
