[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#689425: marked as done (unblock: fcitx-googlepinyin/0.1.6-1)

Your message dated Sun, 21 Apr 2013 23:28:08 +0100
with message-id <1366583288.23177.87.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#689425: unblock: fcitx-googlepinyin/0.1.6-1
has caused the Debian Bug report #689425,
regarding unblock: fcitx-googlepinyin/0.1.6-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
689425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689425
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock


This is a relatively big debdiff, but most of the noise are come from
the newly added svg files which show up as text files in diff. These
changes are limiting the input and install icons to avoid crashing
fcitx main program. Even when known issues in fcitx has already been
fixed, it would be good to make fcitx-googlepinyin safer.

unblock: fcitx-googlepinyin/0.1.6-1


-- 
Regards,
Aron Xu

Attachment: fcitx-googlepinyin_0.1.6-1.debdiff
Description: Binary data


--- End Message ---
--- Begin Message --- 
On Tue, 2012-10-02 at 21:29 +0800, Aron Xu wrote:
> This is a relatively big debdiff, but most of the noise are come from
> the newly added svg files which show up as text files in diff. These
> changes are limiting the input and install icons to avoid crashing
> fcitx main program. Even when known issues in fcitx has already been
> fixed, it would be good to make fcitx-googlepinyin safer.

Apologies for not having finalised this one way or the other at an
earlier point. Unfortunately, it's now too late to get these changes in
before the release.

Regards,

Adam

--- End Message ---
Reply to: