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

Bug#914236: marked as done (ibus-chewing: Should we upgrade to v1.6.1?)

Your message dated Sat, 5 Jan 2019 11:47:01 +0800
with message-id <[🔎] 20190105034701.GA27241@gmail.com>
and subject line Re: Bug#914236: ibus-chewing: Should we upgrade to v1.6.1?
has caused the Debian Bug report #914236,
regarding ibus-chewing: Should we upgrade to v1.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.)


-- 
914236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914236
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: ibus-chewing
Version: 1.5.1-3
Severity: normal
X-Debbugs-CC: mwei@debian.org czchen@debian.org

I noticed that ibus-chewing is tagging some new releases but didn't
explicitly list them on
https://github.com/definite/ibus-chewing/releases .

@mwei @czchen I'm wondering if they are official upstream releases and
whether we should package them in Debian for Debian Buster.

--
Thanks,
Boyuan Yang

--- End Message ---
--- Begin Message --- 
Control: fixed -1 1.6.1-1

On Tue, Nov 20, 2018 at 03:14:58PM -0500, Boyuan Yang wrote:
> Source: ibus-chewing
> Version: 1.5.1-3
> Severity: normal
> X-Debbugs-CC: mwei@debian.org czchen@debian.org
> 
> I noticed that ibus-chewing is tagging some new releases but didn't
> explicitly list them on
> https://github.com/definite/ibus-chewing/releases .
> 
> @mwei @czchen I'm wondering if they are official upstream releases and
> whether we should package them in Debian for Debian Buster.

Fixed by uploading 1.6.1-1.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: