Hi Niko,

> 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

> I'd expect retrying in the background or even leaving it disabled, but
> postinst failure seems too intrusive.

Well, you supplied it with localhost as the IMAP server name, or installed
it with a too high debconf priority and thus implicitly accepted this
setting:

> -- debconf information:
>   imapproxy/imap-server: localhost

It is customary for Debian packages to start a service right after
installation. In fact, the code that does this in the imapproxy package is
inserted by debhelper. So the same things happens in all packages that use
debhelper to take care of init script installation and encounter some kind
of configuration that is not compatible with the local situation.

I think that it's logical that a service that can't be started after
installation causes the installation to give an error. You are then given
the option to correct the situation and finish the installation later.

If you think services should not be started after installation, or that if
such a service errors installation should be continued regardless, I think
you should reassign the bug to debhelper.

I'm not sure what should be changed on the imapproxy package since
'localhost' seems like a sensible default for me if the user skips the
debconf questions, and I do not know of a better default that would solve
your problem.


cheers,
Thijs




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to