From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: buildroot@buildroot.org
Cc: Marcus Folkesson <marcus.folkesson@gmail.com>
Subject: [Buildroot] [PATCH] package/libostree: bump to version 2023.5
Date: Mon, 7 Aug 2023 10:15:36 +0200 [thread overview]
Message-ID: <20230807081536.4167754-1-marcus.folkesson@gmail.com> (raw)
Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
---
package/libostree/libostree.hash | 2 +-
package/libostree/libostree.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/libostree/libostree.hash b/package/libostree/libostree.hash
index 088650a86f..3b88b8200f 100644
--- a/package/libostree/libostree.hash
+++ b/package/libostree/libostree.hash
@@ -1,3 +1,3 @@
# Locally calculated
-sha256 9c575a094da2c307769f0aee15de95470c3b5550cbff211fbbc4f6fc75f333b1 libostree-2023.3.tar.xz
+sha256 bc593afb31fe1ac3d50419f917fafe321a0a3561d7bb2ba498a83740fe3adb14 libostree-2023.5.tar.xz
sha256 b7993225104d90ddd8024fd838faf300bea5e83d91203eab98e29512acebd69c COPYING
diff --git a/package/libostree/libostree.mk b/package/libostree/libostree.mk
index 5c39090654..c61c1d1508 100644
--- a/package/libostree/libostree.mk
+++ b/package/libostree/libostree.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LIBOSTREE_VERSION = 2023.3
+LIBOSTREE_VERSION = 2023.5
LIBOSTREE_SOURCE = libostree-$(LIBOSTREE_VERSION).tar.xz
LIBOSTREE_SITE = https://github.com/ostreedev/ostree/releases/download/v$(LIBOSTREE_VERSION)
--
2.40.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-08-07 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 8:15 Marcus Folkesson [this message]
2023-08-07 21:22 ` [Buildroot] [PATCH] package/libostree: bump to version 2023.5 Thomas Petazzoni via buildroot
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=20230807081536.4167754-1-marcus.folkesson@gmail.com \
--to=marcus.folkesson@gmail.com \
--cc=buildroot@buildroot.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.