Accepted libpyzy 1.0.1-6 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 26 Aug 2018 16:47:11 -0400
Source: libpyzy
Binary: libpyzy-1.0-0v5 libpyzy-dev
Architecture: source
Version: 1.0.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org>
Changed-By: Boyuan Yang <073plan@gmail.com>
Description:
libpyzy-1.0-0v5 - Chinese PinYin and Bopomofo conversion library
libpyzy-dev - Development files of libpyzy
Closes: 899792
Changes:
libpyzy (1.0.1-6) unstable; urgency=medium
.
* Team upload.
* Apply "wrap-and-sort -abst".
* debian/control:
+ Use debian-input-method mailing list in Maintainer field (Closes: #899792)
+ Update YunQiang Su's email address and use the @debian.org one.
+ Bump debhelper compat to v11.
+ Standards-Version to 4.2.1.
+ Remove unnesessary build-dependency dh-autoreconf.
+ Use git repo on Salsa platform for Vcs fields.
* debian/rules: Modernize rules file and get rid of dpkg-parsechangelog
invocation.
* debian/copyright: Use secure uri.
Checksums-Sha1:
8b73920f12e0100e45a20ae1eb062deacf4a1d09 2359 libpyzy_1.0.1-6.dsc
20d048f4f42df1c6028c90bd07d39933729b25d0 4820 libpyzy_1.0.1-6.debian.tar.xz
661ffeea7c6094874b91cc08e9c2e05e5dcd3a44 7235 libpyzy_1.0.1-6_amd64.buildinfo
Checksums-Sha256:
314010f1dac293e407d49c5dccf91a9117cd39cf682717a5384f795ddd40172d 2359 libpyzy_1.0.1-6.dsc
3d99dc3efc66b7faeb3eb7c7dff216b6684d3d6bf5f107c3608e598d8889dc0c 4820 libpyzy_1.0.1-6.debian.tar.xz
26eb332a6572c618cd376e1d0e8b4c9908fa51b17866e66d179e1d2678a01884 7235 libpyzy_1.0.1-6_amd64.buildinfo
Files:
8533f43e321560eb76bcdd879f376c6d 2359 libs optional libpyzy_1.0.1-6.dsc
96c1fd1fec75cd97723d6ab0da3db393 4820 libs optional libpyzy_1.0.1-6.debian.tar.xz
6ffd7661c6409df10de563fe2b2606a7 7235 libs optional libpyzy_1.0.1-6_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAluDFfcACgkQwpPntGGC
Ws5tPg/9F2gKEFcREtzYez+Zt3/WRkDD4Mfg44B727mwTcmFAoR/Bgo6QgK1BIPn
aBJ/NEGzByT/FB3RDYDjevJi7cjnztp/xXnAqvWTafQ+oDy4STDaBX3Vv9A/P20q
zpQBfkRxFSfPod7Zw+dljePWut0f+UX6r59Kj2fd6wMKkWDbLCagwaPCqo3f8VNe
RyghcOiQE1CSdUc+rJfrhOY6p4RySgmJwwxjoYPCqWeVtCZMk1wmOBZ7DOiJ7l2o
oNV/Z2sIx2PEboWsW8EVvBFaSlp2vb/Znj7+1v93XuT7jMCMp/kyUceVZQFlQnwy
bjE8Q/6IfMKqUAHE81H7e0dDlefSRH0XoSsImuqDgClDgE5Deihx69UzmKiZR4/Z
75M6XjrirjFRSiSEFIVtHNc33jXI4URXj/EUPaCalNzGiCzYM0q7saBUqDDOfVtJ
KjDcOyxxbMR+hvxtg/EKRaCpFefj83ricWLIUhiicpKIz2Mxe3A4wp/kdcMyZ0OR
D3bPODwu67G6i0Y1ENXatf/TxibIjO93q2WeskfW6fZbht6u2enqJAz6eJHz3DfR
6BsmF2LK0KPYzQYg8KFJfE4PiLQL/gS3iikJ3QWM+Pw2RlTdgM9u7g3wnA6/82PF
F8bTccchwsyWe09n1SrXcGsPogVqGFXpLAkEFj9mDIzhoJxT6w4=
=S1mC
-----END PGP SIGNATURE-----
Reply to: