[Buildroot] [PATCH] libostree: bump to version 2018.2

[Buildroot] [PATCH] libostree: bump to version 2018.2

[Marcus Folkesson]

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 54bc263f06..6ae4824007 100644
--- a/package/libostree/libostree.hash
+++ b/package/libostree/libostree.hash
@@ -1,3 +1,3 @@
 # Locally calculated
-sha256 8b5e3b80425b91c93aeb916bb047ee194aa138a9cf00ce173dcc0ebc0dd11f4b  libostree-2018.1.tar.xz
+sha256 37661de4a0ac73af5d921f494f17dd052ae2844111ba7c5aaeb1cbc4aae94bea  libostree-2018.2.tar.xz
 sha256 b7993225104d90ddd8024fd838faf300bea5e83d91203eab98e29512acebd69c  COPYING
diff --git a/package/libostree/libostree.mk b/package/libostree/libostree.mk
index 336d11a978..236657e9fa 100644
--- a/package/libostree/libostree.mk
+++ b/package/libostree/libostree.mk
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-LIBOSTREE_VERSION = 2018.1
+LIBOSTREE_VERSION = 2018.2
 LIBOSTREE_SOURCE = libostree-$(LIBOSTREE_VERSION).tar.xz
 LIBOSTREE_SITE = https://github.com/ostreedev/ostree/releases/download/v$(LIBOSTREE_VERSION)
 
-- 
2.15.1

[Buildroot] [PATCH] libostree: bump to version 2018.2

[Peter Korsgaard]

>>>>> "Marcus" == Marcus Folkesson <marcus.folkesson@gmail.com> writes:

 > Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>

Does this need to go to master for the 2018.02 release? According to the
release notes it seems to be a mix of bugfixes and new features.

Committed to next so far, thanks.

-- 
Bye, Peter Korsgaard

[Buildroot] [PATCH] libostree: bump to version 2018.2

[Marcus Folkesson]

Hello Peter,

On Thu, Feb 15, 2018 at 10:17:10PM +0100, Peter Korsgaard wrote:
> >>>>> "Marcus" == Marcus Folkesson <marcus.folkesson@gmail.com> writes:
> 
>  > Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
> 
> Does this need to go to master for the 2018.02 release? According to the
> release notes it seems to be a mix of bugfixes and new features.

I'm not sure what qualifies a bump to go to master, but sure, it does
not hurt.

> 
> Committed to next so far, thanks.
> 
> -- 
> Bye, Peter Korsgaard

Thank you

Best regards
Marcus Folkesson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180217/03bcbbe5/attachment.asc>

[Buildroot] [PATCH] libostree: bump to version 2018.2

[Peter Korsgaard]

>>>>> "Marcus" == Marcus Folkesson <marcus.folkesson@gmail.com> writes:

 > Hello Peter,
 > On Thu, Feb 15, 2018 at 10:17:10PM +0100, Peter Korsgaard wrote:
 >> >>>>> "Marcus" == Marcus Folkesson <marcus.folkesson@gmail.com> writes:
 >> 
 >> > Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
 >> 
 >> Does this need to go to master for the 2018.02 release? According to the
 >> release notes it seems to be a mix of bugfixes and new features.

 > I'm not sure what qualifies a bump to go to master, but sure, it does
 > not hurt.

master material during the stabilization phase is stuff fixing
security/important issues, preferably without adding any new features.

-- 
Bye, Peter Korsgaard