From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@openembedded.org
Cc: Ferry Toth <ftoth@exalondelft.nl>
Subject: [warrir][PATCH 3/4] sudo: Fix fetching sources
Date: Sat, 11 Jan 2020 22:14:56 -0800 [thread overview]
Message-ID: <20200112061457.10741-3-akuster808@gmail.com> (raw)
In-Reply-To: <20200112061457.10741-1-akuster808@gmail.com>
From: Ferry Toth <ftoth@exalondelft.nl>
It looks like https://www.sudo.ws/download.html changed certificate
and directory structure. This breaks fetching sources.
Signed-off-by: Ferry Toth <ftoth@exalondelft.nl>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
(cherry picked from commit f02e9f46ce54fed3c7ddfad7d1003a2fb7ba3a67)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
meta/recipes-extended/sudo/sudo_1.8.27.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-extended/sudo/sudo_1.8.27.bb b/meta/recipes-extended/sudo/sudo_1.8.27.bb
index bbca8395b9..43c27bf37f 100644
--- a/meta/recipes-extended/sudo/sudo_1.8.27.bb
+++ b/meta/recipes-extended/sudo/sudo_1.8.27.bb
@@ -1,6 +1,6 @@
require sudo.inc
-SRC_URI = "http://www.sudo.ws/sudo/dist/sudo-${PV}.tar.gz \
+SRC_URI = "https://www.sudo.ws/dist/sudo-${PV}.tar.gz \
${@bb.utils.contains('DISTRO_FEATURES', 'pam', '${PAM_SRC_URI}', '', d)} \
file://0001-Include-sys-types.h-for-id_t-definition.patch \
file://CVE-2019-14287-1.patch \
--
2.17.1
next prev parent reply other threads:[~2020-01-12 6:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 6:14 [warrir][PATCH 1/4] popt: fix SRC_URI Armin Kuster
2020-01-12 6:14 ` [warrir][PATCH 2/4] sudo: correct SRC_URI Armin Kuster
2020-01-12 6:14 ` Armin Kuster [this message]
2020-01-12 6:14 ` [warrir][PATCH 4/4] stress: update SRC_URI Armin Kuster
2020-01-12 7:02 ` ✗ patchtest: failure for "[warrir] popt: fix SRC_URI..." and 3 more Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200112061457.10741-3-akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=ftoth@exalondelft.nl \
--cc=openembedded-core@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox