New commits:
commit 3a0b8c1fa4d7bae22ba1bbd14cb74cff3fb75b34
Author: Remko van der Vossen <wich AT sourcemage.org>
Commit: Remko van der Vossen <wich AT sourcemage.org>
gnupg: deprecate through a forced dependency
Deprecate through a forced dependency such that gnupg is not removed
before gnupg-2.2 is being cast. If we don't do this gnupg will be
removed due to the self-conflict and only afterwards are any
dependencies of gnupg-2.2 (or potentially any other spells) attempted to
be cast, but they all fail as there is no gpg to do the source
verification (used for both source hashes and pgp signature
verification)
diff --git a/crypto/gnupg/DEPENDS b/crypto/gnupg/DEPENDS
new file mode 100755
index 0000000..56702fd
--- /dev/null
+++ b/crypto/gnupg/DEPENDS
@@ -0,0 +1,2 @@
+depends gnupg-2.2
+force_depends gnupg-2.2
diff --git a/crypto/gnupg/HISTORY b/crypto/gnupg/HISTORY
index f0a5b14..2397764 100644
--- a/crypto/gnupg/HISTORY
+++ b/crypto/gnupg/HISTORY
@@ -1,3 +1,12 @@
+2019-05-06 Remko van der Vossen <wich AT sourcemage.org>
+ * DEPENDS, UP_TRIGGERS: deprecate through a forced dependency such
that
+ gnupg is not removed before gnupg-2.2 is being cast. If we don't do
+ this gnupg will be removed due to the self-conflict and only
+ afterwards are any dependencies of gnupg-2.2 (or potentially any
+ other spells) attempted to be cast, but they all fail as there is no
+ gpg to do the source verification (used for both source hashes and
+ pgp signature verification)
+
2019-01-25 Eric Sandall <sandalle AT sourcemage.org>
* UP_TRIGGER: Need to trigger on an actual spell (gnupg-2.2) not
provider (GNUPG)