From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] wayvnc: version bump 0.8.0 -> 0.9.1
Date: Fri, 7 Mar 2025 10:49:48 +0100 [thread overview]
Message-ID: <20250307094948.4097014-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250227083153.1294167-1-p.zabel@pengutronix.de>
Thanks, applied as df013d2c5e03fa0b42fd8870d10c1161e8fbff8d.
Michael
[sent from post-receive hook]
On Fri, 07 Mar 2025 10:49:48 +0100, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> https://github.com/any1/wayvnc/releases/tag/v0.9.0
> https://github.com/any1/wayvnc/releases/tag/v0.9.1
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Message-Id: <20250227083153.1294167-1-p.zabel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/wayvnc.make b/rules/wayvnc.make
> index 41df73cdb0b9..aeda7ce7a353 100644
> --- a/rules/wayvnc.make
> +++ b/rules/wayvnc.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_WAYVNC) += wayvnc
> #
> # Paths and names
> #
> -WAYVNC_VERSION := 0.8.0
> -WAYVNC_MD5 := 403b1e45edafa6bf07c9c308639df2b9
> +WAYVNC_VERSION := 0.9.1
> +WAYVNC_MD5 := a24b8dc1e6fe1fd14ad9532d9dc6f0d6
> WAYVNC := wayvnc-$(WAYVNC_VERSION)
> WAYVNC_SUFFIX := tar.gz
> WAYVNC_URL := https://github.com/any1/wayvnc/archive/refs/tags/v$(WAYVNC_VERSION).$(WAYVNC_SUFFIX)
> @@ -53,6 +53,7 @@ $(STATEDIR)/wayvnc.targetinstall:
> @$(call install_fixup, wayvnc,DESCRIPTION,missing)
>
> @$(call install_copy, wayvnc, 0, 0, 0755, -, /usr/bin/wayvnc)
> + @$(call install_copy, wayvnc, 0, 0, 0755, -, /usr/bin/wayvncctl)
>
> @$(call install_finish, wayvnc)
>
prev parent reply other threads:[~2025-03-07 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 8:31 [ptxdist] [PATCH] " Philipp Zabel
2025-03-07 9:49 ` Michael Olbrich [this message]
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=20250307094948.4097014-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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