From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-misc/jq/
Date: Sun, 1 Dec 2024 15:02:35 +0000 (UTC) [thread overview]
Message-ID: <1733065289.df24c1f97695d8a64a82577cd785e85ebe7ad4e7.sam@gentoo> (raw)
commit: df24c1f97695d8a64a82577cd785e85ebe7ad4e7
Author: orbea <orbea <AT> riseup <DOT> net>
AuthorDate: Thu Apr 4 20:24:19 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Dec 1 15:01:29 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=df24c1f9
app-misc/jq: don't use the runpath patch
Strange patch that was added without explanation in commit
ed98a0926d3e99ce9e76fb16311b491797cd1042. It also breaks the build with
slibtoolize where the ./libtool script no longer exists and the sed
fails.
Gentoo-Commit: https://gitweb.gentoo.org/repo/gentoo.git/commit/app-misc/jq?id=ed98a0926d3e99ce9e76fb16311b491797cd1042
Signed-off-by: orbea <orbea <AT> riseup.net>
Closes: https://github.com/gentoo/gentoo/pull/36109
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-misc/jq/jq-1.7.1.ebuild | 1 -
1 file changed, 1 deletion(-)
diff --git a/app-misc/jq/jq-1.7.1.ebuild b/app-misc/jq/jq-1.7.1.ebuild
index b657985218d8..75a18f279527 100644
--- a/app-misc/jq/jq-1.7.1.ebuild
+++ b/app-misc/jq/jq-1.7.1.ebuild
@@ -30,7 +30,6 @@ RDEPEND="
"
PATCHES=(
"${FILESDIR}"/jq-1.6-r3-never-bundle-oniguruma.patch
- "${FILESDIR}"/jq-1.7-runpath.patch
)
RESTRICT="!test? ( test )"
next reply other threads:[~2024-12-01 15:02 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 15:02 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-09 5:27 [gentoo-commits] repo/gentoo:master commit in: app-misc/jq/ Sam James
2024-04-18 5:34 Michał Górny
2024-04-06 12:32 Arthur Zamarin
2024-04-06 12:32 Arthur Zamarin
2023-12-13 20:39 Patrick McLean
2023-10-06 17:05 Arthur Zamarin
2023-10-06 14:55 Sam James
2023-10-06 14:31 Sam James
2023-10-06 14:29 Sam James
2023-09-07 21:40 Patrick McLean
2023-08-30 1:57 Patrick McLean
2023-08-08 2:16 Patrick McLean
2023-06-22 11:14 Fabian Groffen
2023-06-22 8:31 Fabian Groffen
2023-02-28 18:30 Patrick McLean
2023-02-28 1:30 Sam James
2023-02-10 22:18 Patrick McLean
2022-08-25 7:07 WANG Xuerui
2021-08-23 22:59 Marek Szuba
2021-04-18 2:58 Sam James
2021-03-04 0:23 Sam James
2021-02-05 12:31 Sam James
2021-02-04 18:21 Patrick McLean
2020-03-17 18:13 Patrick McLean
2019-11-19 15:40 Agostino Sarubbo
2019-11-19 2:06 Patrick McLean
2019-11-19 1:46 Patrick McLean
2019-11-19 1:34 Patrick McLean
2019-11-19 1:28 Patrick McLean
2019-11-17 5:08 Tim Harder
2019-09-28 2:59 Tim Harder
2019-04-17 18:07 Aaron Bauman
2019-04-13 4:14 Robin H. Johnson
2019-04-13 4:07 Robin H. Johnson
2018-12-05 23:54 Patrick McLean
2018-10-16 9:18 Tobias Klausmann
2017-09-23 10:29 Tim Harder
2017-09-23 10:27 Tim Harder
2017-09-23 10:25 Tim Harder
2017-09-17 11:42 Sergei Trofimovich
2017-09-17 11:14 Sergei Trofimovich
2017-08-17 19:12 Tim Harder
2017-08-17 19:12 Tim Harder
2017-07-21 17:54 Thomas Deutschmann
2017-07-11 19:56 Sergei Trofimovich
2017-07-10 9:32 Sergei Trofimovich
2017-07-10 7:08 Sergei Trofimovich
2017-06-29 8:24 Fabian Groffen
2016-08-08 15:30 Tim Harder
2016-02-01 22:53 Patrick McLean
2016-02-01 22:53 Patrick McLean
2016-01-09 1:14 Patrick McLean
2015-12-22 13:51 Fabian Groffen
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=1733065289.df24c1f97695d8a64a82577cd785e85ebe7ad4e7.sam@gentoo \
--to=sam@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