Accepted pycparser 2.21-1 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 12 Nov 2021 23:26:00 -0800
Source: pycparser
Architecture: source
Version: 2.21-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+python@tracker.debian.org>
Changed-By: Stefano Rivera <stefanor@debian.org>
Changes:
pycparser (2.21-1) unstable; urgency=medium
.
* New upstream release.
* Refresh patches.
* Stage examples and fake_libc in build area for build-time tests.
* Use unittest discover in autopkgtests, the upstream test runner has been
removed.
* Stage examples in the temporary directory for autopkgtests.
* Depend on gcc for autopkgtests, there's an example using gcc -E.
Checksums-Sha1:
0d09f80b5bb16f22cb51cef93311907f7ec8021a 1458 pycparser_2.21-1.dsc
359c718c6ece361047f61846b9fa4ea0239576dc 170877 pycparser_2.21.orig.tar.gz
7bd6aa9579aa1bef1493ee6a0fca1df784cf6754 5080 pycparser_2.21-1.debian.tar.xz
80874f2a3b02003d10b30620b1e68811ef677222 5604 pycparser_2.21-1_source.buildinfo
Checksums-Sha256:
34529f68229c4dfef8d878d7a4d703a6261850ebebfe3c6c426139a51e03f073 1458 pycparser_2.21-1.dsc
e644fdec12f7872f86c58ff790da456218b10f863970249516d60a5eaca77206 170877 pycparser_2.21.orig.tar.gz
e925ab3b1e435bd860186876e888fc4edd8267382a72676726236443f6ab208a 5080 pycparser_2.21-1.debian.tar.xz
850387da9f81db4c4cc3d3d73b542dcc8cb54dee3d736955afd1d50f58665c82 5604 pycparser_2.21-1_source.buildinfo
Files:
b29f1943e644fa77e0b105e5e308cdec 1458 python optional pycparser_2.21-1.dsc
48f7d743bf018f7bb2ffc5fb976d1492 170877 python optional pycparser_2.21.orig.tar.gz
c6e7b9e8191156b78f7eb147d4c97af8 5080 python optional pycparser_2.21-1.debian.tar.xz
ac19c6ed0cc9a6bbcc8e5602be82b00f 5604 python optional pycparser_2.21-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYY9ophQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2PUjAQDiLPnPZq3zP7UgkCflAIa9Uf4AsYik
CWD+w6hBhgt6wQD/Tka4tzbTHj+jUzQbH3JiSmNOMvuX1341DzfGZiYd9gc=
=/Ut4
-----END PGP SIGNATURE-----
Reply to: