From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] libgcrypt: update to 1.8.4
Date: Tue, 05 Mar 2019 09:45:48 +0000 [thread overview]
Message-ID: <DA002D0D-E38F-4577-B50E-B954E6751420@ipfire.org> (raw)
In-Reply-To: <a4ea5fa0-1a86-788a-74db-ebad67e72307@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]
Hi,
Thank you for submitting this patch. Sadly, it does not build. I am getting:
checking for gpg-error-config... /usr/bin/gpg-error-config
checking for GPG Error - version >= 1.25... no
configure: error: libgpg-error is needed.
See ftp://ftp.gnupg.org/gcrypt/libgpg-error/ .
Could you please add libgpg-error-devel >= 1.25 as dependency? The package is already available in 1.27, but the build system should know which one it is supposed to use.
Best,
-Michael
> On 4 Mar 2019, at 18:32, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> libgcrypt/libgcrypt.nm | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/libgcrypt/libgcrypt.nm b/libgcrypt/libgcrypt.nm
> index a0488a20c..b1d313777 100644
> --- a/libgcrypt/libgcrypt.nm
> +++ b/libgcrypt/libgcrypt.nm
> @@ -4,11 +4,11 @@
> ###############################################################################
>
> name = libgcrypt
> -version = 1.8.1
> +version = 1.8.4
> release = 1
>
> groups = System/Libraries
> -url = http://www.gnupg.org/
> +url = https://gnupg.org/software/libgcrypt/index.html
> license = LGPLv2.1+
> summary = A general-purpose cryptography library.
>
> @@ -18,7 +18,7 @@ description
> in GNU Privacy Guard.
> end
>
> -source_dl = ftp://ftp.gnupg.org/gcrypt/libgcrypt/
> +source_dl = https://gnupg.org/ftp/gcrypt/libgcrypt/
> sources = %{thisapp}.tar.bz2
>
> build
> --
> 2.16.4
next prev parent reply other threads:[~2019-03-05 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 18:32 Peter Müller
2019-03-05 9:45 ` Michael Tremer [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-23 16:58 Peter Müller
2019-02-26 9:54 ` Michael Tremer
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=DA002D0D-E38F-4577-B50E-B954E6751420@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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