[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted python-depinfo 2.2.0-3 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 01 Dec 2024 16:25:01 +0100
Source: python-depinfo
Architecture: source
Version: 2.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+python@tracker.debian.org>
Changed-By: Étienne Mollier <emollier@debian.org>
Closes: 1083626
Changes:
 python-depinfo (2.2.0-3) unstable; urgency=medium
 .
   * Team upload.
   * d/control: migrate to pyproject.toml.
   * d/control: migrate to autopkgtest-pkg-pybuild.
   * d/control: remove dependency on python3-pkg-resources. (Closes: #1083626)
   * d/control: tests depend on pytest.
   * d/control: add missing test dependencies.
     Those are python3-versioneer and python3-pip; it is worth mentioning
     that the dependency on pip is needed because depinfo tests against pip
     invocations, but not in order to pull missing dependencies as is
     usually the case.
   * d/control: declare compliance to standards version 4.7.0.
   * python3.12.patch: normalize last update timestamp for dep3 compliance.
Checksums-Sha1:
 7fac05e51e2349b59527bfee4f6b28f91d07a87b 2342 python-depinfo_2.2.0-3.dsc
 52b9cc457987f16ee6803f680e886391cded359b 17084 python-depinfo_2.2.0-3.debian.tar.xz
Checksums-Sha256:
 e2af7cb819b8a0c438ba924a4b8a5c2bd57d4ff6dddf31974c938b9ff17290eb 2342 python-depinfo_2.2.0-3.dsc
 ad3e4e925c0feffa7eb610de4b53c3e059c3f1f56a5737a773751a87aaa33306 17084 python-depinfo_2.2.0-3.debian.tar.xz
Files:
 3f87787b7f25821bc1083bf58665d3b2 2342 python optional python-depinfo_2.2.0-3.dsc
 286935a3140e9af93eb95e09c9dab716 17084 python optional python-depinfo_2.2.0-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmdMhU8UHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqjChAAvhF8slSw+nJuBLLwbXHR8q/shuR5
GNR3MrNh3oeyDreoRh9hlHgng/aGYKKFQH7kQAm6qAjILQGN2+vcPHhGZwtwMASS
t79hAN7UlA17ONcfJl9/p3qFjYsldfm6haeWcRIQg9mDRp1WHsQRtjRhADfL4fWs
fm+zbBZ4QRCDZ7uO0q8bta3kqKSXoLkJAIUP2iohZlTOrMnPAqqp74u47RH0wxVn
qL/H29yL2nvBUyRb8NyzHpQaQniWG9TRtgCnNFLbSBrqNYC6d9D039KwgksTV3ym
yOd6e3+bqKGVK2uAc9ZvD1A2OsbdB1NvcZZ/GAi/mqh7llIl1HSXbcoSHyGkSdP/
XWZeY7YwMsn/Q4KadAf22E1QN2TeO6GCairXaXRrWlHpr1uupod9QmdlKNz9lLYm
meMqcZaZoUPvappDDwfr4WQFhZLLQuebeRdbwcTJPE8JH2D+yThXIJhIhC76+JNX
Yg1xqbuPcBxuhKtqa8adNbcB/vJCOxj4+6Yr2aj3YsiewOPxm3OUsFErRjOWoAtw
ZmbCjtvkUstskBYHI2Mp7QLATEOW6fnWSqsWyzdta5lDkvLgpEhLlxyppaQUHx+a
7GCMGgz8QKX/yj4/olrpGCQ7DFOhidaISojj2DHj69SG9yI0hEnmPcWbK847QnWZ
bFh+yNzhjuTDH+8=
=JlMs
-----END PGP SIGNATURE-----

Attachment: pgpeKEsR9MCfp.pgp
Description: PGP signature


Reply to: