From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: David Jander <david@protonic.nl>
Subject: Re: [ptxdist] [APPLIED] libuv version bump 1.34.0 -> 1.42.0
Date: Mon, 9 May 2022 08:29:19 +0200 [thread overview]
Message-ID: <20220509062919.3767856-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220503123346.1439367-2-david@protonic.nl>
Thanks, applied as 31808a531cf1a1ff710073172fa062c21e106c19.
Michael
[sent from post-receive hook]
On Mon, 09 May 2022 08:29:18 +0200, David Jander <david@protonic.nl> wrote:
> Needed for python3-uvloop
>
> Signed-off-by: David Jander <david@protonic.nl>
> Message-Id: <20220503123346.1439367-2-david@protonic.nl>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/libuv-v1.34.0/autogen.sh b/patches/libuv-v1.42.0/autogen.sh
> similarity index 100%
> rename from patches/libuv-v1.34.0/autogen.sh
> rename to patches/libuv-v1.42.0/autogen.sh
> diff --git a/rules/libuv.make b/rules/libuv.make
> index 96f22a04298a..8a9cbacb6a1f 100644
> --- a/rules/libuv.make
> +++ b/rules/libuv.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBUV) += libuv
> #
> # Paths and names
> #
> -LIBUV_VERSION := 1.34.0
> -LIBUV_MD5 := 811ebe06c326e788ac7adf062328f3f1
> +LIBUV_VERSION := 1.42.0
> +LIBUV_MD5 := 484dec4a06e183c20be815019ce9ddd0
> LIBUV := libuv-v$(LIBUV_VERSION)
> LIBUV_SUFFIX := tar.gz
> LIBUV_URL := https://dist.libuv.org/dist/v$(LIBUV_VERSION)/$(LIBUV).$(LIBUV_SUFFIX)
next prev parent reply other threads:[~2022-05-09 6:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 12:33 [ptxdist] [PATCH V2 0/2] Add python3-uvloop David Jander
2022-05-03 12:33 ` [ptxdist] [PATCH V2 1/2] libuv version bump 1.34.0 -> 1.42.0 David Jander
2022-05-09 6:29 ` Michael Olbrich [this message]
2022-05-03 12:33 ` [ptxdist] [PATCH V2 2/2] python3-uvloop: new package David Jander
2022-05-06 7:29 ` Michael Olbrich
2022-05-06 11:31 ` Michael Olbrich
2022-05-06 11:34 ` Michael Olbrich
2022-05-06 11:51 ` David Jander
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=20220509062919.3767856-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=david@protonic.nl \
--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