From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-dns/maradns/
Date: Sun, 3 Mar 2024 07:04:05 +0000 (UTC) [thread overview]
Message-ID: <1709449438.34c26b85ef9801e7671e9742e103d5aba32e360a.sam@gentoo> (raw)
commit: 34c26b85ef9801e7671e9742e103d5aba32e360a
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Sun Mar 3 06:57:59 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Mar 3 07:03:58 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=34c26b85
net-dns/maradns: update filter-lto comment
Upstream applied a patch which should fix it. I haven't tested, since it
doesn't backport cleanly. The distfile randomly renames a directory --
the one with the patched code! -- from "deadwood-github" in git to
"deadwood-${PV}" in the distfile, and I cannot be bothered to put up
with such shenanigans and hand-edit a patch hoping to get it to apply.
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-dns/maradns/maradns-3.5.0036.ebuild | 2 ++
1 file changed, 2 insertions(+)
diff --git a/net-dns/maradns/maradns-3.5.0036.ebuild b/net-dns/maradns/maradns-3.5.0036.ebuild
index 30df46007db5..de0218026790 100644
--- a/net-dns/maradns/maradns-3.5.0036.ebuild
+++ b/net-dns/maradns/maradns-3.5.0036.ebuild
@@ -31,6 +31,8 @@ src_configure() {
# -Werror=lto-type-mismatch
# https://bugs.gentoo.org/861293
# https://github.com/samboy/MaraDNS/discussions/124
+ #
+ # should be fixed in git master; try removing this on the next bump
filter-lto
tc-export CC
next reply other threads:[~2024-03-03 7:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 7:04 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-29 5:47 [gentoo-commits] repo/gentoo:master commit in: net-dns/maradns/ Joonas Niilola
2024-05-28 18:19 Arthur Zamarin
2024-03-03 5:52 Sam James
2024-03-03 5:52 Sam James
2024-02-09 13:47 Joonas Niilola
2023-05-05 17:41 Arthur Zamarin
2023-05-05 17:41 Arthur Zamarin
2022-12-18 18:50 Arthur Zamarin
2022-12-18 12:16 Sam James
2022-07-02 20:54 Piotr Karbowski
2022-06-07 5:22 Sam James
2022-06-07 5:21 Sam James
2022-04-10 21:11 Jonas Stein
2021-05-04 22:17 Sam James
2020-09-19 11:28 Michał Górny
2020-08-18 11:22 Agostino Sarubbo
2020-08-18 11:16 Agostino Sarubbo
2020-07-01 19:47 Piotr Karbowski
2020-07-01 19:47 Piotr Karbowski
2020-06-29 21:01 Piotr Karbowski
2019-12-13 22:32 Piotr Karbowski
2019-10-23 13:39 Agostino Sarubbo
2018-09-29 8:45 Michał Górny
2017-12-02 17:58 David Seifert
2017-12-02 17:58 David Seifert
2017-04-30 11:53 Michael Palimaka
2017-04-29 15:02 Agostino Sarubbo
2017-04-28 12:52 Agostino Sarubbo
2017-04-28 12:31 Agostino Sarubbo
2016-08-03 21:37 Michael Orlitzky
2016-04-28 23:44 Austin English
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=1709449438.34c26b85ef9801e7671e9742e103d5aba32e360a.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