Your message dated Thu, 15 Mar 2007 10:47:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#405704: fixed in up-imapproxy 1.2.4-9
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Processing commands for [EMAIL PROTECTED]:
> reopen 405704
Bug#405704: imapproxy: fails to start - breaks install/upgrade
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
Bug reopened,
reopen 405704
> Changes:
> up-imapproxy (1.2.4-8) unstable; urgency=high
> .
>* Fixed crash on startup when IMAP server is not available (Closes:
> #405704)
The patch provided by Kees Cook was correct, but you only applied half
of it. Let's have a look at the code:
for ( ai = ISD.ai;
explanation is
>> unsatisfactory and you have not received a better one in a separate
>> message then please contact Jose Luis Tallon
<[EMAIL PROTECTED]> by replying
>> to this email.
>>
>> Debian bug tracking system administrator
>> (administrator, Debian Bug
lon <[EMAIL PROTECTED]> by replying
to this email.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------
Subject:
Bug#405704: fixed in up-imapproxy 1.2.4-8
From:
Jose Luis Tallon <[EMAIL
Your message dated Mon, 12 Mar 2007 01:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#405704: fixed in up-imapproxy 1.2.4-8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
On Fri, 2007-03-09 at 14:02 +0100, José Luis Tallón wrote:
> Steve Langasek wrote:
> > Hi Thijs,
> >
> > I really don't understand why this bug should be considered 'grave'.
> Thank you for your interest, Steve. The bug has been patched anyway :-)
>
> Seems to be working, so I will proceed to ask
Steve Langasek wrote:
> Hi Thijs,
>
> I really don't understand why this bug should be considered 'grave'.
Thank you for your interest, Steve. The bug has been patched anyway :-)
Seems to be working, so I will proceed to ask for an sponsored upload
soon, along with some additional translations.
Th
Hi Thijs,
I really don't understand why this bug should be considered 'grave'. The
explanation of the provided patch is that imapproxy segfaults /when the
server isn't listening/; I've configured imapproxy here to test, and it
starts fine for me when pointed at my imap server. Yes, it crashes fo
Processing commands for [EMAIL PROTECTED]:
> severity 405704 grave
Bug#405704: imapproxy: fails to start - breaks install/upgrade
Severity set to `grave' from `normal'
> tags 405704 patch
Bug#405704: imapproxy: fails to start - breaks install/upgrade
There were no tags set.
T
10 matches
Mail list logo
