Accepted cproto 4.7m-4 (source amd64) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 20 Jun 2016 13:08:16 -0500
Source: cproto
Binary: cproto
Architecture: source amd64
Version: 4.7m-4
Distribution: unstable
Urgency: medium
Maintainer: Kenneth J. Pronovici <pronovic@debian.org>
Changed-By: Kenneth J. Pronovici <pronovic@debian.org>
Description:
cproto - utilities to generate C function prototypes from C source code
Changes:
cproto (4.7m-4) unstable; urgency=medium
.
* Bump standards version to 3.9.8.0 (no packaging changes).
* Export "DEB_BUILD_MAINT_OPTIONS = hardening=+all" in debian/rules.
* Fix FTBFS in the Debian Reproducible Builds environment.
- FTBFS caused by mis-use of the $CPROTO environment variable
- Add patches/program.patch to use $PROGRAM rather than $CPROTO
- Adjust debian/tests/unittest to use $PROGRAM rather than $CPROTO
Checksums-Sha1:
a97c52dccef23176400274c263905022535cc9b3 1748 cproto_4.7m-4.dsc
20ef2d96d3e63d00251e5ebbde8f602f32e32f2f 7368 cproto_4.7m-4.debian.tar.xz
1775ecf3535b5fcbad86b598379bd0a9e0372461 60670 cproto-dbgsym_4.7m-4_amd64.deb
6bf8a1ce0fda34bd618545f132a58ed10dfbffce 53298 cproto_4.7m-4_amd64.deb
Checksums-Sha256:
a0c5c68b09efe66f961be3c4b381ff54c628185e1edfbd0e6078dfb2cfcd771f 1748 cproto_4.7m-4.dsc
bbea0304680468e0511b8233a2af7b635ea6ff386f15314c109f36dea712a9bf 7368 cproto_4.7m-4.debian.tar.xz
081472867abd50a7c419a910a7110a487c0f00875b31700cd1d726e42e77e26e 60670 cproto-dbgsym_4.7m-4_amd64.deb
72f42d5bc835478590f835a774b3c6c15061ed8b589c33e7c68bf4d2824b313c 53298 cproto_4.7m-4_amd64.deb
Files:
953ddd3b841be05f987f41c9547b18ea 1748 devel optional cproto_4.7m-4.dsc
96ced7cdc29d5c50a941a4dfd8bf5dd3 7368 devel optional cproto_4.7m-4.debian.tar.xz
bf213feec9a7b5fc0bd87ad89357c827 60670 debug extra cproto-dbgsym_4.7m-4_amd64.deb
7b252d7b9b26d43a8b7875337f9ffcc6 53298 devel optional cproto_4.7m-4_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJXaEtsAAoJEBEZKJLv11k0dFYQALLxkQdGPxJxMW99vCPYHgXV
ZrInu+Hl/VYZeNqeBX6ZHSX8inOwI1oniFMtt+4yFtvxuGN6VDLGvq9Lu5A0igit
Eu2lxzImhykfunHzo08ywhM0GMjqBLnhoGWggZXt57Summjt3MNzJyp1DE856MKM
BGQs+ZVQz30qm7L7XwTKoPSCdDBME36klNglUlzYHW8gZEV9e0p0JRt/EmvJsSwo
fwoASzkVnAQZKfSbmZRGrN8aU4NpvqIdG9UzRtigVZfZp1YRQ5KxOSXGOe2vp7r6
fCkVJ6yV/G/viL6q9YmH7CrawfKikb5kZNBQvVrrjKtZxPMasdxFxp0RJy0bu9xP
sLOHLGsXv/BZmhJxzxrbqXgWWQhUSSgewY4pxVMFeFCEgiSrVKaUm5h7M3+ACl3U
HeqYZxZkFm4h2c83+xDbBrtoiELp1m73FE6n+5+5ixq/nQM0Hy+oFtlpDM2FbUMU
/AxQ0KxD8alPADW50GC0mHLuDg9VItKFV7AykmXHbaSW0HsuKd1F8ZC0SWPa3E0X
6EXkPMlgYMmcofNO22M8l7X3mslbujgBo+jhiq/GlNnvM3QtUSkrXxOC779/OgLQ
mZSheYIyyN/eBUQcsmVpe3YAebhSnS+Y0ZHMd4L9tqPjeLUNCrSRdsVxlRLSMggN
sId0VPNSQJFWuYuLBD1s
=NJfc
-----END PGP SIGNATURE-----
Reply to: