From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-arch/dump/
Date: Wed, 13 Mar 2024 21:04:40 +0000 (UTC) [thread overview]
Message-ID: <1710363846.06e2a745ebceeb1e828e693e2f0d79738de1cdb0.sam@gentoo> (raw)
commit: 06e2a745ebceeb1e828e693e2f0d79738de1cdb0
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Wed Mar 13 06:46:12 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Mar 13 21:04:06 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=06e2a745
app-arch/dump: mark as LTO-unsafe
Software is abandoned sourceforge-ware. It is also buggy and can cause
corruptions, so not incredibly worth optimizing how fast you can corrupt
your filesystem backups. Definitely not worth engaging with sourceforge
to report the bug.
Closes: https://bugs.gentoo.org/854204
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-arch/dump/dump-0.4.47-r3.ebuild | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/app-arch/dump/dump-0.4.47-r3.ebuild b/app-arch/dump/dump-0.4.47-r3.ebuild
index 90ba51ef81f7..ea26f905f91f 100644
--- a/app-arch/dump/dump-0.4.47-r3.ebuild
+++ b/app-arch/dump/dump-0.4.47-r3.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-inherit readme.gentoo-r1
+inherit flag-o-matic readme.gentoo-r1
MY_P="${PN}-$(ver_rs 2 b)"
@@ -53,6 +53,13 @@ PATCHES=(
)
src_configure() {
+ # -Werror=lto-type-mismatch
+ # https://bugs.gentoo.org/854204
+ #
+ # Abandoned upstream for 3 years. Known corruptions reported in
+ # pkg_postinst. Sourceforge software. Not bothering to report a bug...
+ filter-lto
+
local myeconfargs=(
--with-dumpdatespath=/etc/dumpdates
--with-rmtpath='$(sbindir)/rmt'
next reply other threads:[~2024-03-13 21:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 21:04 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-08 19:19 [gentoo-commits] repo/gentoo:master commit in: app-arch/dump/ Arthur Zamarin
2023-09-19 5:38 Arthur Zamarin
2023-09-08 0:12 Sam James
2023-08-24 18:05 Arthur Zamarin
2023-07-24 22:50 Sam James
2023-07-24 18:16 Sam James
2023-07-24 13:39 Arthur Zamarin
2023-07-24 13:39 Arthur Zamarin
2023-06-06 17:48 Ulrich Müller
2021-09-13 20:30 David Seifert
2021-04-07 22:45 Sam James
2021-04-07 9:20 Sergei Trofimovich
2021-04-06 19:53 Sam James
2021-04-06 19:53 Sam James
2021-04-06 17:21 David Seifert
2021-04-05 19:01 Thomas Deutschmann
2021-04-05 17:28 David Seifert
2021-01-06 19:21 Andreas K. Hüttel
2021-01-04 14:53 Lars Wendler
2020-09-26 14:33 Aaron Bauman
2019-10-14 2:18 Matt Turner
2019-09-09 6:02 Agostino Sarubbo
2019-09-09 6:00 Agostino Sarubbo
2019-09-09 5:50 Agostino Sarubbo
2019-09-09 5:49 Agostino Sarubbo
2019-09-08 10:42 Agostino Sarubbo
2019-09-07 21:07 Thomas Deutschmann
2019-07-15 8:36 Lars Wendler
2017-07-16 0:47 Aaron Bauman
2016-12-02 14:21 Tobias Klausmann
2016-12-01 12:53 Agostino Sarubbo
2016-12-01 12:51 Agostino Sarubbo
2016-11-29 16:02 Lars Wendler
2016-05-09 6:41 Mike Frysinger
2016-03-21 21:46 Anthony G. Basile
2015-12-15 20:32 Anthony G. Basile
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=1710363846.06e2a745ebceeb1e828e693e2f0d79738de1cdb0.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