- 07 May, 2022 2 commits
-
- 18 Apr, 2022 1 commit
-
-
georg authored
This change allows to set the env var before building the Debian package, which otherwise fails, as the related code doesn't work if invoked in a chroot, for unknown reasons.
-
- 17 Apr, 2022 1 commit
-
-
georg authored
As of 2022/04/16, gnupg 2.2.27-3 as shipped in Debian, reports 'unknown host' and 'connection refused', which is different from what we see in our upstream CI. Again, reasons are unclear. Given this, relax the expected error message.
-
- 16 Apr, 2022 8 commits
- 13 Apr, 2022 3 commits
- 12 Apr, 2022 2 commits
-
-
georg authored
-
- 11 Apr, 2022 2 commits
-
- 10 Apr, 2022 1 commit
-
- 09 Apr, 2022 1 commit
-
- 08 Apr, 2022 1 commit
-
- 05 Apr, 2022 1 commit
-
-
georg authored
This helps in downstream environments, like Debian, via relying on environment variables, instead of patches, to not require 'byebug'. Similar code is already in place in regards to the usage of 'bundler' and 'simplecov'. This commit doesn't include a CHANGELOG note, as it's not really relevant to most users, I believe.
-
- 04 Apr, 2022 1 commit
-
- 01 Apr, 2022 4 commits
-
-
abc def authored
-
abc def authored
When bounces_drop_all=true, filters such as receive_encrypted_only were circumvented and allowed non-encrypted senders to pass messages onto the lists (see #508). This moves the bounce-dropping mechanism from `filters_runner.rb` to `runner.rb`. Thus, the decision if a bounce is being dropped will be made entirely in runner.rb. `filters_runner.rb` will only take care of checking for errors.
-
abc def authored
-
abc def authored
-
- 26 Mar, 2022 2 commits
-
- 17 Mar, 2022 2 commits
-
-
paz authored
If using the "standard-resolver" and a not reachable keyserver, dirmngr reports a different error message than with its internal resolver
🤦 -
paz authored
"localhost" is not available in (most?) docker environments. This also makes dirmngr disable its internal resolver, which apparently has problems with HKP-URLs containing local IPs.
-
- 11 Mar, 2022 1 commit
-
- 28 Feb, 2022 4 commits
- 25 Dec, 2021 1 commit
-
-
georg authored
-
- 15 Dec, 2021 1 commit
-
- 29 Nov, 2021 1 commit
-
-
georg authored
It seems, the change to ActiveRecord >= 6.0 makes this necessary. Without doing this, the auto-generated database schema file would drop these limits, if running migrations. It seems, this problems has been ongoing since quite some time. For details, see [1]. [1] https://github.com/rails/rails/issues/19001
-