From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/passt/
Date: Sat, 31 Aug 2024 17:53:17 +0000 (UTC) [thread overview]
Message-ID: <1725126783.dd01dfed9af62b7f5c729bf3978108fae9c541d7.zmedico@gentoo> (raw)
commit: dd01dfed9af62b7f5c729bf3978108fae9c541d7
Author: Michal Privoznik <michal.privoznik <AT> gmail <DOT> com>
AuthorDate: Fri Aug 30 07:43:40 2024 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Sat Aug 31 17:53:03 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dd01dfed
net-misc/passt: Don't apply Makefile-2024.03.20.patch on live ebuild
The passt's Makefile was changed so that it no longed enables
_FORTIFY_SOURCE explicitly [1]. This means, the patch that's
applied on top can be dropped.
1: https://passt.top/passt/commit/?id=38363964fc96008761195984c989b036227e0e5c
Signed-off-by: Michal Privoznik <michal.privoznik <AT> gmail.com>
From: https://github.com/gentoo/gentoo/pull/38342
Signed-off-by: Zac Medico <zmedico <AT> gentoo.org>
net-misc/passt/passt-9999.ebuild | 4 ----
1 file changed, 4 deletions(-)
diff --git a/net-misc/passt/passt-9999.ebuild b/net-misc/passt/passt-9999.ebuild
index 37ba4d13c25f..056444e46eba 100644
--- a/net-misc/passt/passt-9999.ebuild
+++ b/net-misc/passt/passt-9999.ebuild
@@ -23,10 +23,6 @@ LICENSE="BSD GPL-2+"
SLOT="0"
IUSE="static"
-PATCHES=(
- "${FILESDIR}"/Makefile-2024.03.20.patch
-)
-
src_prepare() {
default
tc-export CC
next reply other threads:[~2024-08-31 17:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 17:53 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-16 21:22 [gentoo-commits] repo/gentoo:master commit in: net-misc/passt/ Zac Medico
2025-01-10 9:23 Arthur Zamarin
2025-01-10 8:52 Arthur Zamarin
2024-10-11 23:24 Zac Medico
2024-09-01 18:49 Zac Medico
2024-08-31 17:53 Zac Medico
2024-08-24 15:27 Zac Medico
2024-08-22 8:55 WANG Xuerui
2024-08-22 8:55 WANG Xuerui
2024-06-30 5:23 Sam James
2024-06-30 5:10 Sam James
2024-06-13 19:10 Zac Medico
2024-05-12 20:49 Zac Medico
2024-05-05 18:36 Zac Medico
2024-04-18 4:12 Zac Medico
2024-04-01 0:57 Zac Medico
2024-03-31 23:46 Zac Medico
2024-03-21 20:34 Arthur Zamarin
2024-03-21 9:36 Yixun Lan
2024-03-21 0:04 Yixun Lan
2024-02-02 6:37 Zac Medico
2023-12-13 7:54 Florian Schmaus
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=1725126783.dd01dfed9af62b7f5c729bf3978108fae9c541d7.zmedico@gentoo \
--to=zmedico@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