From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/4] libproxy: speed up upstream version check
Date: Mon, 24 Apr 2017 16:15:49 +0300 [thread overview]
Message-ID: <20170424131551.2212-2-alexander.kanavin@linux.intel.com> (raw)
In-Reply-To: <20170424131551.2212-1-alexander.kanavin@linux.intel.com>
Something in the fetched webpage made the default regex matching really slow.
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
meta/recipes-support/libproxy/libproxy_0.4.14.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-support/libproxy/libproxy_0.4.14.bb b/meta/recipes-support/libproxy/libproxy_0.4.14.bb
index 8f56aafd62f..fcdb82f06cc 100644
--- a/meta/recipes-support/libproxy/libproxy_0.4.14.bb
+++ b/meta/recipes-support/libproxy/libproxy_0.4.14.bb
@@ -11,6 +11,7 @@ DEPENDS = "glib-2.0"
SRC_URI = "https://github.com/${BPN}/${BPN}/archive/${PV}.tar.gz"
UPSTREAM_CHECK_URI = "https://github.com/libproxy/libproxy/releases"
+UPSTREAM_CHECK_REGEX = "libproxy-(?P<pver>.*)\.tar"
SRC_URI[md5sum] = "272dc378efcc3335154cef30d171e84a"
SRC_URI[sha256sum] = "6220a6cab837a8996116a0568324cadfd09a07ec16b930d2a330e16d5c2e1eb6"
--
2.11.0
next prev parent 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 [PATCH 1/4] boost: fix upstream version check Alexander Kanavin
2017-04-24 13:15 ` Alexander Kanavin [this message]
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-2-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