> severity 684463 normal thank you!
> However, it would be much nicer if we could find a way to deal with this > scenario without having to use debconf. Maybe we could try to check the > validity of the requirements: there is a 'condor' user and it can't be > used to log in. If there is a reliable way to verify this in the case > that adduser --system fails (and the user comes from LDAP, or whatever > other possible auth method), we could maybe issue a warning message and > proceed without manual approval. Opinions? What about this in condor.postinst:: SH=$(getent passwd | egrep '^condor:'| cut -d : -f 7) if [ "$SH" = "/bin/false" -o "$SH" = "/usr/sbin/nologin" ]; then # condor user exists and it is a locked user else adduser --system ... fi getent gets is info from the nss libraries, so it is independent of auth method. So no need to use new dpkg questions. Could this warrant a freeze exception? Ciao, Tiziano -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
