Debian Package Tracker
Register | Log in
Subscribe

python-pip

Choose email to subscribe with

general
  • source: python-pip (main)
  • version: 26.1.1+dfsg-1
  • maintainer: Debian Python Team (DMD)
  • uploaders: Stefano Rivera [DMD] – Carl Chenet [DMD]
  • arch: all
  • std-ver: 4.7.3
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 20.3.4-4+deb11u1
  • o-o-sec: 20.3.4-4+deb11u2
  • oldstable: 23.0.1+dfsg-1
  • stable: 25.1.1+dfsg-1
  • testing: 26.0.1+dfsg-1
  • unstable: 26.1.1+dfsg-1
versioned links
  • 20.3.4-4+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 20.3.4-4+deb11u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 23.0.1+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 25.1.1+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 26.0.1+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 26.1.1+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • python3-pip (6 bugs: 0, 5, 1, 0)
  • python3-pip-whl (1 bugs: 0, 0, 1, 0)
action needed
debian/patches: 1 patch with invalid metadata, 1 patch to forward upstream high

Among the 7 debian patches available in version 26.1.1+dfsg-1 of the package, we noticed the following issues:

  • 1 patch with invalid metadata that ought to be fixed.
  • 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: 2023-02-26 Last update: 2026-05-24 09:32
2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:
  • CVE-2026-3219: pip handles concatenated tar and ZIP files as ZIP files regardless of filename or whether a file is both a tar and ZIP file. This behavior could result in confusing installation behavior, such as installing "incorrect" files according to the filename of the archive. New behavior only proceeds with installation if the file identifies uniquely as a ZIP or tar archive, not as both.
  • CVE-2026-6357: pip prior to version 26.1 would run self-update check functionality after installing wheel files which required importing well-known Python modules names. These module imports were intentionally deferred to increase startup time of the pip CLI. The patch changes self-update functionality to run before wheels are installed to prevent newly-installed modules from being imported shortly after the installation of a wheel package. Users should still review package contents prior to installation.
Created: 2026-04-21 Last update: 2026-05-24 05:46
2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:
  • CVE-2026-3219: pip handles concatenated tar and ZIP files as ZIP files regardless of filename or whether a file is both a tar and ZIP file. This behavior could result in confusing installation behavior, such as installing "incorrect" files according to the filename of the archive. New behavior only proceeds with installation if the file identifies uniquely as a ZIP or tar archive, not as both.
  • CVE-2026-6357: pip prior to version 26.1 would run self-update check functionality after installing wheel files which required importing well-known Python modules names. These module imports were intentionally deferred to increase startup time of the pip CLI. The patch changes self-update functionality to run before wheels are installed to prevent newly-installed modules from being imported shortly after the installation of a wheel package. Users should still review package contents prior to installation.
Created: 2026-04-21 Last update: 2026-05-24 05:46
lintian reports 41 warnings normal
Lintian reports 41 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2026-05-24 Last update: 2026-05-24 12:30
1 open merge request in Salsa normal
There is 1 open merge request for this package on Salsa. You should consider reviewing and/or merging these merge requests.
Created: 2025-12-04 Last update: 2025-12-04 19:32
4 low-priority security issues in trixie low

There are 4 open security issues in trixie.

4 issues left for the package maintainer to handle:
  • CVE-2025-8869: (needs triaging) When extracting a tar archive pip may not check symbolic links point into the extraction directory if the tarfile module doesn't implement PEP 706. Note that upgrading pip to a "fixed" version for this vulnerability doesn't fix all known vulnerabilities that are remediated by using a Python version that implements PEP 706. Note that this is a vulnerability in pip's fallback implementation of tar extraction for Python versions that don't implement PEP 706 and therefore are not secure to all vulnerabilities in the Python 'tarfile' module. If you're using a Python version that implements PEP 706 then pip doesn't use the "vulnerable" fallback code. Mitigations include upgrading to a version of pip that includes the fix, upgrading to a Python version that implements PEP 706 (Python >=3.9.17, >=3.10.12, >=3.11.4, or >=3.12), applying the linked patch, or inspecting source distributions (sdists) before installation as is already a best-practice.
  • CVE-2026-1703: (needs triaging) When pip is installing and extracting a maliciously crafted wheel archive, files may be extracted outside the installation directory. The path traversal is limited to prefixes of the installation directory, thus isn't able to inject or overwrite executable files in typical situations.
  • CVE-2026-3219: (needs triaging) pip handles concatenated tar and ZIP files as ZIP files regardless of filename or whether a file is both a tar and ZIP file. This behavior could result in confusing installation behavior, such as installing "incorrect" files according to the filename of the archive. New behavior only proceeds with installation if the file identifies uniquely as a ZIP or tar archive, not as both.
  • CVE-2026-6357: (needs triaging) pip prior to version 26.1 would run self-update check functionality after installing wheel files which required importing well-known Python modules names. These module imports were intentionally deferred to increase startup time of the pip CLI. The patch changes self-update functionality to run before wheels are installed to prevent newly-installed modules from being imported shortly after the installation of a wheel package. Users should still review package contents prior to installation.

