From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Artur Wiebe <artur@4wiebe.de>
Subject: Re: [ptxdist] [APPLIED] python3-asyncua: version bump 1.0.2 -> 1.0.6
Date: Thu, 8 Feb 2024 17:03:06 +0100 [thread overview]
Message-ID: <20240208160306.3247339-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20240126144807.2774267-5-artur@4wiebe.de>
Thanks, applied as fa4253c259091dcbb1cdae45f43d35dddbee3e3c.
Michael
[sent from post-receive hook]
On Thu, 08 Feb 2024 17:03:06 +0100, Artur Wiebe <artur@4wiebe.de> wrote:
> Signed-off-by: Artur Wiebe <artur@4wiebe.de>
> Message-Id: <20240126144807.2774267-5-artur@4wiebe.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/python3-asyncua.in b/rules/python3-asyncua.in
> index be6210a8be68..552a139eea50 100644
> --- a/rules/python3-asyncua.in
> +++ b/rules/python3-asyncua.in
> @@ -9,6 +9,7 @@ config PYTHON3_ASYNCUA
> select PYTHON3_PYTZ if RUNTIME
> select PYTHON3_CRYPTOGRAPHY if RUNTIME
> select PYTHON3_SORTEDCONTAINERS if RUNTIME
> + select PYTHON3_PYOPENSSL if RUNTIME
> prompt "asyncua"
> help
> OPC UA / IEC 62541 Client and Server for Python
> diff --git a/rules/python3-asyncua.make b/rules/python3-asyncua.make
> index 46be8e635b87..4f26db722abc 100644
> --- a/rules/python3-asyncua.make
> +++ b/rules/python3-asyncua.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_PYTHON3_ASYNCUA) += python3-asyncua
> #
> # Paths and names
> #
> -PYTHON3_ASYNCUA_VERSION := 1.0.2
> -PYTHON3_ASYNCUA_MD5 := 2253852226cae8c893508e84676c465b
> +PYTHON3_ASYNCUA_VERSION := 1.0.6
> +PYTHON3_ASYNCUA_MD5 := 6353843cb95ba72a4e71bf623c26bff0
> PYTHON3_ASYNCUA := asyncua-$(PYTHON3_ASYNCUA_VERSION)
> PYTHON3_ASYNCUA_SUFFIX := tar.gz
> PYTHON3_ASYNCUA_URL := $(call ptx/mirror-pypi, asyncua, $(PYTHON3_ASYNCUA).$(PYTHON3_ASYNCUA_SUFFIX))
next prev parent reply other threads:[~2024-02-08 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 14:48 [ptxdist] [PATCH 1/5] python3-cffi: version bump 1.15.0 -> 1.16.0 Artur Wiebe
2024-01-26 14:48 ` [ptxdist] [PATCH 2/5] python3-pycparser: version bump 2.18 -> 2.21 Artur Wiebe
2024-01-29 8:28 ` Michael Olbrich
2024-01-26 14:48 ` [ptxdist] [PATCH 3/5] python3-pyopenssl: new package Artur Wiebe
2024-02-08 16:03 ` [ptxdist] [APPLIED] " Michael Olbrich
2024-01-26 14:48 ` [ptxdist] [PATCH 4/5] python3-cryptography: version bump 40.0.1 -> 41.0.7 Artur Wiebe
2024-01-29 9:14 ` Michael Olbrich
2024-01-26 14:48 ` [ptxdist] [PATCH 5/5] python3-asyncua: version bump 1.0.2 -> 1.0.6 Artur Wiebe
2024-02-08 16:03 ` Michael Olbrich [this message]
2024-02-08 16:03 ` [ptxdist] [APPLIED] python3-cffi: version bump 1.15.0 -> 1.16.0 Michael Olbrich
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=20240208160306.3247339-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=artur@4wiebe.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