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

Accepted libbpp-phyl 2.4.1-12 (source) into unstable



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

Format: 1.8
Date: Fri, 26 Sep 2025 21:44:17 +0200
Source: libbpp-phyl
Architecture: source
Version: 2.4.1-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
Changed-By: Étienne Mollier <emollier@debian.org>
Closes: 1113116
Changes:
 libbpp-phyl (2.4.1-12) unstable; urgency=medium
 .
   * Team upload.
   * cmake-4.patch: new: bump cmake minimum to 3.10. (Closes: #1113116)
   * d/control: declare compliance to standards version 4.7.2.
   * d/control: remove redundant Rules-Requires-Root: no.
   * d/watch: convert to v5 Github template.
   * d/copyright: remove the old FSF address.
   * d/*lintian-overrides: remove now unused t64 override.
   * d/s/lintian-overrides: glob d/control line number.
     This fixes mismatches caused by variability in the d/control file.
   * d/*lintian-overrides: override conflicts-with-version.
     This overrides is necessary in the context of the t64 transition.
Checksums-Sha1:
 2921ff1f6806d3a3004941e550cba5ed60368e4b 2303 libbpp-phyl_2.4.1-12.dsc
 6d5b5fb1025e03b9dd5742a39fadd3d202baeeec 15448 libbpp-phyl_2.4.1-12.debian.tar.xz
Checksums-Sha256:
 42c5ff87d2d3872d7013fb9fe0d291e04be9e79ecb8fa7d59d3979b0a158fd89 2303 libbpp-phyl_2.4.1-12.dsc
 1e6d1b2f184a4d0e8339d03726a2c7cdd405d333feb3722852cfcbddd805e025 15448 libbpp-phyl_2.4.1-12.debian.tar.xz
Files:
 bcde4224875edb03e9569b890d3b27a6 2303 science optional libbpp-phyl_2.4.1-12.dsc
 996c0b2607885cf412dad0398975dc8c 15448 science optional libbpp-phyl_2.4.1-12.debian.tar.xz

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

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmjW8KUUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqhcA/+PqoGfdEXp9Cuki1hQyj2arJAbJZJ
+kY7dWMELnKSm7/4VDaqkKwUFwwq6bLrmik49w5bfxiAXkXOwfjatQtxvaNIcZju
6vaOnDcDSJGmZPYBwoNJWXhj5hkxTmvfOT0Wq2+cyIdt+C6L/pkiy1wS4rZ8ZELo
bFDqWwqVd8X5619dOl83BRdSP6GRnrrMrDzryFpf2i86WgnlJMXmFFj7eD2KaJCl
ofAtfjWE1drSTkFPrsjNo9zrrFpzauIamPlPIby012O6gjHAOPGeUJsEZKvH6vKJ
67FQYjRq0PykNjLjPKT9xs1F/OqI+rvjhIE7gI2/a0nb/aScD7VXTyc2Iku2ON+p
scuffnkdkoyHg5Zh+tdPAsWzkk+XRbVdTVH7dXAU4vdboRX0CWcoJZKFJ5ep0lH4
9oQKonrFRUvhY2kLsd/fjgvzPBrGjVfkqydyBg0TOmeh25VxfEuf4nxIiQD9Z6xA
8mm6cp16SW1Gsf6gwK7Z2bO4aUPQ6w/0x07nxQkvFH0DCKQjhgOY1+zEmisl3+8R
FrIONHhhhBTAfDFZPPWAzOo6sXjJNis7Q6bN2YZTnbRYCra4ZzcoKes88MAYRD9q
iCtls7CuIGhOM7OkGL/tKg5nGKqi9f+aHaj9d8XD71I33XBsPtSDEtZe7PMZkMGm
sGGCfWAjAD38KsM=
=aj8T
-----END PGP SIGNATURE-----

Attachment: pgpsF4EH09zWw.pgp
Description: PGP signature


Reply to: