| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Remove-upstream-git-fanciness.patch | Remove upstream git fanciness Debian needs to be able to build libgpg-error while using git for tracking the debian packaging itself. Debian also wants to autoreconf this stuff. However, Debian does *not* need to conform exactly to upstream's git configurations. This avoids mistakes like accidentally identifying running code as a beta. This is the same approach taken in debian's libgpg-error packaging since 2017. |
Daniel Kahn Gillmor <dkg@fifthhorseman.net> | not-needed | 2015-06-11 | ||
| 0002-drop-python2-support.patch | drop python2 support | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | yes | 2019-08-23 | ||
| 0003-Ship-python-examples-with-python3-in-shebang-line.patch | Ship python examples with python3 in shebang line See discussion at #982630 and https://www.python.org/dev/peps/pep-0394/#recommendation : > When packaging third party Python scripts, distributors are > encouraged to change less specific shebangs to more specific > ones. This ensures software is used with the latest version of > Python available, and it can remove a dependency on Python > 2. The details on what specifics to set are left to the > distributors; though. Example specifics could include: > > - Changing python shebangs to python3 when Python 3.x is > supported. |
Daniel Kahn Gillmor <dkg@fifthhorseman.net> | not-needed | 2021-02-16 | ||
| 0004-Avoid-the-hardcoded-list-of-Python-versions.patch | Avoid the hardcoded list of Python versions Instead stick to Debian's list of supported Pythons. |
Stefano Rivera <stefanor@debian.org> | not-needed | debian | 2021-11-23 | |
| 0007-lang-python-tests-Fix-FTBFS-caused-by-missing-PYTHON.patch | [PATCH] lang: python: tests: Fix FTBFS caused by missing PYTHON Updated by Paul Gevers <elbrus@debian.org> |
Alexandre Ghiti <alexandre.ghiti@canonical.com> | no | 2022-03-31 | ||
| 0010-build-python-Don-t-use-gpg-error-config-gpgme-config.patch | build:python: Don't use gpg-error-config/gpgme-config. * lang/python/setup.py.in: Use @prefix@, @GPGME_CONFIG_LIBS@, @GPGME_CONFIG_CFLAGS@, and @GPG_ERROR_CFLAGS@ of configure. -- (cherry picked from commit ae9258fbf3b9d434495ef11fc184a91fe7c4ca57) |
NIIBE Yutaka <gniibe@fsij.org> | no | 2022-09-15 | ||
| 0013-python-Fix-configure-generating-setup.py.patch | python: Fix configure generating setup.py. * lang/python/setup.py.in: Handle the case, when substitutions may be empty. -- (cherry-picked from commit f1802682c3c8794edaca37966405bd1f070f5e01) |
NIIBE Yutaka <gniibe@fsij.org> | no | 2022-10-26 | ||
| 0015-build-Prefer-gpgrt-config-when-available.patch | build: Prefer gpgrt-config when available. * src/gpgme.m4: Overriding the decision by --with-gpgme-prefix, use gpgrt-config gpgme when gpgrt-config is available. -- This may offer better migration. (cherry picked from commit 9f55dceca0cf2926d14cb4a70bd0cdc454d89f03) |
NIIBE Yutaka <gniibe@fsij.org> | no | 2022-11-02 | ||
| 0016-gpgme.m4-Include-_AM_PATH_GPGRT_CONFIG-implementatio.patch | gpgme.m4: Include _AM_PATH_GPGRT_CONFIG implementation. * src/gpgme.m4 (_AM_PATH_GPGRT_CONFIG): New. (_AM_PATH_GPGME_CONFIG): Require _AM_PATH_GPGRT_CONFIG. -- (cherry-picked from abd51848bdc8a5ea5929f9cfb819a408dc53d463) |
NIIBE Yutaka <gniibe@fsij.org> | no | 2022-11-15 | ||
| 0017-doc-Update-documentation-for-gpgme.pc-and-pkg-config.patch | doc: Update documentation for gpgme.pc and pkg-config. -- (cherry-picked from ae2057e6017427941aef00ccf1b7a9f6b0e3189c) |
NIIBE Yutaka <gniibe@fsij.org> | no | 2022-11-15 |