On Thu, May 7, 2009 at 5:49 PM, S'orlok Reaves <[email protected]> wrote:
> The Burmese responded positively to the khmerOS suggestion, setting up a > central wiki for translators and localization: > http://l10n.my-mm.org/doku.php > At the moment, resources are too limited to do anything else, but this is an > excellent start. This wiki allows us to consolidate information and hopefully > resolve issues such as the various non-conformant encodings of Burmese. Open > Office 3.1 features a Burmese locale; once other tools have been translated, > we can get more involved with the issue of education and training. Good stuff! Unfortunately KhmerOS is in decline, their site is full of spam and people fawning over use of Khmer in non-free stuff like the iPhone or Google. > From my email history, I've noticed that scim-waitzar-1.0.0 is still > awaiting sponsorship, with no major suggestions for improvement. In another > email, Paul, you stated that you are not able to sponsor any packages at the > moment. If that is the case, I was wondering if you could either recommend > someone to sponsor scim-waitzar, or inform me of an unofficial repository I > can submit scim-waitzar to (similar to rpmfusion, but for Deiban instead of > Fedora). I am in no way ungrateful of the expertise you have shared with me; > rather, I just want to upload a stable package (1.0.0) before I start working > on 1.0.1. It is my belief that scim-waitzar fulfills a real and pressing need > in the open-source community: to my knowledge there is NO other romanised > input method for Burmese typists using Debian, and we have reports of people > using scim-waitzar on Ubuntu and Fedora (thanks to alien) as well. I think that was when my key had expired and I wasn't able to upload. In any case I'm not the right person to sponsor waitzar since I'm monolingual and only need to type English. However, I'm happy to review the packaging and leave the testing and sponsoring to those who have more investment in input methods. I've appended a review of the stuff on mentors to the bottom of this mail. I'd suggest contacting the scim/ibus maintainers > Finally, is any Debian mentor able to comment on the new "ibus" > infrastructure? Fedora seems to be intent on replacing scim with ibus; is > Debian also moving that way? Various ibus components are waiting for ftpmaster approval in NEW, so ibus will probably be present in Debian. http://ftp-master.debian.org/new.html ibus-waitzar might be a good thing to create as a result. BTW, do you have any comment on http://bugs.debian.org/456317 ? Package reviews: libwaitzar: watch file doesn't appear to work properly and there is no libwaitzar tarball on Google code. the output of "c++filt < debian/*.symbols" indicates that the library is exporting some symbols in the std namespace when it probably shouldn't, not sure about that though. Also, waitzar::_...@libwaitzar1 looks like a private symbol that should not be exported. c++filt < debian/*.symbols libwaitzar1 contains /usr/share/waitzar/, which violates debian-policy 8.2: http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-support-files The Standards-Version is now outdated, /usr/share/doc/debian-policy/upgrading-checklist.txt.gz lists changes in each version. Please move the config.guess/config.sub subsitution to the configure rule in debian/rules in line with the new recommendations in the latest autotools-dev package. debian/copyright misses that some files are Copyright Prince Ka Naung Project. What about installing ExternalModelTester.cpp as an example in the -dev package? In the upstream code, please consider moving licensing information to the top of files where it is currently at the bottom. The upstream tarball doesn't make it clear that parts of the code are GPLv3 and parts are Apache 2.0. I suggest creating a README.license file to document this fact. Also, there is a COPYING file that only contains the GPLv2. Whats the license of the Java Platform API Documentation that Wait_Zar_Model_API.html mentions its style is based on. The upstream NEWS file doesn't look very useful or accurate. You might want to consider using svn2cl to generate the ChangeLog file too. AUTHORS looks like it could use some additions for the GPL-licensed stuff. You might want to add a README.source file explaining to the ftpmasters something about contents of the data/model2/ directory. The package FTBFS on amd64 sid due to this error (with DPKG_GENSYMBOLS_CHECK_LEVEL=4): .... dh_makeshlibs dpkg-gensymbols: warning: Failed to parse a line in debian/libwaitzar1.symbols: dpkg-gensymbols: warning: Failed to parse a line in debian/libwaitzar1.symbols: dpkg-gensymbols: warning: Failed to parse a line in debian/libwaitzar1.symbols: dpkg-gensymbols: warning: Failed to parse a line in debian/libwaitzar1.symbols: dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libwaitzar1/DEBIAN/symbols doesn't match completely debian/libwaitzar1.symbols --- dpkg-gensymbolsG8EWsa 2009-05-08 06:49:57.000000000 +0000 +++ dpkg-gensymbolsePjTeE 2009-05-08 06:49:57.000000000 +0000 @@ -1,5 +1,6 @@ libwaitzar.so.1 libwaitzar1 #MINVER# * Build-Depends-Package: libwaitzar-dev + hid...@hidden 1.0.0 _zn7waitzar11wordbuilder10typelette...@libwaitzar1 1.0.0 _zn7waitzar11wordbuilder12getlasterro...@libwaitzar1 1.0.0 _zn7waitzar11wordbuilder13getwordstrin...@libwaitzar1 1.0.0 @@ -23,10 +24,12 @@ _zn7waitzar11wordbuilderc1epkcst6vectorisssais...@libwaitzar1 1.0.0 _zn7waitzar11wordbuilderc1epptiippjiis4...@libwaitzar1 1.0.0 _zn7waitzar11wordbuilderc1e...@libwaitzar1 1.0.0 + _zn7waitzar11wordbuilderc1e...@libwaitzar1 1.0.0 _zn7waitzar11wordbuilderc2epkc...@libwaitzar1 1.0.0 _zn7waitzar11wordbuilderc2epkcst6vectorisssais...@libwaitzar1 1.0.0 _zn7waitzar11wordbuilderc2epptiippjiis4...@libwaitzar1 1.0.0 _zn7waitzar11wordbuilderc2e...@libwaitzar1 1.0.0 + _zn7waitzar11wordbuilderc2e...@libwaitzar1 1.0.0 _zn7waitzar11wordbuilderd...@libwaitzar1 1.0.0 _zn7waitzar11wordbuilderd...@libwaitzar1 1.0.0 _zn7waitzar11convertfontepws0...@libwaitzar1 1.0.0 @@ -53,3 +56,4 @@ _znst6vectorijsaijeed...@libwaitzar1 1.0.0 _znst6vectoritsaitee13_m_insert_auxen9__gnu_cxx17__normal_iteratoripts1_ee...@libwaitzar1 1.0.0 _znst6vectoritsaiteed...@libwaitzar1 1.0.0 + libwaitz...@libwaitzar1 1.0.0 scim-waitzar: watch file is broken. I'm not sure what doc/fonts/ is doing, but Debian already contains ttf-sil-padauk. Based on the contents of debian/copyright, how about build-depending on the font packages and generating them at build time? I also suggest switching to DejaVu instead of Bitstream Vera. Some of the source code is derived from other scim input methods and you seem to miss the copyright for those from debian/copyright. The upstream README file contains stuff not useful for most users of the package, you might Same comment as above about the NEWS/ChangeLog files. Why is local.conf in the upstream tarball? Same comment as about about config.guess/sub. Standards-Version again. Shouldn't it build-depend on libwaitzar-dev? The package FTBFS because of this: checking for DEPS... configure: error: Package requirements (waitzar >= 1.0.0) were not met: No package 'waitzar' found -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
