Accepted picocom 1.7-2 (source amd64) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Fri, 02 Jun 2017 22:21:14 +0000
Source: picocom
Binary: picocom
Architecture: source amd64
Version: 1.7-2
Distribution: unstable
Urgency: high
Maintainer: Matt Palmer <mpalmer@debian.org>
Changed-By: W. Martin Borgert <debacle@debian.org>
Description:
picocom - minimal dumb-terminal emulation program
Closes: 863671
Changes:
picocom (1.7-2) unstable; urgency=high
.
* Fix CVE-2015-9059 (Closes: #863671).
* Add myself to Uploaders.
* Add Vcs fields.
Checksums-Sha1:
cbac46fbd56832814c74279a7b6ad25cbcd98a07 1867 picocom_1.7-2.dsc
0c04b32d75873bc2ac20dc94745b6fe13ace3ecb 6564 picocom_1.7-2.debian.tar.xz
ccd3345908e420b26a305ffa3215297a45d1c379 12912 picocom-dbgsym_1.7-2_amd64.deb
dca5ca4090da191ce6694d6d0d3bcff64c154478 5566 picocom_1.7-2_amd64.buildinfo
49848e328dde79c6c5b2511d1d20b4f9b9d46493 21858 picocom_1.7-2_amd64.deb
Checksums-Sha256:
663bc082a01a6df2724772d64fab35b52ffcae16cfa67dcd1ea1b9d44c0c506a 1867 picocom_1.7-2.dsc
0e94e76b40b5f5c4260211b6320d17d509d8a01bc52da3d3ab81bfca148cfeb1 6564 picocom_1.7-2.debian.tar.xz
9076cd75aab07e10c002be4cfa39b6dcbb4eade0c07d6b1b037a9eb99761381e 12912 picocom-dbgsym_1.7-2_amd64.deb
d58bcbbb50c3eef80962e99cdb9b2afbf5359cce80fb714309f287832d510b49 5566 picocom_1.7-2_amd64.buildinfo
fa6e9c0144a65d58b4c5871f6e7c4284d901a1b52f8e7ca73d854a643c1aa032 21858 picocom_1.7-2_amd64.deb
Files:
e53caa751cec335e838b5590eb3a1324 1867 comm optional picocom_1.7-2.dsc
867075fecdfae4998289d8553a452317 6564 comm optional picocom_1.7-2.debian.tar.xz
6d8f552b3898421dc6f942edc50d714e 12912 debug extra picocom-dbgsym_1.7-2_amd64.deb
265dfe334648373cff7c4495e456e597 5566 comm optional picocom_1.7-2_amd64.buildinfo
84f5f539da5c0db9afb36010e1527f77 21858 comm optional picocom_1.7-2_amd64.deb
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAlkx6qcACgkQ4+Chwoa5
Y+pIQQ//Z8LujfOtD2YPZnCB/+CAEA4iFNBOao1Ev22iAafm6f8q8nCKfA6AJOkq
PB3I8kOiig0rmLHoTptuT8e5e4HjAklIIYtVSELsRh1whLkD8cDIdPwPbS7g89b4
SSfyXUn05gnxszr6jA1FS+yKWNk4pV5079oX3Oqu4YVKjCb8zlC/p7W6Wnv7J5AV
+wThrhNlvJh2NWFthidVsAkUQFQgGOIVbhp9H6LSb3ZKzAD/9NvGjqlPe1tTOQ+4
L5nAEUEvSyh/dwvmBOeTUyXe44M3km9eNJ1cj9586yfBgmQm2kgqkhYUGF7icfqm
86/LvDvMxx+TrG2CuRv6lIHzvbOBSdGBaK2PMBUU7tKEStQlwBc66450k9iB9oWZ
U8uMK5jO34K4yKuPVfK2BDUkeWxPowMpa1u1GJK8mpcwBh7hfjorWA09az3w3iwM
UqPakQz06GkxeHFBdFWez5JPnE0nzhUh35gts1xE7Abw2OSj0Tf/vSYq6rpoqIKG
/j3YSCQNTdFdcGiGtDDXvIRhu23L1V3LcbDoJcSIlGK6VMJ/RqUhQYOrztdsgPKm
1UetrPJucOm/GxS7vxLUzJdnl5Z7BMRnQ5MX0raw6Z32fcsIZ++u4NuNFePwSEVL
6VbhYhXggHgpOM/5RVnJpj8lRNAcRUIGHkom10VdZVe7DZFbAGQ=
=4E8J
-----END PGP SIGNATURE-----
Reply to: