From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Enrico Jorns <ejo@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] rauc: version bump 1.8 -> 1.9
Date: Thu, 16 Mar 2023 15:31:22 +0100 [thread overview]
Message-ID: <20230316143122.3676019-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230308085858.3482511-1-ejo@pengutronix.de>
Thanks, applied as 00d31655443b118b146d22dd3d36e9e21dfd526a.
Michael
[sent from post-receive hook]
On Thu, 16 Mar 2023 15:31:22 +0100, Enrico Jorns <ejo@pengutronix.de> wrote:
> RAUC switched to meson as the main build system but kept autotools for
> this release to ease migration.
> Since the meson-generated artifact does not have a 'configure' file, a
> separate autools release tarball was created that is used here.
>
> Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
> Message-Id: <20230308085858.3482511-1-ejo@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/rauc.make b/rules/rauc.make
> index cac186a64b0c..0502fd3704ed 100644
> --- a/rules/rauc.make
> +++ b/rules/rauc.make
> @@ -14,11 +14,11 @@ PACKAGES-$(PTXCONF_RAUC) += rauc
> #
> # Paths and names
> #
> -RAUC_VERSION := 1.8
> -RAUC_MD5 := acd0e788d804bda6645a2506c1068789
> +RAUC_VERSION := 1.9
> +RAUC_MD5 := 5b6ca0032185828f8f22d9a416319c3a
> RAUC := rauc-$(RAUC_VERSION)
> RAUC_SUFFIX := tar.xz
> -RAUC_URL := https://github.com/rauc/rauc/releases/download/v$(RAUC_VERSION)/$(RAUC).$(RAUC_SUFFIX)
> +RAUC_URL := https://github.com/rauc/rauc/releases/download/v$(RAUC_VERSION)/$(RAUC)-autotools.$(RAUC_SUFFIX)
> RAUC_SOURCE := $(SRCDIR)/$(RAUC).$(RAUC_SUFFIX)
> RAUC_DIR := $(BUILDDIR)/$(RAUC)
> RAUC_LICENSE := LGPL-2.1-only
prev parent reply other threads:[~2023-03-16 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 8:58 [ptxdist] [PATCH] " Enrico Jorns
2023-03-16 14:31 ` 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=20230316143122.3676019-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ejo@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