Debian Patches
Status for gpgme1.0/1.24.2-3
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 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 | ||
| 0020-python3-setuptools.diff | Fix setup.py invocation. Debian's python3-setuptools requires additional options (compared to distutils which was shipped wwith python < 3.12). |
Andreas Metzler <ametzler@debian.org> | not-needed | debian | vendor | 2023-10-28 |
| 0025_debian_default_is_openpgp.diff | Adapt testsuite to changed gnupg defaults in Debian | Andreas Metzler <ametzler@debian.org> | not-needed | debian | vendor | 2025-04-20 |
| 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 | ||
| 30-0001-cpp-Ensure-that-all-transitions-go-from-one-state-to.patch | [PATCH 1/4] cpp: Ensure that all transitions go from one state to a different state * src/gpgsignkeyeditinteractor.cpp (makeTable): Replace transitions from CONFIRM to CONFIRM with transitions from CONFIRM to CONFIRM2 and vice versa. Add transitions from CONFIRM2 to some other state for all transitions from CONFIRM to some other state. -- The state machine gets stuck if a transition doesn't change the state but an action is required. To avoid this situation the CONFIRM2 state was introduced, but it was not used correctly. Taken from gpgmepp commit aee2b30482406e677dbddf1a68b2a11a5dc70adf |
=?UTF-8?q?Ingo=20Kl=C3=B6cker?= <dev@ingo-kloecker.de> | no | 2025-04-11 | ||
| 30-0002-cpp-Validate-the-transition-map.patch | [PATCH 2/4] cpp: Validate the transition map * lang/cpp/src/gpgsignkeyeditinteractor.cpp (makeTable): Assert that all transitions go from one state to a different state. -- The state machine gets stuck if a transition doesn't change the state. Make sure that this cannot happen again by mistake. Taken from gpgmepp commit 6f2e91d4d25afa6934ceaf1563a4d826a904d644 |
=?UTF-8?q?Ingo=20Kl=C3=B6cker?= <dev@ingo-kloecker.de> | no | 2025-04-11 | ||
| 30-0003-cpp-Add-missing-transition-remove-two-ignored-and-wr.patch | [PATCH 3/4] cpp: Add missing transition, remove two ignored (and wrong) transitions * lang/cpp/src/gpgsignkeyeditinteractor.cpp (makeTable): Remove two transitions. Add one transition. * lang/cpp/src/gpgsignkeyeditinteractor.cpp (makeTable) <sign_uid.dupe_okay>: Add one more transition. -- This adds a missing transition for the CONFIRM2 state which ensures that the certification is properly completed in case two confirmations were requested. And it removes two useless (and wrong) transitions which are overwritten by two later correct transitions in the map. This is gpgmepp commit 5b77f4072d03342b8719bbe93fc77641fffb476a The second patch fixed a bug seen before we could test Ingo's patch. - wk |
=?UTF-8?q?Ingo=20Kl=C3=B6cker?= <dev@ingo-kloecker.de> | no | 2025-04-15 | ||
| 31-cpp-Ensure-correct-expiration-time-on-32-bit-arch-wi.patch | [PATCH 4/4] cpp: Ensure correct expiration time on 32-bit arch with 64-bit time_t * lang/cpp/src/key.cpp (Subkey::expirationTime): Cast away the signedness of _gpgme_subkey.expires before casting to time_t. -- _gpgme_subkey.expires stores the expiration as `long int` although the expiration is always an unsigned value. Casting the value to unsigned long int before casting it to time_t ensures that we get the correct expiration value for 64-bit time_t even on 32-bit systems. With signed 32-bit time_t we still get a negative value as before. |
=?UTF-8?q?Ingo=20Kl=C3=B6cker?= <dev@ingo-kloecker.de> | no | 2025-05-05 |
All known versions for source package 'gpgme1.0'
- 2.0.0-1 (experimental)
- 1.24.2-3 (trixie, forky, sid)
- 1.18.0-3 (bookworm-backports, bookworm, bookworm-proposed-updates)