Package: tripwire Version: 2.4.2.2-5 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. This bug was observed during i386 tests in i386 testing and unstable chroots on an amd64 host. This seems to have started after the binNMU against glibc 2.21. >From the attached log (scroll to the bottom...): Selecting previously unselected package tripwire. (Reading database ... (Reading database ... 8843 files and directories currently installed.) Preparing to unpack .../tripwire_2.4.2.2-5+b1_i386.deb ... Unpacking tripwire (2.4.2.2-5+b1) ... Setting up tripwire (2.4.2.2-5+b1) ... Segmentation fault Segmentation fault Generating site key (this may take several minutes)... Segmentation fault dpkg: error processing package tripwire (--configure): subprocess installed post-installation script returned error exit status 139 Errors were encountered while processing: tripwire cheers, Andreas
tripwire_2.4.2.2-5+b1.log.gz
Description: application/gzip
