Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
0030-fix-verifying-encapsulated-messages.patch | Fix verifying encapsulated messages This monkeypatches mail-gpg to restore the use of the unaltered raw source of the relevant email part. This code was removed in <https://github.com/jkraemer/mail-gpg/commit/5fded41ccee4a58f848a2f8e7bd53d11236f8984> for yet unknown reasons. The issue is tracked at <https://github.com/jkraemer/mail-gpg/issues/67>. |
yes | upstream | upstream | 2021-07-29 | |
0029-gemspec-mail-gpg-relax-version.patch | gemspec: relax version of mail-gpg Allow to use the latest version of the gem mail-gpg. Our specs had been failing with versions > 0.4.2, but we found out it was our specs' fault. |
no | upstream | 2021-05-23 | ||
0028-specs-fix-to-less-depend-on-preconditions.patch | Fix specs to less depend on preconditions Some expectations only worked as long as the content-transfer-encoding was not Base64. Some only worked if it was Quoted-Printable. Now they don't depend on the CTE anymore. |
no | upstream | 2021-05-23 | ||
0027-rescue-gpgme-error-canceled.patch | Also consider GPGME::Error::Canceled as DecryptionFailed | no | upstream | 2021-05-23 | ||
0025-gemspec-relax-thor-version.patch | gemspec: relax thor version | Georg Faerber <georg@debian.org> | not-needed | 2021-02-02 | ||
0024-gemspec-update-bigdecimal.patch | gemspec: update bigdecimal | not-needed | 2020-04-02 | |||
0023-gemspec-sqlite-relax-version-check.patch | gemspec: relax SQLite dependency | Georg Faerber <georg@debian.org> | yes | 2021-02-02 | ||
0016-gemspec-update-sinatra.patch | gemspec: allow sinatra* 2~ Unstable and testing ship sinatra and sinatra-contrib 2.0.5. Accordingly, update the gemspec. |
Georg Faerber <georg@riseup.net> | no | 2021-02-02 | ||
0011-fix-for-activerecord-6.patch | Fix for ruby-activerecord 6 This patch specifies the ActiveRecord version in each migration, and skips the migration specs which are obsolete by now. |
not-needed | upstream | 2021-05-23 | ||
0008-dirmngr-no-tor-standard-resolver.patch | dirmngr: Don't use tor, use standard resolver (specs only) It seems dirmngr still has problems connecting to a keyserver if invoked in a chroot. This leads to failing specs. This patch introduces a dirmngr config for the affected specs. The config disables the use of Tor and enforces the use of the so called "standard resolver" for DNS resolution. Using both options makes dirmngr, and therefore the specs, work reliably. This will be integrated upstream. Additionally, this will be reported to upstream of GnuPG. |
Georg Faerber <georg@riseup.net> | no | 2021-02-07 | ||
0007-specs-remove-install-test.patch | specs: Remove install test Remove the spec which tests and expects the install to fail, if a shell-process fails, as it fails itself, currently. Upstream is aware of this patch and we're working on integrating it upstream. |
Georg Faerber <georg@riseup.net> | no | 2020-12-27 | ||
0004-use-default-debian-keyserver.patch | schleuder config: Use default Debian keyserver Debian stretch (and all future versions) ship(s) with sensible keyserver defaults, therefore, use these. |
Georg Faerber <georg@riseup.net> | no | 2018-09-21 | ||
0005-man-fix-log-path.patch | man/: Fix logging path We're logging into '/var/log/schleuder', so reflect this in the manpage. Upstream is aware of this patch and we're working on integrating it upstream. |
Georg Faerber <georg@riseup.net> | no | 2017-01-26 | ||
0001-lib-fix-paths.patch | lib/: Fix paths Use '/var/log/schleuder' for logging. Set the 'root_dir' to '/usr/lib/ruby/vendor_ruby/schleuder/'. Additionally, add '/usr/share/schleuder/locales/*.yml' to the locales load path. Use 'require' instead of 'require_relative'. Upstream is aware of this patch and we're working on integrating it upstream. |
Georg Faerber <georg@riseup.net> | no | 2021-05-23 | ||
0002-etc-fix-paths.patch | Fix paths used by upstream Logs should go into '/var/log/schleuder'. | Georg Faerber <georg@riseup.net> | no | 2021-02-07 | ||
0026-Change-way-to-block-passphrase-interaction.patch | Change way to block passphrase interaction This changes the way we block gpg from asking interactively for a passphrase, ever. It's also a less hacky way to force this. This works with gpg-2.0.26+gpgme-1.5.1, gpg-2.1.18+gpgme-1.8.0, gpg-2.2.27+gpgme-1.14.0, and gpg-2.2.27+gpgme-1.15.1, which makes me optimistic that it's universally working. The previous solution brought problems for some platforms and specific combinations of gnupg with gpgme (resulting in "GPGME::Error no such file or directory"). (cherry picked from commit 0b7c3a9ffd0178c7610752899e569758704ffd32) |
paz <paz@nadir.org> | yes | 2021-02-12 | ||
0031-db-change-boolean-values-to-integers.patch | DB: change boolean values to integers Since ActiveRecord >= 6.0, the SQLite3 connection adapter relies on boolean serialization to use 1 and 0, but does not natively recognize 't' and 'f' as booleans were previously serialized. Accordingly, this patch handles conversion via a database migration of both column defaults and stored data provided by a user. |
Georg Faerber <georg@riseup.net> | yes | upstream | upstream | 2021-12-25 |