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: dev-debug/valgrind/
Date: Fri, 18 Apr 2025 21:33:56 +0000 (UTC)	[thread overview]
Message-ID: <1745011816.99df2dfcd3f65c3d4d7a9cccc79592548bf0c489.sam@gentoo> (raw)

commit:     99df2dfcd3f65c3d4d7a9cccc79592548bf0c489
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 18 21:30:16 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Apr 18 21:30:16 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=99df2dfc

dev-debug/valgrind: sync live

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

 dev-debug/valgrind/valgrind-9999.ebuild | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/dev-debug/valgrind/valgrind-9999.ebuild b/dev-debug/valgrind/valgrind-9999.ebuild
index c8b5db499d34..b8778b8c8633 100644
--- a/dev-debug/valgrind/valgrind-9999.ebuild
+++ b/dev-debug/valgrind/valgrind-9999.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2024 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -74,6 +74,8 @@ QA_CONFIG_IMPL_DECL_SKIP+=(
 	# errors and reports both "function definition is not allowed here" and
 	# -Wimplicit-function-declaration. bug #900396
 	foo
+	# FreeBSD function, bug #932822
+	aio_readv
 )
 
 src_unpack() {


             reply	other threads:[~2025-04-18 21:34 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 21:33 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-10 16:48 [gentoo-commits] repo/gentoo:master commit in: dev-debug/valgrind/ Sam James
2025-05-01 14:25 Sam James
2025-05-01  7:27 Sam James
2025-05-01  7:24 Sam James
2025-05-01  6:07 Sam James
2025-05-01  6:07 Sam James
2025-04-25 14:55 Sam James
2025-04-24 10:30 Sam James
2025-04-19  4:24 Sam James
2025-04-18 21:33 Sam James
2025-03-31 22:23 Sam James
2025-03-28 18:22 Sam James
2025-03-28 18:22 Sam James
2025-03-28 18:22 Sam James
2025-03-28 18:22 Sam James
2025-02-10  8:56 Sam James
2025-01-21  6:17 Arthur Zamarin
2025-01-21  6:17 Arthur Zamarin
2025-01-21  6:17 Arthur Zamarin
2024-12-01  9:00 Sam James
2024-11-27  6:24 Sam James
2024-11-03 21:26 Andreas K. Hüttel
2024-11-01  7:13 Sam James
2024-10-28  8:37 Sam James
2024-10-03  4:46 Sam James
2024-10-03  4:46 Sam James
2024-10-03  4:46 Sam James
2024-08-31  5:15 Sam James
2024-08-30 13:00 Jakov Smolić
2024-08-30 13:00 Jakov Smolić
2024-08-30  8:12 Sam James
2024-08-30  8:12 Sam James
2024-07-07  2:05 Sam James
2024-07-07  1:54 Sam James
2024-06-24  5:33 Sam James
2024-06-12 14:30 Sam James
2024-06-12  4:26 Sam James
2024-06-12  4:26 Sam James
2024-06-11 19:00 Sam James
2024-05-26 23:12 Sam James
2024-05-13 12:52 Arthur Zamarin
2024-05-13  1:06 Sam James
2024-05-13  1:06 Sam James
2024-05-13  1:06 Sam James
2024-04-26 21:35 Sam James
2024-04-26 19:36 Sam James
2024-04-25  8:55 Sam James
2024-04-25  8:55 Sam James
2024-04-24 23:03 Sam James
2024-04-20  4:23 Sam James
2024-01-14  4:32 Sam James
2024-01-14  4:19 Sam James
2024-01-14  4:14 Sam James
2024-01-14  4:08 Sam James
2024-01-14  3:17 Sam James
2024-01-14  3:17 Sam James

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=1745011816.99df2dfcd3f65c3d4d7a9cccc79592548bf0c489.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