From: Alexander Kanavin <[email protected]>

Upstream isn't clearly communicating their release strategy and plan:
https://www.gnupg.org/download/

In the beginning gnupg 2.5.x were development releases while 2.4.x was
the current maintenance branch. Over time, upstream started to indicate
that 2.5.x should be seen as proper releases, while 2.4.x reached EOL a few
weeks ago. There has not been any communcation about if and when 2.6 appears,
and if it does, will the odd-even version scheme still be followed.

Meanwhile, we do need to pick up the latest 2.5 releases with AUH, so let's drop
the odd-even pretense for now.

Signed-off-by: Alexander Kanavin <[email protected]>
---
 meta/recipes-support/gnupg/gnupg_2.5.20.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-support/gnupg/gnupg_2.5.20.bb 
b/meta/recipes-support/gnupg/gnupg_2.5.20.bb
index 4146b12824..a7f0d40c1f 100644
--- a/meta/recipes-support/gnupg/gnupg_2.5.20.bb
+++ b/meta/recipes-support/gnupg/gnupg_2.5.20.bb
@@ -11,10 +11,11 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=189af8afca6d6075ba6c9e0aa8077626 \
 
 DEPENDS = "npth libassuan libksba zlib bzip2 readline libgcrypt"
 
-inherit autotools gettext texinfo pkgconfig upstream-version-is-even
+inherit autotools gettext texinfo pkgconfig
 
 require drop-unknown-suffix.inc
 
+# Note: when 2.6 is out, check whether upstream-version-is-even class should 
be re-enabled
 UPSTREAM_CHECK_URI = "https://gnupg.org/ftp/gcrypt/gnupg/";
 SRC_URI = "${GNUPG_MIRROR}/${BPN}/${BPN}-${PV}.tar.bz2 \
            file://0002-use-pkgconfig-instead-of-npth-config.patch \
-- 
2.47.3

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#241084): 
https://lists.openembedded.org/g/openembedded-core/message/241084
Mute This Topic: https://lists.openembedded.org/mt/120296908/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to