On 16/11/10 00:57, José Luis Tallón wrote:
Thanks. Will apply.
Great, thanks!
Even though the fix can't possibly enter Squeeze (unfortunately), I will
try and have it in the next version.
Mind sponsoring the upload ?
Talk to the release-team. Installation problems are something they might
severity #512369 normal
tags #512369 +patch
thanks
Leo 'costela' Antunes wrote:
Hi,
[snip]
How about calling dh_installinit with --no-start and manually calling
invoke-rc.d imapproxy start || true on fresh installs? Possibly
throwing a warning?
I just think its unnecessary to botch the
Hi,
Just my two cents on this relatively old bug which just happen to hit
me: I understand the need for avoiding user interaction on install and
all, but simply failing the installation with the standard debconf
priority seems a bit sloppy IMHO, specially considering it's not that
rare to have
Package: imapproxy
Version: 1.2.6-4
Severity: serious
This package fails to configure with the default settings when
an IMAP server can't be reached on localhost:143.
Setting up imapproxy (1.2.6-4) ...
Starting IMAP proxy: invoke-rc.d: initscript imapproxy, action start failed.
dpkg: error
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
severity 512369 normal
thanks
On Tue, Jan 20, 2009 at 01:59:24PM +0100, Thijs Kinkhorst wrote:
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
6 matches
Mail list logo
