Your message dated Sat, 13 Apr 2013 16:06:05 +0100 with message-id <1365865565.4627.42.camel@jacala.jungle.funky-badger.org> and subject line Re: Bug#690836: partial review of unblock: fcitx/4.2.4.2-1 has caused the Debian Bug report #690836, regarding unblock: fcitx/4.2.4.2-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.) -- 690836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690836 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: fcitx/4.2.4.2-1
- From: Aron Xu <happyaron.xu@gmail.com>
- Date: Thu, 18 Oct 2012 19:50:39 +0800
- Message-id: <CAMr=8w667mNJ1qjNX-mfxBkvp=ovNFDkyOsKKaH10xHvOpgJ1A@mail.gmail.com>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock This is a new upstream bug fix release for 4.2.4.x stable branch. This branch is established with the intention of being included in Debian Wheezy. 4.2.4.2 comes with all the changes we have already applied to 4.2.4.1 tree, as well as a series of error handling enhancements and bug fixes in the GTK IM Modules. The debdiff is filled with noises, so a diff of the actual code change is also attached. -- Regards, Aron XuAttachment: fcitx_4.2.4.2-1.debdiff
Description: Binary dataAttachment: code.diff
Description: Binary data
--- End Message ---
--- Begin Message ---
- To: Aron Xu <happyaron.xu@gmail.com>, 690836-done@bugs.debian.org
- Cc: Paul Gevers <elbrus@debian.org>
- Subject: Re: Bug#690836: partial review of unblock: fcitx/4.2.4.2-1
- From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Date: Sat, 13 Apr 2013 16:06:05 +0100
- Message-id: <1365865565.4627.42.camel@jacala.jungle.funky-badger.org>
- In-reply-to: <CAMr=8w6C3U7fh_fQW1UWYMjek-m84YN0fMMKM8y4sSfEVk8X3Q@mail.gmail.com>
- References: <CAMr=8w667mNJ1qjNX-mfxBkvp=ovNFDkyOsKKaH10xHvOpgJ1A@mail.gmail.com> <50DD73E7.8060306@debian.org> <CAMr=8w6C3U7fh_fQW1UWYMjek-m84YN0fMMKM8y4sSfEVk8X3Q@mail.gmail.com>
On Sat, 2012-12-29 at 03:32 +0800, Aron Xu wrote: > On Fri, Dec 28, 2012 at 6:26 PM, Paul Gevers <elbrus@debian.org> wrote: > > - I suggest explaining in more detail why this version of the package > > deserves a freeze exception [2]. I don't see any RC or important bugs > > fixed, or release goals achieved, so I DON'T expect the RT to grant > > the unblock. > > This unblock was filed on 18 Oct 2012, at that time freeze wasn't that > deep yet. Your original mail also never made it to -release, most likely due to the size of the diff. Apologies for not having to back to you sooner, but looking at the current state of the package I noticed that unstable now has 4.2.7-2 with a huge debdiff. I'm afraid we can't really look at migrating that package at this point. If there are fixes that you believe are important enough to be fixed still but aren't filed as RC bugs for whatever reason, please let us know. Regards, Adam
--- End Message ---