From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/4] make.sh: Added p11-kit and libtasn1 for python3 based ca-certificates approach
Date: Mon, 23 Aug 2021 11:34:11 +0100 [thread overview]
Message-ID: <6B2CD430-22CF-42B1-A7F0-89AB18B3EA2A@ipfire.org> (raw)
In-Reply-To: <20210820200428.3535766-2-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 20 Aug 2021, at 21:04, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - p11-kit required for certs extraction in building of python3 compatible ca-certificates
> - p11-kit requires libtasn1 as a build dependency
> - p11-kit and libtasn1 added to make.sh
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> make.sh | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/make.sh b/make.sh
> index 0baf2050d..7608e1630 100755
> --- a/make.sh
> +++ b/make.sh
> @@ -1234,6 +1234,8 @@ buildipfire() {
> lfsmake2 grub
> lfsmake2 efivar
> lfsmake2 efibootmgr
> + lfsmake2 libtasn1
> + lfsmake2 p11-kit
> lfsmake2 ca-certificates
> lfsmake2 fireinfo
> lfsmake2 libnet
> --
> 2.33.0
>
next prev parent reply other threads:[~2021-08-23 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 20:04 [PATCH 1/4] ca-certificates: Update to work with python3 version of certdata2pem.py Adolf Belka
2021-08-20 20:04 ` [PATCH 2/4] make.sh: Added p11-kit and libtasn1 for python3 based ca-certificates approach Adolf Belka
2021-08-23 10:34 ` Michael Tremer [this message]
2021-08-20 20:04 ` [PATCH 3/4] p11-kit: New program required for python3 compatibility of ca-certificates Adolf Belka
2021-08-23 10:34 ` Michael Tremer
2021-08-20 20:04 ` [PATCH 4/4] libtasn1: New program required as build dependency for p11-kit Adolf Belka
2021-08-23 10:34 ` Michael Tremer
2021-08-23 10:34 ` [PATCH 1/4] ca-certificates: Update to work with python3 version of certdata2pem.py 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=6B2CD430-22CF-42B1-A7F0-89AB18B3EA2A@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