Debian Package Tracker
Register | Log in
Subscribe

python-bcrypt

password hashing library for Python 3

Choose email to subscribe with

general
  • source: python-bcrypt (main)
  • version: 5.0.0-7
  • maintainer: Debian Python Team (DMD)
  • uploaders: Simon Fondrie-Teitler [DMD]
  • arch: any
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 3.1.7-4
  • oldstable: 3.2.2-1
  • stable: 4.2.0-2.1
  • testing: 5.0.0-6
  • unstable: 5.0.0-7
versioned links
  • 3.1.7-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.2.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 4.2.0-2.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 5.0.0-6: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 5.0.0-7: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • python3-bcrypt
action needed
Depends on packages which need a new maintainer normal
The packages that python-bcrypt depends on which need a new maintainer are:
  • rust-bcrypt-pbkdf (#1081722)
    • Build-Depends: librust-bcrypt-pbkdf-dev
Created: 2024-09-14 Last update: 2026-10-11 20:00
lintian reports 2 warnings normal
Lintian reports 2 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2026-08-03 Last update: 2026-08-03 02:32
debian/patches: 1 patch to forward upstream low

Among the 3 debian patches available in version 5.0.0-6 of the package, we noticed the following issues:

  • 1 patch where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2025-09-11 Last update: 2026-08-03 09:00
testing migrations
  • excuses:
    • Migration status for python-bcrypt (5.0.0-6 to 5.0.0-7): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
    • Issues preventing migration:
    • ∙ ∙ Missing build on riscv64
    • ∙ ∙ Piuparts check waiting for test results - https://piuparts.debian.org/sid/source/p/python-bcrypt.html
    • ∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
    • ∙ ∙ Autopkgtest for ansible/14.0.0+dfsg-1: amd64: Test triggered, arm64: Test triggered (will not be considered a regression) ♻ (reference ♻), armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for azure-cli/2.91.0-1: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for biomaj3/3.1.24-6: amd64: Test triggered, arm64: Test triggered, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Test triggered, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for biomaj3-daemon/3.0.24-4: amd64: Test triggered, arm64: Test triggered, armhf: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for biomaj3-download/3.2.12-4: amd64: Test triggered, arm64: Test triggered, armhf: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for biomaj3-process/3.0.19-5: amd64: Test triggered, arm64: Test triggered, armhf: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for biomaj3-user/3.0.12-2: amd64: Test triggered, arm64: Test triggered, armhf: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for ceph/20.2.4+ds-1: amd64: Test triggered (will not be considered a regression) ♻ (reference ♻), arm64: Test triggered (will not be considered a regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻ (reference ♻), i386: Test triggered, ppc64el: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for flask-bcrypt/1.0.1-3: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for ironic/1:35.0.1-10: amd64: Test triggered (will not be considered a regression) ♻ (reference ♻), arm64: Test triggered (will not be considered a regression) ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for keystone/2:30.0.0-1: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for paramiko/5.0.0-1: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-asyncssh/2.24.0-2: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-bcrypt/5.0.0-7: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-cryptography/49.0.0-2: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-django/3:5.2.17-2: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), armhf: Pass, i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), s390x: Pass
    • ∙ ∙ Autopkgtest for python-ironic-lib/7.0.0-3: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-oslo.middleware/8.2.0-2: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-proton-core/0.7.0-1: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-pwdlib/0.3.1-1: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for radicale/3.7.8+ds-3: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for spyder/6.1.7+ds-2: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), armhf: Pass, i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), s390x: Ignored failure ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for tryton-server/7.0.56-1: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for twisted/26.4.0-4: amd64: Test triggered, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
    • ∙ ∙ Lintian check waiting for test results - info
    • ∙ ∙ Reproducibility check waiting for results on amd64 - info
    • ∙ ∙ Reproducibility check waiting for results on arm64 - info
    • ∙ ∙ Reproducibility check waiting for results on i386 - info
    • ∙ ∙ Too young, only 0 of 5 days old
    • Additional info (not blocking):
    • ∙ ∙ Reproduced on armhf - info
    • Not considered
