From: <kai.kang@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [PATCH 1/3] openl2tp: update SRC_URI
Date: Thu, 22 Dec 2016 17:28:07 +0800 [thread overview]
Message-ID: <20161222092809.13510-2-kai.kang@windriver.com> (raw)
In-Reply-To: <20161222092809.13510-1-kai.kang@windriver.com>
From: Kai Kang <kai.kang@windriver.com>
The original SRC_URI is not valid, so update it with openl2tp official
ftp site.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
meta-networking/recipes-protocols/openl2tp/openl2tp_1.8.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-networking/recipes-protocols/openl2tp/openl2tp_1.8.bb b/meta-networking/recipes-protocols/openl2tp/openl2tp_1.8.bb
index 5a63404..67118d8 100644
--- a/meta-networking/recipes-protocols/openl2tp/openl2tp_1.8.bb
+++ b/meta-networking/recipes-protocols/openl2tp/openl2tp_1.8.bb
@@ -11,7 +11,7 @@ LICENSE = "GPL-2.0"
LIC_FILES_CHKSUM = "file://COPYING;md5=e9d9259cbbf00945adc25a470c1d3585"
DEPENDS = "popt flex readline"
-SRC_URI = "http://ftp.jaist.ac.jp/pub/sourceforge/o/op/${PN}/${PN}/${PV}/${BP}.tar.gz \
+SRC_URI = "ftp://ftp.openl2tp.org/releases/${BP}/${BP}.tar.gz \
file://Makefile-modify-CFLAGS-to-aviod-build-error.patch \
file://openl2tp-simplify-gcc-warning-hack.patch \
file://Makefile-obey-LDFLAGS.patch \
--
2.10.1
next prev parent reply other threads:[~2016-12-22 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 9:28 [meta-networking][PATCH 0/3] Update SRC_URIs of 3 packages kai.kang
2016-12-22 9:28 ` kai.kang [this message]
2016-12-22 9:28 ` [PATCH 2/3] ctdb: update SRC_URI kai.kang
2016-12-22 9:28 ` [PATCH 3/3] pimd: " kai.kang
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=20161222092809.13510-2-kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-devel@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