Your message dated Tue, 3 Jul 2018 01:28:03 +0200
with message-id <[email protected]>
and subject line Re: Bug#902675: RFS: fcitx/1:4.2.9.6-3
has caused the Debian Bug report #902675,
regarding RFS: fcitx/1:4.2.9.6-3
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 [email protected]
immediately.)
--
902675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902675
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: [email protected] [email protected]
[email protected]
Dear Aron, Mike, debian-input-method members and mentors,
As part of bug fixes and package rebuild in Debian Input Method Team, I
prepared a team upload for package "fcitx" and I'm currently looking for a
sponsor for this package.
Besides, I am looking for a DD to help to grant me write permission to fcitx's
git repository on Salsa (https://salsa.debian.org/debian/fcitx) so that I could
push my work onto the repository. A temporary git repo has been set up on Salsa
already (https://salsa.debian.org/hosiet-guest/fcitx).
Levels of rebuild (and bugfix):
Level 1:
* libmarisa0 (done), libopencc2 (done)
Level 2:
* libbkc2 (done), libkkc-data (done), librime1 (done)
Level 3:
* brise (done), fcitx
^ we are here
Level 4:
* fcitx-kkc, ibus-kkc, fcitx-rime, ibus-rime, goldendict (out of team but
under my control), ibus-libzhuyin
* Package name : fcitx
Version : 1:4.2.9.6-3
Upstream Author : Weng Xuetian <[email protected]>
* URL : https://gitlab.com/fcitx/fcitx
* License : GPL-2+
Section : utils
It builds those binary packages:
fcitx - Flexible Input Method Framework
fcitx-bin - Flexible Input Method Framework - essential binaries
fcitx-data - Flexible Input Method Framework - essential data files
fcitx-frontend-all - Flexible Input Method Framework - frontends metapackage
fcitx-frontend-gtk2 - Flexible Input Method Framework - GTK+ 2 IM Module
frontend
fcitx-frontend-gtk3 - Flexible Input Method Framework - GTK+ 3 IM Module
frontend
fcitx-frontend-qt4 - Flexible Input Method Framework - Qt4 IM Module frontend
fcitx-libs - Flexible Input Method Framework - metapackage for libraries
fcitx-libs-dev - Flexible Input Method Framework - library development files
fcitx-module-dbus - Flexible Input Method Framework - D-Bus module and IPC
frontend
fcitx-module-kimpanel - Flexible Input Method Framework - KIMPanel protocol
module
fcitx-module-lua - Flexible Input Method Framework - Lua module
fcitx-module-x11 - Flexible Input Method Framework - X11 module and XIM
frontend
fcitx-modules - Flexible Input Method Framework - core modules
fcitx-pinyin - Flexible Input Method Framework - classic Pinyin engine
fcitx-qw - Flexible Input Method Framework - QuWei engine
fcitx-table - Flexible Input Method Framework - table engine
fcitx-table-all - Flexible Input Method Framework - tables metapackage
fcitx-table-bingchan - Flexible Input Method Framework - Bingchan table
fcitx-table-cangjie - Flexible Input Method Framework - Cangjie table
fcitx-table-dianbaoma - Flexible Input Method Framework - Dianbaoma table
fcitx-table-erbi - Flexible Input Method Framework - Erbi table
fcitx-table-wanfeng - Flexible Input Method Framework - Wanfeng table
fcitx-table-wbpy - Flexible Input Method Framework - WubiPinyin table
fcitx-table-wubi - Flexible Input Method Framework - Wubi table
fcitx-table-ziranma - Flexible Input Method Framework - Ziranma table
fcitx-tools - Flexible Input Method Framework - various tools
fcitx-ui-classic - Flexible Input Method Framework - Classic user interface
gir1.2-fcitx-1.0 - GObject introspection data for fcitx
libfcitx-config4 - Flexible Input Method Framework - configuration support
library
libfcitx-core0 - Flexible Input Method Framework - library of core functions
libfcitx-gclient1 - Flexible Input Method Framework - D-Bus client library for
Glib
libfcitx-qt0 - Flexible Input Method Framework - Meta package for Qt library
libfcitx-utils0 - Flexible Input Method Framework - utility support library
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/fcitx
Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/f/fcitx/fcitx_4.2.9.6-3.dsc
Git packaging repository (the canonical one):
https://salsa.debian.org/debian/fcitx
Git packaging repository (temporary, contains my work):
https://salsa.debian.org/hosiet-guest/fcitx
Changes since the last upload:
fcitx (1:4.2.9.6-3) unstable; urgency=medium
.
* Team upload.
* Manual rebuild against opencc 1.0.5.
* Use GitLab repository as upstream homepage to coordinate with
upstream project migration.
* Install fcitx4-config into fcitx-bin instead of fcitx-libs-dev.
This partially solves #806567.
* d/rules: Pass "--as-needed" option to the linker.
--
Regards,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
On Fri, Jun 29, 2018 at 08:14:40PM +0800, Boyuan Yang wrote:
> Besides, I am looking for a DD to help to grant me write permission to fcitx's
> git repository on Salsa (https://salsa.debian.org/debian/fcitx) so that I
> could
> push my work onto the repository. A temporary git repo has been set up on
> Salsa
> already (https://salsa.debian.org/hosiet-guest/fcitx).
Perms granted; I didn't push your changes.
> Changes since the last upload:
>
> fcitx (1:4.2.9.6-3) unstable; urgency=medium
> .
> * Team upload.
> * Manual rebuild against opencc 1.0.5.
> * Use GitLab repository as upstream homepage to coordinate with
> upstream project migration.
> * Install fcitx4-config into fcitx-bin instead of fcitx-libs-dev.
> This partially solves #806567.
> * d/rules: Pass "--as-needed" option to the linker.
Looks good, although I didn't test the functionality. Uploaded.
喵!
--
⢀⣴⠾⠻⢶⣦⠀ There's an easy way to tell toy operating systems from real ones.
⣾⠁⢰⠒⠀⣿⡁ Just look at how their shipped fonts display U+1F52B, this makes
⢿⡄⠘⠷⠚⠋⠀ the intended audience obvious. It's also interesting to see OSes
⠈⠳⣄⠀⠀⠀⠀ go back and forth wrt their intended target.
--- End Message ---
