Control: severity -1 normal Hi,
Lowering severity since only piuparts is stumbling upon this (i.e.: neither the FusionForge rebuild testsuite nor any of our production installs triggered this issue, hence widespread usage works). I wish you didn't wait until right when FusionForge is back in testing to report this. This has been around for ages, we didn't touch the package for 2 months, and it's much more efficient to group reports. (For the record, I find templated messages displeasing, and one that calls a package "too buggy" for such an issue, disrespectful :/) Patch onwards. Cheers! Sylvain On Tue, Sep 08, 2015 at 02:57:29PM +0200, Andreas Beckmann wrote: > Package: fusionforge-web > Version: 6.0.2+20150901-1 > 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...): > > Selecting previously unselected package fusionforge-web. > (Reading database ... > (Reading database ... 12482 files and directories currently installed.) > Preparing to unpack .../fusionforge-web_6.0.2+20150901-1_all.deb ... > Unpacking fusionforge-web (6.0.2+20150901-1) ... > Setting up fusionforge-web (6.0.2+20150901-1) ... > Enabling site fusionforge. > To activate the new configuration, you need to run: > service apache2 reload > /usr/share/fusionforge/post-install.d/web/web.sh: line 77: openssl: command > not found > dpkg: error processing package fusionforge-web (--configure): > subprocess installed post-installation script returned error exit status > 127 > Errors were encountered while processing: > fusionforge-web
