From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libgpg-error: bump to version 1.39
Date: Sun, 13 Dec 2020 22:10:25 +0100 [thread overview]
Message-ID: <20201213211025.GD3281876@scaer> (raw)
In-Reply-To: <20201213160109.877775-1-fontaine.fabrice@gmail.com>
Fabrice, All,
On 2020-12-13 17:01 +0100, Fabrice Fontaine spake thusly:
> https://dev.gnupg.org/T5031
> https://dev.gnupg.org/T4859
That last one states that mips64 big endian is now supported. But we
already allowed that in Buildroot.
Damn, libgpg-error is weird...
If you can spot any architecture that is now being supported could you
look at updating BR2_PACKAGE_LIBGPG_ERROR_ARCH_SUPPORTS accordingly,
please?
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/libgpg-error/libgpg-error.hash | 7 +++++--
> package/libgpg-error/libgpg-error.mk | 2 +-
> 2 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/package/libgpg-error/libgpg-error.hash b/package/libgpg-error/libgpg-error.hash
> index 05c46d6d43..70aa3a01d8 100644
> --- a/package/libgpg-error/libgpg-error.hash
> +++ b/package/libgpg-error/libgpg-error.hash
> @@ -1,7 +1,10 @@
> +# From https://www.gnupg.org/download/integrity_check.html
> +sha1 991a7a53e778a3de5ba8aad711e0bc9453101f4b libgpg-error-1.39.tar.bz2
> +
> # Locally calculated after checking pgp signature
> -# https://gnupg.org/ftp/gcrypt/libgpg-error/libgpg-error-1.37.tar.bz2.sig
> +# https://gnupg.org/ftp/gcrypt/libgpg-error/libgpg-error-1.39.tar.bz2.sig
> # using key D8692123C4065DEA5E0F3AB5249B39D24F25E3B6
> -sha256 b32d6ff72a73cf79797f7f2d039e95e9c6f92f0c1450215410840ab62aea9763 libgpg-error-1.37.tar.bz2
> +sha256 4a836edcae592094ef1c5a4834908f44986ab2b82e0824a0344b49df8cdb298f libgpg-error-1.39.tar.bz2
> # Locally calculated
> sha256 231f7edcc7352d7734a96eef0b8030f77982678c516876fcb81e25b32d68564c COPYING
> sha256 a9bdde5616ecdd1e980b44f360600ee8783b1f99b8cc83a2beb163a0a390e861 COPYING.LIB
> diff --git a/package/libgpg-error/libgpg-error.mk b/package/libgpg-error/libgpg-error.mk
> index 6281faa662..8980c67012 100644
> --- a/package/libgpg-error/libgpg-error.mk
> +++ b/package/libgpg-error/libgpg-error.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -LIBGPG_ERROR_VERSION = 1.37
> +LIBGPG_ERROR_VERSION = 1.39
> LIBGPG_ERROR_SITE = https://www.gnupg.org/ftp/gcrypt/libgpg-error
> LIBGPG_ERROR_SOURCE = libgpg-error-$(LIBGPG_ERROR_VERSION).tar.bz2
> LIBGPG_ERROR_LICENSE = GPL-2.0+, LGPL-2.1+
> --
> 2.29.2
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/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. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2020-12-13 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 16:01 [Buildroot] [PATCH 1/1] package/libgpg-error: bump to version 1.39 Fabrice Fontaine
2020-12-13 21:10 ` 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=20201213211025.GD3281876@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.