Debian Patches

Status for cryptoparser/1.6.0-3

Patch Description Author Forwarded Bugs Origin Last update
skip-tests.patch skip test, when path does not exist Martin <debacle@debian.org> no vendor 2026-05-14
fix-timestamps-on-32-bit-platforms.patch fix(common): Parse and compose timestamps on 32-bit platforms (#110) Szilárd Pfeiffer <coroner@pfeifferszilard.hu> yes upstream backport, https://gitlab.com/coroner/cryptoparser/-/commit/1ea2e3ab35c4adcb5a4dfdcf6bc8cd7bda2002aa
fix-metadata-author-parsing.patch Parse author from Author-email metadata In Python 3.15, accessing missing metadata keys via __getitem__ raises KeyError
instead of returning None. Since pyproject.toml defines authors with both name
and email, the metadata contains Author-email instead of Author.
Parse the author and author email using email.utils.parseaddr, consistent with
upstream's cryptolyzer and cryptodatahub.		 Maximiliano Curia <maxy@debian.org> no 2026-10-13
fix-top-level-txt.patch Restrict package discovery to cryptoparser Without explicitly specifying include patterns, setuptools package auto-discovery
finds namespace packages in build/, debian/, docs/, and test/.
When pybuild builds sequentially for multiple Python versions, the build/ directory
created during the first Python build gets discovered as packages (e.g. build.lib)
during the second Python build. The pattern exclude = ['build'] does not match
subpackages like build.lib (as setuptools matches dot-separated package paths),
causing "build" to be added to top_level.txt in the second wheel and leading to a
merge conflict in dh_python3.
Restrict package discovery to include only 'cryptoparser*' to ensure only the
intended package is included and top_level.txt is consistent across builds.		 Maximiliano Curia <maxy@debian.org> no 2026-10-20

All known versions for source package 'cryptoparser'

Links