Package: puppetmaster-passenger Version: 3.0.0~rc1-1 Severity: serious User: [email protected] 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 puppetmaster-passenger (3.0.0~rc1-1) ...
Signed certificate request for ca
Rebuilding inventory file
myhost.domain.example.com has a waiting certificate request
Signed certificate request for myhost.domain.example.com
Removing file Puppet::SSL::CertificateRequest myhost.domain.example.com at
'/var/lib/puppet/ssl/ca/requests/myhost.domain.example.com.pem'
Removing file Puppet::SSL::CertificateRequest myhost.domain.example.com at
'/var/lib/puppet/ssl/certificate_requests/myhost.domain.example.com.pem'
Considering dependency setenvif for ssl:
Module setenvif already enabled
Considering dependency mime for ssl:
Module mime already enabled
Considering dependency socache_shmcb for ssl:
Enabling module socache_shmcb.
Enabling module ssl.
See /usr/share/doc/apache2/README.Debian.gz on how to configure SSL and
create self-signed certificates.
To activate the new configuration, you need to run:
service apache2 restart
Enabling module headers.
To activate the new configuration, you need to run:
service apache2 restart
ERROR: Site puppetmaster does not exist!
dpkg: error processing puppetmaster-passenger (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
puppetmaster-passenger
Note that no services are running (forbidden by policy-rc.d) in the chroot
where piuparts performs the test.
cheers,
Andreas
puppetmaster-passenger_3.0.0~rc1-1.log.gz
Description: GNU Zip compressed data
