package imapproxy 1.2.6-4 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
up-imapproxy (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
simply did sudo apt-get install imapproxy on latest ubuntu 8.10
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
imapproxy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 59.0kB of archives.
After this operation, 250kB of additional disk space will be used.
Get:1 http://
Fetched 59.0kB in 0s (127kB/s)
Preconfiguring packages ...
Selecting previously deselected package imapproxy.
(Reading database ... 116488 files and directories currently installed.)
Unpacking imapproxy (from .../imapproxy_
Processing triggers for man-db ...
Setting up imapproxy (1.2.6-4) ...
Starting IMAP proxy: invoke-rc.d: initscript imapproxy, action "start" failed.
dpkg: error processing imapproxy (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
imapproxy
E: Sub-process /usr/bin/dpkg returned an error code (1)
nils@blackbox:~$ uname -a
Linux blackbox 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux
nils@blackbox:~$
ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: imapproxy 1.2.6-4
SourcePackage: up-imapproxy
Title: package imapproxy 1.2.6-4 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux 2.6.27-11-generic x86_64
I have also experienced this bug - the default installed configuration won't start with:
invoke-rc.d imapproxy start
which in turn causes the postinst script to bail out. It seems that the problem is the line:
server_hostname localhost
Since localhost likely is not an IMAP server. Maybe it would be good to provide an /etc/default file which prevents the proxy being launched by default until it is configured correctly.