From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-cffi: bump to version 1.17.1
Date: Sat, 21 Sep 2024 22:17:45 +0200 [thread overview]
Message-ID: <Zu8p6WUIIASFTeOc@landeda> (raw)
In-Reply-To: <20240905194023.1103271-1-james.hilliard1@gmail.com>
James, All,
On 2024-09-05 13:40 -0600, James Hilliard spake thusly:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/python-cffi/python-cffi.hash | 4 ++--
> package/python-cffi/python-cffi.mk | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/package/python-cffi/python-cffi.hash b/package/python-cffi/python-cffi.hash
> index 0573d6ec06..2847d38b55 100644
> --- a/package/python-cffi/python-cffi.hash
> +++ b/package/python-cffi/python-cffi.hash
> @@ -1,5 +1,5 @@
> # md5, sha256 from https://pypi.org/pypi/cffi/json
> -md5 0bcaed453da3004d0bea103038345c1e cffi-1.16.0.tar.gz
> -sha256 bcb3ef43e58665bbda2fb198698fcae6776483e0c4a631aa5647806c25e02cc0 cffi-1.16.0.tar.gz
> +md5 4336ca58b2df0cc3b163884d5fa2e5e2 cffi-1.17.1.tar.gz
> +sha256 1c39c6016c32bc48dd54561950ebd6836e1670f2ae46128f67cf49e789c52824 cffi-1.17.1.tar.gz
> # Locally computed sha256 checksums
> sha256 04b80f5b077bbed68808cfebadeb5e3523f2a8c9a96495c587bd96df1eac2a33 LICENSE
> diff --git a/package/python-cffi/python-cffi.mk b/package/python-cffi/python-cffi.mk
> index 1f83db079b..152009e8ca 100644
> --- a/package/python-cffi/python-cffi.mk
> +++ b/package/python-cffi/python-cffi.mk
> @@ -4,9 +4,9 @@
> #
> ################################################################################
>
> -PYTHON_CFFI_VERSION = 1.16.0
> +PYTHON_CFFI_VERSION = 1.17.1
> PYTHON_CFFI_SOURCE = cffi-$(PYTHON_CFFI_VERSION).tar.gz
> -PYTHON_CFFI_SITE = https://files.pythonhosted.org/packages/68/ce/95b0bae7968c65473e1298efb042e10cafc7bafc14d9e4f154008241c91d
> +PYTHON_CFFI_SITE = https://files.pythonhosted.org/packages/fc/97/c783634659c2920c3fc70419e3af40972dbaf758daa229a7d6ea6135c90d
> PYTHON_CFFI_SETUP_TYPE = setuptools
> PYTHON_CFFI_DEPENDENCIES = host-pkgconf libffi
> PYTHON_CFFI_LICENSE = MIT
> --
> 2.34.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-09-21 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 19:40 [Buildroot] [PATCH 1/1] package/python-cffi: bump to version 1.17.1 James Hilliard
2024-09-21 20:17 ` Yann E. MORIN [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=Zu8p6WUIIASFTeOc@landeda \
--to=yann.morin.1998@free.fr \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.