Accepted flask-bcrypt 0.7.1-3 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 02 May 2022 20:42:39 -0400
Source: flask-bcrypt
Architecture: source
Version: 0.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+python@tracker.debian.org>
Changed-By: Sandro Tosi <morph@debian.org>
Changes:
flask-bcrypt (0.7.1-3) unstable; urgency=medium
.
[ Ondřej Nový ]
* Bump Standards-Version to 4.4.1.
* d/control: Update Maintainer field with new Debian Python Team
contact address.
* d/control: Update Vcs-* fields with new Debian Python Team Salsa
layout.
.
[ Debian Janitor ]
* Use secure URI in Homepage field.
* Update standards version to 4.5.0, no changes needed.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Apply multi-arch hints.
+ python-flask-bcrypt-doc: Add Multi-Arch: foreign.
* Bump debhelper from old 12 to 13.
* Update standards version to 4.5.1, no changes needed.
Checksums-Sha1:
9cd88ec83981af7e31f145773e138073c9fd06a2 2190 flask-bcrypt_0.7.1-3.dsc
cc1f31002a3a741a85817920b9cff8ccded42569 3368 flask-bcrypt_0.7.1-3.debian.tar.xz
cfcd12706c9d45645dd75edf659a309b43077a13 7850 flask-bcrypt_0.7.1-3_source.buildinfo
Checksums-Sha256:
88d089a4250892ddc848a3a3542ced7e06cd5b31c92bb8c669fbd752fd9da8ad 2190 flask-bcrypt_0.7.1-3.dsc
9a74d56f26a6a4d971e42ed7cbe5bdaaa476e4191e8a90fcfd581f8b005c5a8f 3368 flask-bcrypt_0.7.1-3.debian.tar.xz
dd7dea530cf8bfdda84851e0e1ce5aaadf831b8a222f646cd8c19e9bba4f6440 7850 flask-bcrypt_0.7.1-3_source.buildinfo
Files:
a1947b8d718549789c07a17c28ee29e1 2190 python optional flask-bcrypt_0.7.1-3.dsc
ed4015c08ceb7b43c4ee155837154a8e 3368 python optional flask-bcrypt_0.7.1-3.debian.tar.xz
e60294a8f66f4eb81117ef728fc7f578 7850 python optional flask-bcrypt_0.7.1-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmJwesMACgkQh588mTgB
qU9k4Q//Xn3h4LlUt0Gu3cy6Od6vkkGKUK20Qr8O7MKTJ0Fe/UrFen//faSaQznD
G27SXDn/LakK+dvYOkCwnQRySFSY98bnrdQbojEvbABI8D8AfrWu7qdDv8I1dkJH
M5OVwMAT66axNyMBUj2ZBjXcUeZ+VgaJKqqaPsX8novwc7yleehWewzbi/JgZBB1
qiyI8AXbQ6PYnV/Bycg1JOAOLRf35gwSh+KCFbsKEtgncvh/UxunK/l/yOnxt7dl
E+mpRXMIKptzh7d50/j2hJmqvMebBPUERofE5/GJT77+yQYEJKAEsBYpn/6iJ5HX
mbyIRelpZxNWkiPIHPbl/bpCXx4etVfHCym+BHYGV39zDCLUFZM5NfXi8ky0qfg5
HwwH3xCipdlokzuL+bMxId0N1ljCVEwPxNPgGTdA6wIaYHNHoH5qi2y6jbCzuoTT
hLZq/JCO62/40QQHFBQWBrcnaKemNCyk+1dpgiBbj8PHZHoPVKNds61Lh/gX57ks
jogIBV7NzYozBB0oqjEJTMhYwdQAz152RImz2znGE6JdnRpJYRBpZWQRWS03oIRE
EbfJFUsGNSVu6Qmd+lT9V/VcYTEJDqOAFuCrUnh4vXnWzZk8R4RR/jZJl4kxgswq
qL8jfiGNmthSAv91QQrm44BMmGHphXN3MhEVx2d6S6c9Y0NCLn0=
=K0aV
-----END PGP SIGNATURE-----
Reply to: