mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] host-autotools-autoconf-archive: Version bump. 2019.01.06 -> 2021.02.19
Date: Mon,  7 Feb 2022 10:26:58 +0100	[thread overview]
Message-ID: <20220207092700.1871493-2-christian.melki@t2data.com> (raw)
In-Reply-To: <20220207092700.1871493-1-christian.melki@t2data.com>

* Update the autoconf-archive. From the changelog:
The macros AX_CHECK_PCRE2 and AX_PROG_ROBOT have been added.
Many other macros have received updates.

* Copyright year changed in README.

Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
 rules/host-autotools-autoconf-archive.make | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/rules/host-autotools-autoconf-archive.make b/rules/host-autotools-autoconf-archive.make
index ed3be47da..8cbbc2cae 100644
--- a/rules/host-autotools-autoconf-archive.make
+++ b/rules/host-autotools-autoconf-archive.make
@@ -14,8 +14,8 @@ HOST_PACKAGES-$(PTXCONF_HOST_AUTOTOOLS_AUTOCONF_ARCHIVE) += host-autotools-autoc
 #
 # Paths and names
 #
-HOST_AUTOTOOLS_AUTOCONF_ARCHIVE_VERSION	:= 2019.01.06
-HOST_AUTOTOOLS_AUTOCONF_ARCHIVE_MD5	:= d46413c8b00a125b1529bae385bbec55
+HOST_AUTOTOOLS_AUTOCONF_ARCHIVE_VERSION	:= 2021.02.19
+HOST_AUTOTOOLS_AUTOCONF_ARCHIVE_MD5	:= 4f06adfbe3f1a2dada06066cf460e5ab
 HOST_AUTOTOOLS_AUTOCONF_ARCHIVE		:= autoconf-archive-$(HOST_AUTOTOOLS_AUTOCONF_ARCHIVE_VERSION)
 HOST_AUTOTOOLS_AUTOCONF_ARCHIVE_SUFFIX	:= tar.xz
 HOST_AUTOTOOLS_AUTOCONF_ARCHIVE_URL	:= $(call ptx/mirror, GNU, autoconf-archive/$(HOST_AUTOTOOLS_AUTOCONF_ARCHIVE).$(HOST_AUTOTOOLS_AUTOCONF_ARCHIVE_SUFFIX))
@@ -25,7 +25,7 @@ HOST_AUTOTOOLS_AUTOCONF_ARCHIVE_LICENSE	:= GPL-3.0-or-later WITH Autoconf-except
 HOST_AUTOTOOLS_AUTOCONF_ARCHIVE_LICENSE_FILES := \
 	file://COPYING;md5=11cc2d3ee574f9d6b7ee797bdce4d423 \
 	file://COPYING.EXCEPTION;md5=fdef168ebff3bc2f13664c365a5fb515 \
-	file://README;startline=51;endline=67;md5=28397cd25dc41e1932e0d1127aaf1836
+	file://README;startline=51;endline=67;md5=7c82f887b170a4ff706dfa66906b6d35
 
 # ----------------------------------------------------------------------------
 # Prepare
-- 
2.30.2


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


  reply	other threads:[~2022-02-07  9:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  9:26 [ptxdist] [PATCH] cross-nasm: Version bump. 2.15 -> 2.15.05 Christian Melki
2022-02-07  9:26 ` Christian Melki [this message]
2022-02-14 12:43   ` [ptxdist] [APPLIED] host-autotools-autoconf-archive: Version bump. 2019.01.06 -> 2021.02.19 Michael Olbrich
2022-02-21  6:33   ` [ptxdist] [PATCH] " Alexander Dahl
2022-02-07  9:26 ` [ptxdist] [PATCH] host-mtools: Version bump. 4.0.16 -> 4.0.37 Christian Melki
2022-02-14 12:43   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-07  9:27 ` [ptxdist] [PATCH] host-autotools-automake: Version bump. 1.16.1 -> 1.16.5 Christian Melki
2022-02-14 12:43   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-14 12:43 ` [ptxdist] [APPLIED] cross-nasm: Version bump. 2.15 -> 2.15.05 Michael Olbrich

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=20220207092700.1871493-2-christian.melki@t2data.com \
    --to=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    /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