Package: wims-lti Version: 0.4.4-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts
Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up wims-lti (0.4.4-2) ... dpkg: error processing package wims-lti (--configure): installed wims-lti package post-installation script subprocess returned error exit status 2 Processing triggers for libc-bin (2.31-9) ... Processing triggers for ca-certificates (20210119) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Errors were encountered while processing: wims-lti If I insert set -x in the postinst script, the race ends with [...] + db_get wims-lti/virtualHost + _db_cmd GET wims-lti/virtualHost + _db_internal_IFS= + IFS= + printf %s\n GET wims-lti/virtualHost + IFS= + read -r _db_internal_line + IFS= + RET=wims-lti.example.com + return 0 + virtualHost=wims-lti.example.com + appDir=/var/lib/wims-lti + apacheConfDist=/etc/apache2/sites-available/wims-lti-django.conf-dist + apacheConf=/etc/apache2/sites-available/wims-lti-django.conf + getent passwd lti + lti_entry= I'd suggest this change to fix the logic, and something similar for the group: - lti_entry=$(getent passwd lti) - if [ -z "$lti_entry" ]; then + if ! getent passwd lti >/dev/null ; then cheers, Andreas
wims-lti_0.4.4-2.log.gz
Description: application/gzip
