From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/4] boost: fix upstream version check
Date: Mon, 24 Apr 2017 16:15:48 +0300 [thread overview]
Message-ID: <20170424131551.2212-1-alexander.kanavin@linux.intel.com> (raw)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
meta/recipes-support/boost/boost-1.64.0.inc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-support/boost/boost-1.64.0.inc b/meta/recipes-support/boost/boost-1.64.0.inc
index 2fa63dca6c7..dc7b1a9c015 100644
--- a/meta/recipes-support/boost/boost-1.64.0.inc
+++ b/meta/recipes-support/boost/boost-1.64.0.inc
@@ -15,6 +15,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/project/boost/boost/${PV}/${BOOST_P}.tar.bz2"
SRC_URI[md5sum] = "93eecce2abed9d2442c9676914709349"
SRC_URI[sha256sum] = "7bcc5caace97baa948931d712ea5f37038dbb1c5d89b43ad4def4ed7cb683332"
-UPSTREAM_CHECK_URI = "https://sourceforge.net/projects/boost/files/"
+UPSTREAM_CHECK_URI = "http://www.boost.org/users/download/"
+UPSTREAM_CHECK_REGEX = "boostorg/release/(?P<pver>.*)/source/"
S = "${WORKDIR}/${BOOST_P}"
--
2.11.0
next reply other threads:[~2017-04-24 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 13:15 Alexander Kanavin [this message]
2017-04-24 13:15 ` [PATCH 2/4] libproxy: speed up upstream version check Alexander Kanavin
2017-04-24 13:15 ` [PATCH 3/4] portmap: remove recipe Alexander Kanavin
2017-04-24 13:15 ` [PATCH 4/4] linux-libc-headers: fix upstream version check Alexander Kanavin
2017-04-24 13:31 ` ✗ patchtest: failure for "boost: fix upstream version ch..." and 3 more Patchwork
2017-04-24 13:32 ` Alexander Kanavin
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=20170424131551.2212-1-alexander.kanavin@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.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