You can find information about how to handle these issues in the security team's documentation.

Created: 2025-09-24 Last update: 2026-05-24 05:46
5 low-priority security issues in bookworm low

There are 5 open security issues in bookworm.

5 issues left for the package maintainer to handle:
  • CVE-2023-5752: (needs triaging) When installing a package from a Mercurial VCS URL (ie "pip install hg+...") with pip prior to v23.3, the specified Mercurial revision could be used to inject arbitrary configuration options to the "hg clone" call (ie "--config"). Controlling the Mercurial configuration can modify how and which repository is installed. This vulnerability does not affect users who aren't installing from Mercurial.
  • CVE-2025-8869: (needs triaging) When extracting a tar archive pip may not check symbolic links point into the extraction directory if the tarfile module doesn't implement PEP 706. Note that upgrading pip to a "fixed" version for this vulnerability doesn't fix all known vulnerabilities that are remediated by using a Python version that implements PEP 706. Note that this is a vulnerability in pip's fallback implementation of tar extraction for Python versions that don't implement PEP 706 and therefore are not secure to all vulnerabilities in the Python 'tarfile' module. If you're using a Python version that implements PEP 706 then pip doesn't use the "vulnerable" fallback code. Mitigations include upgrading to a version of pip that includes the fix, upgrading to a Python version that implements PEP 706 (Python >=3.9.17, >=3.10.12, >=3.11.4, or >=3.12), applying the linked patch, or inspecting source distributions (sdists) before installation as is already a best-practice.
  • CVE-2026-1703: (needs triaging) When pip is installing and extracting a maliciously crafted wheel archive, files may be extracted outside the installation directory. The path traversal is limited to prefixes of the installation directory, thus isn't able to inject or overwrite executable files in typical situations.
  • CVE-2026-3219: (needs triaging) pip handles concatenated tar and ZIP files as ZIP files regardless of filename or whether a file is both a tar and ZIP file. This behavior could result in confusing installation behavior, such as installing "incorrect" files according to the filename of the archive. New behavior only proceeds with installation if the file identifies uniquely as a ZIP or tar archive, not as both.
  • CVE-2026-6357: (needs triaging) pip prior to version 26.1 would run self-update check functionality after installing wheel files which required importing well-known Python modules names. These module imports were intentionally deferred to increase startup time of the pip CLI. The patch changes self-update functionality to run before wheels are installed to prevent newly-installed modules from being imported shortly after the installation of a wheel package. Users should still review package contents prior to installation.

You can find information about how to handle these issues in the security team's documentation.

