From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 07/12] sqlite3: upgrade to version 3.22.0
Date: Tue, 23 Jan 2018 16:05:47 +0200 [thread overview]
Message-ID: <1516716352-32735-8-git-send-email-maxin.john@intel.com> (raw)
In-Reply-To: <1516716352-32735-1-git-send-email-maxin.john@intel.com>
Update SRC_URI for releases in 2018.
Signed-off-by: Maxin B. John <maxin.john@intel.com>
---
meta/recipes-support/sqlite/sqlite3_3.21.0.bb | 10 ----------
meta/recipes-support/sqlite/sqlite3_3.22.0.bb | 10 ++++++++++
2 files changed, 10 insertions(+), 10 deletions(-)
delete mode 100644 meta/recipes-support/sqlite/sqlite3_3.21.0.bb
create mode 100644 meta/recipes-support/sqlite/sqlite3_3.22.0.bb
diff --git a/meta/recipes-support/sqlite/sqlite3_3.21.0.bb b/meta/recipes-support/sqlite/sqlite3_3.21.0.bb
deleted file mode 100644
index 1d51733..0000000
--- a/meta/recipes-support/sqlite/sqlite3_3.21.0.bb
+++ /dev/null
@@ -1,10 +0,0 @@
-require sqlite3.inc
-
-LICENSE = "PD"
-LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed00c66"
-
-SRC_URI = "\
- http://www.sqlite.org/2017/sqlite-autoconf-${SQLITE_PV}.tar.gz \
- "
-SRC_URI[md5sum] = "7913de4c3126ba3c24689cb7a199ea31"
-SRC_URI[sha256sum] = "d7dd516775005ad87a57f428b6f86afd206cb341722927f104d3f0cf65fbbbe3"
diff --git a/meta/recipes-support/sqlite/sqlite3_3.22.0.bb b/meta/recipes-support/sqlite/sqlite3_3.22.0.bb
new file mode 100644
index 0000000..ef88659
--- /dev/null
+++ b/meta/recipes-support/sqlite/sqlite3_3.22.0.bb
@@ -0,0 +1,10 @@
+require sqlite3.inc
+
+LICENSE = "PD"
+LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed00c66"
+
+SRC_URI = "\
+ http://www.sqlite.org/2018/sqlite-autoconf-${SQLITE_PV}.tar.gz \
+ "
+SRC_URI[md5sum] = "96b5648d542e8afa6ab7ffb8db8ddc3d"
+SRC_URI[sha256sum] = "2824ab1238b706bc66127320afbdffb096361130e23291f26928a027b885c612"
--
2.4.0
next prev parent reply other threads:[~2018-01-23 14:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 14:05 [PATCH 00/12] package upgrades Maxin B. John
2018-01-23 14:05 ` [PATCH 01/12] freetype: upgrade to version 2.9 Maxin B. John
2018-01-23 14:02 ` Alexander Kanavin
2018-01-23 14:05 ` [PATCH 02/12] libsoup-2.4: upgrade to version 2.61.2 Maxin B. John
2018-01-23 14:44 ` Burton, Ross
2018-01-24 9:25 ` Maxin B. John
2018-01-23 14:05 ` [PATCH 03/12] ofono: upgrade to version 1.22 Maxin B. John
2018-01-23 14:05 ` [PATCH 04/12] pango: upgrade to version 1.41.0 Maxin B. John
2018-01-23 14:45 ` Burton, Ross
2018-01-23 14:42 ` Alexander Kanavin
2018-01-23 14:54 ` Burton, Ross
2018-01-23 14:05 ` [PATCH 05/12] libtasn1: upgrade to version 4.13 Maxin B. John
2018-01-23 14:05 ` [PATCH 06/12] puzzles: upgrade to latest commit Maxin B. John
2018-01-23 14:05 ` Maxin B. John [this message]
2018-01-23 14:05 ` [PATCH 08/12] vte: upgrade to version 0.50.2 Maxin B. John
2018-01-23 14:05 ` [PATCH 09/12] gtk+: upgrade to version 2.24.32 Maxin B. John
2018-01-23 14:05 ` [PATCH 10/12] gtk+3: upgrade to version 3.22.26 Maxin B. John
2018-01-23 14:05 ` [PATCH 11/12] gtk-icon-utils-native: " Maxin B. John
2018-01-23 14:05 ` [PATCH 12/12] atk: upgrade to version 2.26.1 Maxin B. John
2018-01-23 14:06 ` [PATCH 00/12] package upgrades Alexander Kanavin
2018-01-24 9:01 ` Maxin B. John
2018-01-25 7:09 ` 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=1516716352-32735-8-git-send-email-maxin.john@intel.com \
--to=maxin.john@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