severity #470431 normal
tags #470371 + moreinfo
thanks
Laurent Bonnaud wrote:
> Package: imapproxy
> Version: 1.2.6-1
> Severity: grave
> Justification: renders package unusable
>
>
> Hi,
>
> here is the problem:
>
> # apt-get install imapproxy
> 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 6 not upgraded.
> Need to get 53.7kB of archives.
> After this operation, 238kB of additional disk space will be used.
> Get:1 http://ftp.fr.debian.org sid/main imapproxy 1.2.6-1 [53.7kB]
> Fetched 53.7kB in 0s (261kB/s)
> database /var/lib/apt/listchanges.db failed to load.
> Preconfiguring packages ...
> Selecting previously deselected package imapproxy.
> (Reading database ... 1590210 files and directories currently installed.)
> Unpacking imapproxy (from .../imapproxy_1.2.6-1_i386.deb) ...
> Setting up imapproxy (1.2.6-1) ...
> 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)
>
Do you have any IMAP server daemon running?
There is actually an error in imapproxy's default config file --
imapproxy tries to bind to and listen to the same address with the
config file shipped.
This will be fixed by changing the default listen_port to another value
for the cases where the user chooses "localhost" as the server.
This issue is complicated to classify, since this behaviour is a result
of recent changes in code upstream -- previously, it would start without
complaining even if it couldn't bind. This behaviour is probably more
"sane".
Regards,
J.L.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
