public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-arch/libarchive/, app-arch/libarchive/files/
Date: Mon, 29 Jul 2024 20:00:15 +0000 (UTC)	[thread overview]
Message-ID: <1722283179.7a5e420e408012a569f8170b8138c318abcebda7.grobian@gentoo> (raw)

commit:     7a5e420e408012a569f8170b8138c318abcebda7
Author:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 29 19:59:39 2024 +0000
Commit:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Mon Jul 29 19:59:39 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7a5e420e

app-arch/libarchive-3.7.4: add patch from upstream for INT_MAX usage

Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>

 .../files/libarchive-3.7.4-INT_MAX.patch           | 26 ++++++++++++++++++++++
 app-arch/libarchive/libarchive-3.7.4.ebuild        |  2 ++
 2 files changed, 28 insertions(+)

diff --git a/app-arch/libarchive/files/libarchive-3.7.4-INT_MAX.patch b/app-arch/libarchive/files/libarchive-3.7.4-INT_MAX.patch
new file mode 100644
index 000000000000..150216b3344d
--- /dev/null
+++ b/app-arch/libarchive/files/libarchive-3.7.4-INT_MAX.patch
@@ -0,0 +1,26 @@
+From 6ff1cd1e487ddf545337b88da3f1f5ca69a2f958 Mon Sep 17 00:00:00 2001
+From: Tim Kientzle <kientzle@acm.org>
+Date: Mon, 6 May 2024 20:46:26 -0700
+Subject: [PATCH] Define INT_MAX via `#include <limits.h>` (#2170)
+
+#2110 added usages of INT_MAX here without adding the necessary header.
+
+Resolves #2162
+---
+ tar/bsdtar.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/tar/bsdtar.c b/tar/bsdtar.c
+index 42baab286..f0e71afd1 100644
+--- a/tar/bsdtar.c
++++ b/tar/bsdtar.c
+@@ -43,6 +43,9 @@
+ #ifdef HAVE_LANGINFO_H
+ #include <langinfo.h>
+ #endif
++#ifdef HAVE_LIMITS_H
++#include <limits.h>
++#endif
+ #ifdef HAVE_LOCALE_H
+ #include <locale.h>
+ #endif

diff --git a/app-arch/libarchive/libarchive-3.7.4.ebuild b/app-arch/libarchive/libarchive-3.7.4.ebuild
index 7c609d3a3f58..695219f457cd 100644
--- a/app-arch/libarchive/libarchive-3.7.4.ebuild
+++ b/app-arch/libarchive/libarchive-3.7.4.ebuild
@@ -74,6 +74,8 @@ PATCHES=(
 	# https://github.com/libarchive/libarchive/issues/2069
 	# (we can simply update the command since we don't support old lrzip)
 	"${FILESDIR}/${PN}-3.7.2-lrzip.patch"
+	# https://github.com/libarchive/libarchive/commit/6ff1cd1e487ddf545337b88da3f1f5ca69a2f958
+	"${FILESDIR}/${PN}-3.7.4-INT_MAX.patch"
 )
 
 src_prepare() {


             reply	other threads:[~2024-07-29 20:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 20:00 Fabian Groffen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-31 15:36 [gentoo-commits] repo/gentoo:master commit in: app-arch/libarchive/, app-arch/libarchive/files/ Michał Górny
2024-02-16 13:53 Michał Górny
2023-04-08 18:45 Michał Górny
2022-02-11 13:36 Michał Górny
2021-04-30 23:27 Sam James
2020-12-18 18:16 Fabian Groffen
2019-09-02  7:07 Lars Wendler
2018-04-19 15:24 Aaron Bauman
2018-01-02 13:12 Michał Górny
2017-06-29 23:39 Patrick McLean
2016-07-26 17:56 NP Hardass
2016-05-11  4:02 NP Hardass

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=1722283179.7a5e420e408012a569f8170b8138c318abcebda7.grobian@gentoo \
    --to=grobian@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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