(originally was going to submit a bug, but decided to ask here instead, so cut/pasted this to here)
Package: slocate Version: 2.4-2potato1 Severity: normal I removed adduser from a system here awhile ago. Today, i went to install slocate sl:~# apt-get install slocate Reading Package Lists... Done Building Dependency Tree... Done The following NEW packages will be installed: slocate 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/21.9kB of archives. After unpacking 63.5kB will be used. debconf: failed to initialize Dialog frontend debconf: falling back to Text frontend Selecting previously deselected package slocate. (Reading database ... 6383 files and directories currently installed.) Unpacking slocate (from .../slocate_2.4-2potato1_i386.deb) ... Adding `diversion of /usr/bin/locate to /usr/bin/locate.notslocate by slocate' Adding `diversion of /usr/bin/updatedb to /usr/bin/updatedb.notslocate by slocate' Adding `diversion of /usr/share/man/man1/locate.1.gz to /usr/share/man/man1/locate.notslocate.1.gz by slocate' Adding `diversion of /usr/share/man/man1/updatedb.1.gz to /usr/share/man/man1/updatedb.notslocate.1.gz by slocate' Adding `diversion of /etc/cron.daily/find to /etc/cron.daily/find.notslocate by slocate' Setting up slocate (2.4-2potato1) ... Changing permissions on: /usr/bin/slocate chown: root.slocate: invalid group dpkg: error processing slocate (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: slocate E: Sub-process /usr/bin/dpkg returned an error code (1) Looks like it uses adduser to add the slocate user. Am I just daft in my understanding of dependencies? Does a required package(adduser) end up automatically a dependency for everything else? If nothing else, maybe it could show the failed adduser in the postinst script Mike