public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/libfaketime/
Date: Mon, 26 May 2025 08:13:18 +0000 (UTC)	[thread overview]
Message-ID: <1748247174.a56a52b6d5a4145c5eba5cf30739f0e3e6fb7b45.sam@gentoo> (raw)

commit:     a56a52b6d5a4145c5eba5cf30739f0e3e6fb7b45
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon May 26 08:12:54 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon May 26 08:12:54 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a56a52b6

sys-libs/libfaketime: drop obsolete sed

I'd meant to do this before and forgot. The warning is still there but we drop
-Werror so...

Signed-off-by: Sam James <sam <AT> gentoo.org>

 sys-libs/libfaketime/libfaketime-0.9.11.ebuild | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/sys-libs/libfaketime/libfaketime-0.9.11.ebuild b/sys-libs/libfaketime/libfaketime-0.9.11.ebuild
index 748369074ad3..3422e091fe82 100644
--- a/sys-libs/libfaketime/libfaketime-0.9.11.ebuild
+++ b/sys-libs/libfaketime/libfaketime-0.9.11.ebuild
@@ -18,9 +18,6 @@ src_prepare() {
 
 	sed -i -e 's/-Werror //' {src,test}/Makefile || die
 
-	# Bug #617624 (GCC-6 compatibility)
-	sed -i 's/-Wno-nonnull-compare //' src/Makefile || die
-
 	# bug #863911
 	filter-lto
 


             reply	other threads:[~2025-05-26  8:13 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26  8:13 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-01 22:42 [gentoo-commits] repo/gentoo:master commit in: sys-libs/libfaketime/ Sam James
2025-09-01 22:42 Sam James
2025-09-01 17:34 Arthur Zamarin
2025-09-01 17:34 Arthur Zamarin
2025-08-30  6:48 Arthur Zamarin
2025-07-13  6:47 Sam James
2025-06-20 16:58 Arthur Zamarin
2025-05-25 15:39 Sam James
2024-03-03 22:08 Sam James
2024-03-03 21:44 Andreas K. Hüttel
2024-03-03 21:44 Andreas K. Hüttel
2023-11-24  9:31 Sam James
2023-03-04  8:18 Arthur Zamarin
2023-03-04  7:47 Arthur Zamarin
2023-03-04  7:28 Arthur Zamarin
2023-03-04  6:29 Arthur Zamarin
2023-03-04  5:49 Arthur Zamarin
2022-08-25  3:50 Sam James
2022-08-25  3:47 Sam James
2022-08-25  3:47 Sam James
2022-05-19  9:27 Yixun Lan
2022-05-19  9:27 Yixun Lan
2021-04-24 16:26 Thomas Deutschmann
2021-04-24 16:26 Thomas Deutschmann
2021-03-01 18:06 Thomas Deutschmann
2021-03-01 18:06 Thomas Deutschmann
2020-06-13 21:09 Matt Turner
2020-05-08  9:36 Sergei Trofimovich
2020-05-03 10:25 Agostino Sarubbo
2020-04-04 10:52 Sergei Trofimovich
2020-03-29 21:21 Sergei Trofimovich
2020-03-28 23:40 Sergei Trofimovich
2020-03-16 20:09 Matt Turner
2020-03-03  0:03 Thomas Deutschmann
2020-03-03  0:03 Thomas Deutschmann
2020-03-03  0:03 Thomas Deutschmann
2020-03-03  0:03 Thomas Deutschmann
2018-06-03  8:00 Mart Raudsepp
2018-03-28  5:05 Markus Meier
2017-11-23 20:48 Thomas Deutschmann
2017-10-01 19:38 Sergei Trofimovich
2017-08-12 19:11 Thomas Deutschmann
2017-05-18 19:16 Thomas Deutschmann
2017-05-07  7:06 Thomas Deutschmann
2016-12-05 16:26 Mike Frysinger
2016-09-25 19:57 Jeroen Roovers
2016-09-14 20:20 Thomas Deutschmann
2016-05-19  9:42 Jeroen Roovers
2016-03-15 17:28 Markus Meier
2015-09-15  0:41 Tim Harder

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=1748247174.a56a52b6d5a4145c5eba5cf30739f0e3e6fb7b45.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