From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-debug/valgrind/
Date: Wed, 27 Nov 2024 06:24:05 +0000 (UTC) [thread overview]
Message-ID: <1732688620.c2d2acb20658b6932b37542762b2ac4d9ba7f79e.sam@gentoo> (raw)
commit: c2d2acb20658b6932b37542762b2ac4d9ba7f79e
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 27 06:20:27 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Nov 27 06:23:40 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2d2acb2
dev-debug/valgrind: add 3.24.0_p1
Mark Wielaard (9):
Set version to 3.24.1.GIT
Prepare NEWS for branch 3.24 fixes
vgdb.c (fork_and_exec_valgrind): Fix off-by-one error write
vgdb.c (fork_and_exec_valgrind): Fix another off-by-one error write
Add exp and supp patterns for missing main frame for ppc64le
helgrind/tests/tc17_sembar.c: Remove bool typedef
drd/tests/swapcontext.c: Rename typedef struct thread_local to threadlocal
none/tests/bug234814.c: sa_handler take an int as argument
Add open_tree, move_mount, fsopen, fsconfig, fsmount, fspick linux syswraps
Paul Floyd (2):
regtest: add a fdleak filter for write on write on linux arm64
Add additional exp-ppc64le files to EXTRA_DIST
Peter Seiderer (1):
Add support for landlock_create_ruleset (444), landlock_add_rule (445) and landlock_restrict_self (446) syscalls
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-debug/valgrind/Manifest | 1 +
.../valgrind/{valgrind-9999.ebuild => valgrind-3.24.0_p1.ebuild} | 4 +++-
dev-debug/valgrind/valgrind-9999.ebuild | 4 +++-
3 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/dev-debug/valgrind/Manifest b/dev-debug/valgrind/Manifest
index b30ce2fc0446..0b8d5a0a2a36 100644
--- a/dev-debug/valgrind/Manifest
+++ b/dev-debug/valgrind/Manifest
@@ -1,5 +1,6 @@
DIST valgrind-3.23.0-patches-3.tar.xz 23084 BLAKE2B 4794143bd80f984d5dc07f792837faa139a4bf8cc6220c7c1e79b85f2c0e6ee579eb5e4220decc264a4e21424683554794d015e10aee20b9e34c16724d64eb58 SHA512 0144142d62552158d90a118591a50412d077d3e79fce333fb6da40aff8acd6c924d15c85f69293d1a189b2ecde66c184cf82c8ba3a134f95c439d50e147e331c
DIST valgrind-3.23.0.tar.bz2 16550038 BLAKE2B 9312761b0531006725f13270984b26c48f71ebe66e355b04410d7c01773c9b78ec21db3259cab398e58b3b68f93f5f074db06efe1f359bd7cf423515576191a4 SHA512 27d038faaaf6154cace2df18c3573291393548ba0738dbb6aba58eab6324c5beaa95fc5f3c0271663ca071baf829b15d806f7e81074f7cf087bef20ea0ed3117
DIST valgrind-3.23.0.tar.bz2.asc 488 BLAKE2B b06781577e3e84e506e56bd4acc7341aecacb6b5898d8f0daab627d24bc70c9c60edad11dc7e3723ac77aa9c7978f1e13af7734e7a37763c720e77ea4ff103a4 SHA512 e10b38c72ed1fb8d79a3fa84ab70c475ec7a15927a578ee6715aa74f9600453f0fb72551053b6c31583321c37dab100bafbf6e689c02a3bc06021f6092b4bc80
+DIST valgrind-3.24.0-patches-1.tar.xz 10112 BLAKE2B 83e3b5970b4b4af60dacd90d0d7153359ece8f207f99e3325c8504a0fca123db3b803f2c745ed184f9aa3a4a54d1f922067dd060ce8d18d8b8bd4b936f676602 SHA512 054f5c9ee2676f172e896838e6fb50b1e51a842a8ede2dacb7def01c786bbd874f8099d9bd9ddb0ae88c7d1b32686dee80631ea7f6e27b0efd78a6c1fbdaaaec
DIST valgrind-3.24.0.tar.bz2 16632387 BLAKE2B e11ad08f0062bd39788cd71d7ce058dec7a7207fbbe25f0dbfc7fb5735667809681cec2c843659553fbd49bcc6c71bdb93d87ffda3589247e4ee87c98fe51332 SHA512 6c131ff93d1f432d8362a47285cc377cba224ebca4f18e922c6156f7736d43020ece14d8fd16913498ab00fd18c85e2042a7d5351c3901e80413c584ebb406f3
DIST valgrind-3.24.0.tar.bz2.asc 488 BLAKE2B f6307d10ee3ca26d837bf00471d179655ddbb0137920e175767a9d875aae355cea6727112deb788300a5196d94500bf9b341f8c70d46a1f83c40ae579ad45431 SHA512 37e9188756940960dcfe771d10275de7759ae652c94e710618948a8b366f66f3453f77b7751df0010b58304b203d7b3b56ac7a671d142d620916689ce5c84ae0
diff --git a/dev-debug/valgrind/valgrind-9999.ebuild b/dev-debug/valgrind/valgrind-3.24.0_p1.ebuild
similarity index 97%
copy from dev-debug/valgrind/valgrind-9999.ebuild
copy to dev-debug/valgrind/valgrind-3.24.0_p1.ebuild
index bd5cb983fad2..67740a66998a 100644
--- a/dev-debug/valgrind/valgrind-9999.ebuild
+++ b/dev-debug/valgrind/valgrind-3.24.0_p1.ebuild
@@ -29,7 +29,9 @@ else
https://sourceware.org/pub/valgrind/${MY_P}.tar.bz2
verify-sig? ( https://sourceware.org/pub/valgrind/${MY_P}.tar.bz2.asc )
"
- # Rollups of backports on ${PV}_STABLE branch upstream.
+ # Rollups of backports on ${PV}_STABLE branch upstream. This branch
+ # is usually announced on the mailing list and distros are encouraged
+ # to pull from it regularly.
if [[ ${PV} == *_p* ]] ; then
SRC_URI+=" https://dev.gentoo.org/~sam/distfiles/${CATEGORY}/${PN}/${VALGRIND_PATCH_TARBALL}.tar.xz"
fi
diff --git a/dev-debug/valgrind/valgrind-9999.ebuild b/dev-debug/valgrind/valgrind-9999.ebuild
index bd5cb983fad2..67740a66998a 100644
--- a/dev-debug/valgrind/valgrind-9999.ebuild
+++ b/dev-debug/valgrind/valgrind-9999.ebuild
@@ -29,7 +29,9 @@ else
https://sourceware.org/pub/valgrind/${MY_P}.tar.bz2
verify-sig? ( https://sourceware.org/pub/valgrind/${MY_P}.tar.bz2.asc )
"
- # Rollups of backports on ${PV}_STABLE branch upstream.
+ # Rollups of backports on ${PV}_STABLE branch upstream. This branch
+ # is usually announced on the mailing list and distros are encouraged
+ # to pull from it regularly.
if [[ ${PV} == *_p* ]] ; then
SRC_URI+=" https://dev.gentoo.org/~sam/distfiles/${CATEGORY}/${PN}/${VALGRIND_PATCH_TARBALL}.tar.xz"
fi
next reply other threads:[~2024-11-27 6:24 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 6:24 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-25 1:07 [gentoo-commits] repo/gentoo:master commit in: dev-debug/valgrind/ Sam James
2025-10-18 16:47 Sam James
2025-10-18 16:00 Sam James
2025-09-06 20:54 Sam James
2025-07-04 3:26 Eli Schwartz
2025-06-22 15:47 Sam James
2025-06-22 14:50 Sam James
2025-06-21 17:50 Sam James
2025-06-19 1:40 Sam James
2025-06-19 1:40 Sam James
2025-06-19 1:40 Sam James
2025-05-20 19:07 Sam James
2025-05-10 16:48 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-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-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=1732688620.c2d2acb20658b6932b37542762b2ac4d9ba7f79e.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