Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2 v2] package/asterisk: bump to 20.6.0
Date: Sat, 03 Feb 2024 11:31:49 +0100	[thread overview]
Message-ID: <87msshu9d6.fsf@48ers.dk> (raw)
In-Reply-To: <Zb0RQA8kV+RXOd0h@waldemar-brodkorb.de> (Waldemar Brodkorb's message of "Fri, 2 Feb 2024 16:58:56 +0100")

>>>>> "Waldemar" == Waldemar Brodkorb <wbx@openadk.org> writes:

 > See here for changes:
 > https://downloads.asterisk.org/pub/telephony/asterisk/ChangeLog-20-current.md

 > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
 > ---
 v1-> v2:
 >  - use separate libjwt package instead of bundled one, suggested by
 >    Peter Korsgaard
 > ---
 >  package/asterisk/Config.in     | 1 +
 >  package/asterisk/asterisk.hash | 2 +-
 >  package/asterisk/asterisk.mk   | 6 ++++--
 >  3 files changed, 6 insertions(+), 3 deletions(-)

 > diff --git a/package/asterisk/Config.in b/package/asterisk/Config.in
 > index c52456f8fc..662f070dac 100644
 > --- a/package/asterisk/Config.in
 > +++ b/package/asterisk/Config.in
 > @@ -10,6 +10,7 @@ config BR2_PACKAGE_ASTERISK
 >  	select BR2_PACKAGE_LIBCURL
 >  	select BR2_PACKAGE_LIBEDIT
 >  	select BR2_PACKAGE_LIBILBC
 > +	select BR2_PACKAGE_LIBJWT
 >  	select BR2_PACKAGE_LIBXML2
 >  	select BR2_PACKAGE_SQLITE
 >  	select BR2_PACKAGE_UTIL_LINUX
 > diff --git a/package/asterisk/asterisk.hash b/package/asterisk/asterisk.hash
 > index 246f4219aa..d50955dd2b 100644
 > --- a/package/asterisk/asterisk.hash
 > +++ b/package/asterisk/asterisk.hash
 > @@ -1,5 +1,5 @@
 >  # Locally computed
 > -sha256  9def260ac8745a5eac7aceabe1c22f84a283b7812f0eccd760f87ce9eb991d22  asterisk-20.5.2.tar.gz
 > +sha256  088dbc08916e21528dba364f5452b2090b066dbba4548b32ec10af138d4b442f  asterisk-20.6.0.tar.gz
 
 >  # sha1 from: http://downloads.asterisk.org/pub/telephony/sounds/releases
 >  # sha256 locally computed
 > diff --git a/package/asterisk/asterisk.mk b/package/asterisk/asterisk.mk
 > index d1f3ea82d3..869e4128ff 100644
 > --- a/package/asterisk/asterisk.mk
 > +++ b/package/asterisk/asterisk.mk
 > @@ -4,7 +4,7 @@
 >  #
 >  ################################################################################
 
 > -ASTERISK_VERSION = 20.5.2
 > +ASTERISK_VERSION = 20.6.0
 >  # Use the github mirror: it's an official mirror maintained by Digium, and
 >  # provides tarballs, which the main Asterisk git tree (behind Gerrit) does not.
 >  ASTERISK_SITE = $(call github,asterisk,asterisk,$(ASTERISK_VERSION))
 > @@ -27,7 +27,7 @@ ASTERISK_SELINUX_MODULES = asterisk
 
 >  # For patches 0002 and 0003
 >  ASTERISK_AUTORECONF = YES
 > -ASTERISK_AUTORECONF_OPTS = -Iautoconf -Ithird-party -Ithird-party/pjproject -Ithird-party/jansson
 > +ASTERISK_AUTORECONF_OPTS = -Iautoconf -Ithird-party -Ithird-party/pjproject -Ithird-party/jansson -Ithird-party/libjwt

Why do we still need to point autoreconf to the bundle libjwt?

Even worse, I see the following during the configure step:

checking for embedded pjproject (may have to download)... configuring
[pjproject]  Downloading https://raw.githubusercontent.com/asterisk/third-party/master/pjproject/2.13.1/pjproject-2.13.1.tar.bz2 to /tmp/pjproject-2.13.1.tar.bz2
[pjproject]  Verifying /tmp/pjproject-2.13.1.tar.bz2
[pjproject]  Verify successful
[pjproject]  Verifying /tmp/pjproject-2.13.1.tar.bz2
[pjproject]  Verify successful
[pjproject]  Unpacking /tmp/pjproject-2.13.1.tar.bz2

We don't want packages to download stuff behind our back. Can we use an
external pjproject?

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-03 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 15:58 [Buildroot] [PATCH 2/2 v2] package/asterisk: bump to 20.6.0 Waldemar Brodkorb
2024-02-03 10:31 ` Peter Korsgaard [this message]
2024-02-04  7:40   ` Waldemar Brodkorb

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=87msshu9d6.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=wbx@openadk.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