Created: 2023-10-25 Last update: 2026-05-24 05:46
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.3).
Created: 2026-03-31 Last update: 2026-05-24 06:01
testing migrations
  • excuses:
    • Migration status for python-pip (26.0.1+dfsg-1 to 26.1.1+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
    • Issues preventing migration:
    • ∙ ∙ Autopkgtest for afdko/4.0.1+dfsg1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for astroid/4.1.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for click/0.5.2-11: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for datasette/0.65.2+ds-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for doit/0.36.0-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-29: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • ∙ ∙ Autopkgtest for fenics-dolfinx/1:0.10.0.post5-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Pass
    • ∙ ∙ Autopkgtest for fenics-ffcx/1:0.10.1.post0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for ffc/2019.2.0~legacy20230509.35df986-8: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for flit/3.12.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for forensic-artifacts/20230928-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for glean-parser/15.0.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for guake/3.10.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for helpdev/0.7.1-6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for ideep/0.0~git20251020.9275706-1.1: amd64: Pass, arm64: Pass, i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for jupyter-core/5.9.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for laniakea/0.1.1-5: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for libreoffice/4:26.2.3.2-2: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Pass, riscv64: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Pass
    • ∙ ∙ Autopkgtest for llm/0.30-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for magicgui/0.10.1-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for mintpy/1.6.3-1: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for napari-plugin-manager/0.1.10-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for numba/0.63.1+dfsg-3: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for orange-canvas-core/0.2.8-2: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for pdf2docx/0.5.10-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for pip-check-reqs/2.5.6-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for pusimp/0.1.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for pypy3/7.3.22+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for pytest-doctestplus/1.7.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for pytest-skip-markers/1.3.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-aiohttp-oauthlib/0.1.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for python-auditwheel/6.6.0+ds1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-briefcase/0.4.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-brotlicffi/1.2.0.1+ds1-6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-cffi/2.0.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-depinfo/2.2.0-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-django-extensions/4.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-jsonschema/4.26.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-ovoenergy/3.0.2-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-pbr/7.0.3-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-pip/26.1.1+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-pipdeptree/2.30.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-shippinglabel/2.3.0+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-sievelib/1.5.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-taskipy/1.14.1-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-virtualenv/21.3.1+ds-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-xarray/2026.01.0-2: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python3.13/3.13.12-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • ∙ ∙ Autopkgtest for python3.14/3.14.5-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • ∙ ∙ Autopkgtest for rdflib/7.4.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for rope/1.14.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for ros-rosdep/0.26.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for rows/0.5.0~dev0~1~1d5a326-1.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for scikit-build/0.18.1-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for topplot/0.2.2+repack-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for yoyo/9.0.0+dfsg1-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for yq/3.4.3-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Too young, only 1 of 5 days old
    • Additional info (not blocking):
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pip.html
    • ∙ ∙ Reproduced on amd64 - info
    • ∙ ∙ Reproduced on arm64 - info
    • ∙ ∙ Reproduced on armhf - info
    • ∙ ∙ Reproduced on i386 - info
    • Not considered
news
[rss feed]
  • [2026-05-23] Accepted python-pip 26.1.1+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2026-02-08] python-pip 26.0.1+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2026-02-05] Accepted python-pip 26.0.1+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2026-02-04] Accepted python-pip 26.0+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2025-12-07] python-pip 25.3+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2025-10-26] Accepted python-pip 20.3.4-4+deb11u2 (source) into oldoldstable-security (Daniel Leidert)
  • [2025-10-25] Accepted python-pip 25.3+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2025-08-15] python-pip 25.2+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2025-08-10] Accepted python-pip 25.2+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2025-05-11] python-pip 25.1.1+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2025-05-02] Accepted python-pip 25.1.1+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2025-04-26] Accepted python-pip 25.1+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2025-03-28] python-pip 25.0.1+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2025-03-25] Accepted python-pip 25.0.1+dfsg-1 (source) into unstable (Colin Watson)
  • [2025-01-30] python-pip 25.0+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2025-01-26] Accepted python-pip 25.0+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2024-11-04] python-pip 24.3.1+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-11-01] Accepted python-pip 24.3.1+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2024-08-11] python-pip 24.2+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-08-08] Accepted python-pip 24.2+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2024-07-02] python-pip 24.1.1+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-06-29] Accepted python-pip 24.1.1+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2024-06-27] python-pip 24.1+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-06-25] Accepted python-pip 24.1+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2024-03-16] python-pip 24.0+dfsg-2 MIGRATED to testing (Debian testing watch)
  • [2024-03-06] Accepted python-pip 24.0+dfsg-2 (source) into unstable (Stefano Rivera)
  • [2024-02-08] python-pip 24.0+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-02-05] Accepted python-pip 24.0+dfsg-1 (source) into unstable (Stefano Rivera)
  • [2023-10-21] python-pip 23.3+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2023-10-19] Accepted python-pip 23.3+dfsg-1 (source) into unstable (Stefano Rivera)
  • 1
  • 2
bugs [bug history graph]
  • all: 7
  • RC: 0
  • I&N: 5
  • M&W: 2
  • F&P: 0
  • patch: 0
links
  • homepage
  • lintian (0, 41)
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 25.1.1+dfsg-1ubuntu2
  • 20 bugs

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