news
[rss feed]
  • [2026-10-11] Accepted python-bcrypt 5.0.0-7 (source) into unstable (Colin Watson)
  • [2026-08-06] python-bcrypt 5.0.0-6 MIGRATED to testing (Debian testing watch)
  • [2026-08-02] Accepted python-bcrypt 5.0.0-6 (source) into unstable (Colin Watson)
  • [2026-04-09] python-bcrypt 5.0.0-5 MIGRATED to testing (Debian testing watch)
  • [2026-03-31] Accepted python-bcrypt 5.0.0-5 (source) into unstable (Colin Watson)
  • [2026-03-20] python-bcrypt 5.0.0-4 MIGRATED to testing (Debian testing watch)
  • [2026-03-17] Accepted python-bcrypt 5.0.0-4 (source) into unstable (Jelmer Vernooij) (signed by: Jelmer Vernooij)
  • [2025-12-12] python-bcrypt 5.0.0-3 MIGRATED to testing (Debian testing watch)
  • [2025-12-08] Accepted python-bcrypt 5.0.0-3 (source) into unstable (Colin Watson)
  • [2025-12-07] python-bcrypt 5.0.0-2 MIGRATED to testing (Debian testing watch)
  • [2025-12-03] Accepted python-bcrypt 5.0.0-2 (source) into unstable (Colin Watson)
  • [2025-10-22] Accepted python-bcrypt 5.0.0-1 (source) into unstable (Colin Watson)
  • [2025-10-15] python-bcrypt 4.3.0-2 MIGRATED to testing (Debian testing watch)
  • [2025-10-13] Accepted python-bcrypt 4.3.0-2 (source) into unstable (Colin Watson)
  • [2025-09-14] python-bcrypt 4.3.0-1 MIGRATED to testing (Debian testing watch)
  • [2025-09-10] Accepted python-bcrypt 4.3.0-1 (source) into unstable (Bastian Germann) (signed by: bage@debian.org)
  • [2024-11-20] python-bcrypt 4.2.0-2.1 MIGRATED to testing (Debian testing watch)
  • [2024-11-18] Accepted python-bcrypt 4.2.0-2.1 (source) into unstable (Thomas Goirand)
  • [2024-10-10] python-bcrypt 4.2.0-2 MIGRATED to testing (Debian testing watch)
  • [2024-10-07] Accepted python-bcrypt 4.2.0-2 (source) into unstable (Colin Watson)
  • [2024-08-18] python-bcrypt 4.2.0-1 MIGRATED to testing (Debian testing watch)
  • [2024-08-15] Accepted python-bcrypt 4.2.0-1 (source) into unstable (Bastian Germann) (signed by: bage@debian.org)
  • [2024-06-29] python-bcrypt 4.1.2-1 MIGRATED to testing (Debian testing watch)
  • [2024-06-26] Accepted python-bcrypt 4.1.2-1 (source) into unstable (Bastian Germann) (signed by: bage@debian.org)
  • [2023-01-16] Accepted python-bcrypt 3.2.2-1~bpo11+1 (source) into bullseye-backports (Bastian Germann) (signed by: bage@debian.org)
  • [2023-01-10] python-bcrypt 3.2.2-1 MIGRATED to testing (Debian testing watch)
  • [2023-01-03] Accepted python-bcrypt 3.2.2-1 (source) into unstable (Bastian Germann) (signed by: bage@debian.org)
  • [2021-11-22] Accepted python-bcrypt 3.2.0-1~bpo11+1 (source amd64) into bullseye-backports, bullseye-backports (Debian FTP Masters) (signed by: Luca Boccassi)
  • [2021-10-12] python-bcrypt 3.2.0-1 MIGRATED to testing (Debian testing watch)
  • [2021-10-09] Accepted python-bcrypt 3.2.0-1 (source) into unstable (Gordon Ball)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian (0, 2)
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 5.0.0-6
  • 1 bug

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing