Debian Patches

Status for pyjwt/2.15.0-1

Patch	Description	Author	Forwarded	Last update
docs-Use-packaged-intersphinx-resources.patch	docs: Use packaged intersphinx resources	Carsten Schoenert <c.schoenert@t-online.de>	not-needed	2026-02-21
docs-index.rst-Use-a-local-graphic-instead-of-sidelinking.patch	docs: index.rst Use a local graphic instead of sidelinking	Carsten Schoenert <c.schoenert@t-online.de>	not-needed	2025-01-03
Normalize-base64-alphabet-in-base64url_decode-to-avoid-Py.patch	Normalize base64 alphabet in base64url_decode to avoid Py3.15 FutureWarning base64url_decode passed input straight to base64.urlsafe_b64decode after padding. When the input carried standard-alphabet characters (+ or /), Python 3.15 emits FutureWarning about invalid characters in URL-safe Base64 data, and CPython has announced it will eventually discard those characters (silently corrupting the decoded bytes). Translate + and / to - and _ before decoding so valid URL-safe input never warns and historical standard-alphabet input keeps decoding to the same bytes deterministically. The test_compressed_jwt fixture also carried a standard-Base64 payload segment (a literal /) rather than the URL-safe form an RFC 7515 JWT requires; rebuild it (and its HMAC signature) on the URL-safe alphabet. Fixes #1167	arpitjain099 <arpitjain099@gmail.com>	yes	2026-06-04