From: "zangrc" <zangrc.fnst@cn.fujitsu.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [oe] [meta-webserver] [PATCH] nostromo: upgrade 1.9.7 -> 1.9.9
Date: Fri, 24 Jul 2020 17:51:01 +0800 [thread overview]
Message-ID: <1595584262-85677-3-git-send-email-zangrc.fnst@cn.fujitsu.com> (raw)
In-Reply-To: <1595584262-85677-1-git-send-email-zangrc.fnst@cn.fujitsu.com>
Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
---
.../nostromo/{nostromo_1.9.7.bb => nostromo_1.9.9.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-webserver/recipes-httpd/nostromo/{nostromo_1.9.7.bb => nostromo_1.9.9.bb} (94%)
diff --git a/meta-webserver/recipes-httpd/nostromo/nostromo_1.9.7.bb b/meta-webserver/recipes-httpd/nostromo/nostromo_1.9.9.bb
similarity index 94%
rename from meta-webserver/recipes-httpd/nostromo/nostromo_1.9.7.bb
rename to meta-webserver/recipes-httpd/nostromo/nostromo_1.9.9.bb
index d13ef74feb..e726c9ac66 100644
--- a/meta-webserver/recipes-httpd/nostromo/nostromo_1.9.7.bb
+++ b/meta-webserver/recipes-httpd/nostromo/nostromo_1.9.9.bb
@@ -11,8 +11,8 @@ SRC_URI = "http://www.nazgul.ch/dev/${BPN}-${PV}.tar.gz \
file://nostromo \
"
-SRC_URI[md5sum] = "6189714845b3ad5d0fc490f8cf48dacf"
-SRC_URI[sha256sum] = "33c635f317fb441e10d5297bb4218ae0ea62c48f2fc3029c08f5d2167c6cdfca"
+SRC_URI[md5sum] = "a054eb8e09560082793aaad676e33bd3"
+SRC_URI[sha256sum] = "1fad0a28d934835b582cedc98857e12e5adb991b14b87b52b39e6a501f4a9486"
TARGET_CC_ARCH += "${LDFLAGS}"
--
2.25.1
next prev parent reply other threads:[~2020-07-24 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 9:50 [oe] [meta-webserver] [PATCH] apache-websocket: upgrade 0.1.1 -> 0.1.2 zangrc
2020-07-24 9:51 ` [oe] [meta-webserver] [PATCH] hiawatha: upgrade 10.10 -> 10.11 zangrc
2020-07-24 9:51 ` zangrc [this message]
2020-07-24 9:51 ` [oe] [meta-oe] [PATCH] purple-skypeweb: upgrade 1.5 -> 1.6 zangrc
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=1595584262-85677-3-git-send-email-zangrc.fnst@cn.fujitsu.com \
--to=zangrc.fnst@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.