ok
___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
reportbug_3.47_i386.changes uploaded successfully to localhost
along with the files:
reportbug_3.47.dsc
reportbug_3.47.tar.gz
reportbug_3.47_all.deb
Greetings,
Your Debian queue daemon
___
Reportbug-maint mailing list
Reportbug-maint@list
Your message dated Wed, 12 Nov 2008 16:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#504424: fixed in reportbug 3.47
has caused the Debian Bug report #504424,
regarding reportbug sometimes crash when trying to display bugs
to be marked as done.
This means that you claim tha
Accepted:
reportbug_3.47.dsc
to pool/main/r/reportbug/reportbug_3.47.dsc
reportbug_3.47.tar.gz
to pool/main/r/reportbug/reportbug_3.47.tar.gz
reportbug_3.47_all.deb
to pool/main/r/reportbug/reportbug_3.47_all.deb
Override entries for your package:
reportbug_3.47.dsc - source utils
reportbu
Processing commands for [EMAIL PROTECTED]:
> tag 504424 + pending
Bug#504424: reportbug sometimes crash when trying to display bugs
There were no tags set.
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(
Hi Ryo,
On Wed, Nov 12, 2008 at 14:37, Ryo IGARASHI <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 12, 2008 at 5:22 PM, Sandro Tosi <[EMAIL PROTECTED]> wrote:
>>> FYI, the bug occurs from PuTTY from windows but not from Terminal from
>>> MacOSX.
>>
>> Mh, but the bug still occurs or "occurred"? :) Just
Hi Sandro,
On Wed, Nov 12, 2008 at 5:22 PM, Sandro Tosi <[EMAIL PROTECTED]> wrote:
>> FYI, the bug occurs from PuTTY from windows but not from Terminal from
>> MacOSX.
>
> Mh, but the bug still occurs or "occurred"? :) Just to be clear before
> upload it.
>
> Thanks for your check,
Oh, sorry for
Hi Ryo,
On Wed, Nov 12, 2008 at 07:53, Ryo IGARASHI <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 12, 2008 at 2:38 AM, Sandro Tosi <[EMAIL PROTECTED]> wrote:
>> I prepared a preliminary version here[1]: may you please check if it
>> fixes your bug? I tried to replicate it with reportbug and zsh on a
>>