[kirkstone][PATCH] wayland-protocols: upgrade 1.22 -> 1.23

[kirkstone][PATCH] wayland-protocols: upgrade 1.22 -> 1.23

[Denys Dmytriyenko]

wayland-protocols 1.23 is now available.

This release adds the new gesture "hold" to the pointer gesture protocol.

https://lists.freedesktop.org/archives/wayland-devel/2021-September/041979.html

Signed-off-by: Denys Dmytriyenko <denis@denix.org>
---
Please note - this is meant for kirkstone(-next), as upgrade to 1.22 is not in master yet

 .../wayland/{wayland-protocols_1.22.bb => wayland-protocols_1.23.bb}    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/wayland/{wayland-protocols_1.22.bb => wayland-protocols_1.23.bb} (90%)

diff --git a/meta/recipes-graphics/wayland/wayland-protocols_1.22.bb b/meta/recipes-graphics/wayland/wayland-protocols_1.23.bb
similarity index 90%
rename from meta/recipes-graphics/wayland/wayland-protocols_1.22.bb
rename to meta/recipes-graphics/wayland/wayland-protocols_1.23.bb
index 4e8d390..60b6eb1 100644
--- a/meta/recipes-graphics/wayland/wayland-protocols_1.22.bb
+++ b/meta/recipes-graphics/wayland/wayland-protocols_1.23.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=c7b12b6702da38ca028ace54aae3d484 \
 
 SRC_URI = "https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
            "
-SRC_URI[sha256sum] = "96e7cf03524995a47028236c6d6141c874e693cb80c0be8dabe15455cdd5a5a7"
+SRC_URI[sha256sum] = "6c0af1915f96f615927a6270d025bd973ff1c58e521e4ca1fc9abfc914633f76"
 
 UPSTREAM_CHECK_URI = "https://wayland.freedesktop.org/releases.html"
 
-- 
2.7.4

Re: [OE-core] [kirkstone][PATCH] wayland-protocols: upgrade 1.22 -> 1.23

[Armin Kuster]

So we wait until that branch is created in 5 months before we can apply
it ?  Is this like post dating a check?

-armin

On 9/15/21 6:06 PM, Denys Dmytriyenko wrote:
> wayland-protocols 1.23 is now available.
>
> This release adds the new gesture "hold" to the pointer gesture protocol.
>
> https://lists.freedesktop.org/archives/wayland-devel/2021-September/041979.html
>
> Signed-off-by: Denys Dmytriyenko <denis@denix.org>
> ---
> Please note - this is meant for kirkstone(-next), as upgrade to 1.22 is not in master yet
>
>  .../wayland/{wayland-protocols_1.22.bb => wayland-protocols_1.23.bb}    | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>  rename meta/recipes-graphics/wayland/{wayland-protocols_1.22.bb => wayland-protocols_1.23.bb} (90%)
>
> diff --git a/meta/recipes-graphics/wayland/wayland-protocols_1.22.bb b/meta/recipes-graphics/wayland/wayland-protocols_1.23.bb
> similarity index 90%
> rename from meta/recipes-graphics/wayland/wayland-protocols_1.22.bb
> rename to meta/recipes-graphics/wayland/wayland-protocols_1.23.bb
> index 4e8d390..60b6eb1 100644
> --- a/meta/recipes-graphics/wayland/wayland-protocols_1.22.bb
> +++ b/meta/recipes-graphics/wayland/wayland-protocols_1.23.bb
> @@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=c7b12b6702da38ca028ace54aae3d484 \
>  
>  SRC_URI = "https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
>             "
> -SRC_URI[sha256sum] = "96e7cf03524995a47028236c6d6141c874e693cb80c0be8dabe15455cdd5a5a7"
> +SRC_URI[sha256sum] = "6c0af1915f96f615927a6270d025bd973ff1c58e521e4ca1fc9abfc914633f76"
>  
>  UPSTREAM_CHECK_URI = "https://wayland.freedesktop.org/releases.html"
>  
>
> 
>

Re: [OE-core] [kirkstone][PATCH] wayland-protocols: upgrade 1.22 -> 1.23

[Richard Purdie]

On Wed, 2021-09-15 at 19:31 -0700, Armin Kuster wrote:
> So we wait until that branch is created in 5 months before we can apply
> it ?  Is this like post dating a check?

Alexandre and I are using "kirkstone-next" as a place to queue things for the
next release so this does make sense.

Cheers,

Richard

Re: [OE-core] [kirkstone][PATCH] wayland-protocols: upgrade 1.22 -> 1.23

[Armin Kuster]

On 9/16/21 1:03 AM, Richard Purdie wrote:
> On Wed, 2021-09-15 at 19:31 -0700, Armin Kuster wrote:
>> So we wait until that branch is created in 5 months before we can apply
>> it ?  Is this like post dating a check?
> Alexandre and I are using "kirkstone-next" as a place to queue things for the
> next release so this does make sense.

I know why you and Alexandre are doing it.  Should there be a note added
to the
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Sending_using_git-send-email
Section "Backporting fixes to stable releases"  regarding an exception
during code stabilization to use the next next stable branch name
instead of "Master" ?

-armin

>
> Cheers,
>
> Richard
>

Re: [OE-core] [kirkstone][PATCH] wayland-protocols: upgrade 1.22 -> 1.23

[Richard Purdie]

On Thu, 2021-09-16 at 08:26 -0700, akuster808 wrote:
> 
> On 9/16/21 1:03 AM, Richard Purdie wrote:
> > On Wed, 2021-09-15 at 19:31 -0700, Armin Kuster wrote:
> > > So we wait until that branch is created in 5 months before we can apply
> > > it ?  Is this like post dating a check?
> > Alexandre and I are using "kirkstone-next" as a place to queue things for the
> > next release so this does make sense.
> 
> I know why you and Alexandre are doing it.  Should there be a note added
> to the
> https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Sending_using_git-send-email
> Section "Backporting fixes to stable releases"  regarding an exception
> during code stabilization to use the next next stable branch name
> instead of "Master" ?

We say "don't sent these patches" and people do. I don't really want to document
that it is "ok", I'm just trying to handle the reality of the situation since if
we don't do something with things, we end up in a really big mess after release.

Cheers,

Richard