Accepted php-codesniffer 3.2.3-1 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 27 Feb 2018 13:46:52 -1000
Source: php-codesniffer
Binary: php-codesniffer
Architecture: source
Version: 3.2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers <pkg-php-pear@lists.alioth.debian.org>
Changed-By: David Prévot <taffit@debian.org>
Description:
php-codesniffer - PHP, CSS and JavaScript coding standard analyzer and checker
Changes:
php-codesniffer (3.2.3-1) unstable; urgency=medium
.
[ Greg Sherwood ]
* Prepare for 3.2.3 release
.
[ David Prévot ]
* Move project repository to salsa.d.o
* Update Standards-Version to 4.1.3
* Update manpages
Checksums-Sha1:
4c9985530f782c6d61afc0218da2f08db9c3c87a 1777 php-codesniffer_3.2.3-1.dsc
6f970c9a385e62a81b75e7fb0483524a2ecd6402 560524 php-codesniffer_3.2.3.orig.tar.gz
d502f50fd07ee9f605d9a7a2cbca95512aca35e4 10492 php-codesniffer_3.2.3-1.debian.tar.xz
Checksums-Sha256:
929128ac7271cfcf0e985d3e42a9b60f839145dbac38722137c4635513b45914 1777 php-codesniffer_3.2.3-1.dsc
eea9fc447b424a01e892be28970f30ba49810528291f70e8f36935ed12caf138 560524 php-codesniffer_3.2.3.orig.tar.gz
2715c8d3c47c3e4a0174d670d0a5405030bd1f74f5b1ca37f9b89169289c8810 10492 php-codesniffer_3.2.3-1.debian.tar.xz
Files:
a3e77d00545564342b93c043a158c84f 1777 php optional php-codesniffer_3.2.3-1.dsc
b799f3bad2c6435fca817a76900c8160 560524 php optional php-codesniffer_3.2.3.orig.tar.gz
4569f02b658298da061d5063e59b60e5 10492 php optional php-codesniffer_3.2.3-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAlqV8ZEACgkQBYwc+UT2
vTwboAf6A4ns0aOWJOU5+b8po7IQYlVBbh59gn2Q/+LqgcDka9x/lAzPCvH728vo
5eEG3M0RiVp4Ta/jx+HduYnR0CPBTxBOJV6yuEYbmuyKTTkNasmuOZVw/fFCmSNX
qpVYRG6tEoxtdFZrzwe4I/kJ1yO2VCtxHSIQ6QXGD2c2woGg98pEslBG7NFCmTvp
kbgmw7jU673QKlS2PWY/qUivylz9yP5AYn/75hRYvsuT8pnoOJIHtjjpygIzS8Bz
rq7z6pfoFMDOFVxSPed/z3rQY9qjKgzOpi+shKWE7W7XTFn3rKzS+djvv119mtOM
+lUgSqqXeOZs7RU7isGnuNhYNo/DDg==
=DJzV
-----END PGP SIGNATURE-----
Reply to: