Dear mentors,

I am looking for a sponsor for my package "sunpinyin".

* Package name    : sunpinyin
  Version         : 2.0.2~git20100627-1
  Upstream Author : Lei Zhang <phill.zh...@sun.com>
                                Ervin Yan <ervin....@sun.com>
                                Yong Sun <m...@yongsun.me>
                                Kefu Chai <tchai...@gmail.com>
                                Wei Xue <wei....@sun.com>
                                Leo Zheng <zym...@gmail.com>
                                chumsdock <vor...@gmail.com>
                                Mike Qin<mikeandm...@gmail.com>
* URL             : http://code.google.com/p/sunpinyin
* License         : LGPL-2.1 or CDDL
  Section         : libs

It builds these binary packages:
libsunpinyin-dev - Simplified Chinese Input Method from SUN
libsunpinyin3 - Simplified Chinese Input Method from SUN
sunpinyin-utils - Simplified Chinese Input Method from SUN

The package appears to be lintian clean.

The upload would fix these bugs: 478811

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/s/sunpinyin
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/s/sunpinyin/sunpinyin_2.0.2~git20100627-1.dsc

The initial ITP is not reported by me, I've contacted with the original 
reporter kefu chai and he allowed me to work on this package[1]. 

I've uploaded ibus-sunpinyin too, which can be downloaded with 
dget http://mentors.debian.net/debian/pool/main/i/ibus-sunpinyin/ibus-
sunpinyin_2.0.2~git20100628-1.dsc
Even it is not in good shape(lack of some Build-Depends and Depends and cannot 
be compiled in my pbuilder), it can be used to verify sunpinyin.

I would be glad if someone uploaded this package for me.

[1] http://lists.debian.org/debian-mentors/2010/06/msg00460.html
Kind regards
-- 
Liang Guo
http://bluestone.cublog.cn

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to