From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/yara-python/
Date: Wed, 24 Aug 2022 00:30:51 +0000 (UTC) [thread overview]
Message-ID: <1661301019.e0a3aa3f40e45b5ad87705db8c08759c6ece1c96.sam@gentoo> (raw)
commit: e0a3aa3f40e45b5ad87705db8c08759c6ece1c96
Author: Mario Haustein <mario.haustein <AT> hrz <DOT> tu-chemnitz <DOT> de>
AuthorDate: Tue Aug 23 15:34:58 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Aug 24 00:30:19 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e0a3aa3f
dev-python/yara-python: update Manifest
Tthere are two release notifications from GitHub in my mailbox, one
dated at Tue, 09 Aug 2022 07:51:47 UTC and one at Tue, 09 Aug 2022 14:18:40 UTC
concerning version 4.2.3. My commit was at Tue Aug 9 11:38:20 2022 UTC right
between the two releases. It seems upstream amended the release after my pull request.
Diff between old version & new is fine.
Closes: https://bugs.gentoo.org/866115
Signed-off-by: Mario Haustein <mario.haustein <AT> hrz.tu-chemnitz.de>
Closes: https://github.com/gentoo/gentoo/pull/26979
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/yara-python/Manifest | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/yara-python/Manifest b/dev-python/yara-python/Manifest
index 0821999b4538..7fb67ee0f0f7 100644
--- a/dev-python/yara-python/Manifest
+++ b/dev-python/yara-python/Manifest
@@ -1,2 +1,2 @@
DIST yara-python-4.2.0.gh.tar.gz 34459 BLAKE2B fce460385eaa75dd1779fe49c7937ff36d7604433deb310b6fe9e66af9ea521952f92bee61829372cf19c7efee170329609530f1f9e863991720e4887c3c1349 SHA512 ba08d709fc51679ec9fe36165e0864b79fc241f85c681bf59823fe7bb0e34e928cded050ff296147eb5bcb837485f39949aa93425a0eb9ca8b3730e60fac93f4
-DIST yara-python-4.2.3.gh.tar.gz 34466 BLAKE2B a4c1435a73163cacc445e50d0651306b06df9ceffc1f01eb03b440325a3463672c3829ff48d4b45fa3cdb54e52c7661636b46c81aad39e3b51da0995e192f728 SHA512 d6d083cafe759e47ed1497f97df12679e75e647850696b20d0335d4693ba82970e3bfb23e8e975b4c6f813a8f3f439e96ad9e97d3a7766bb0472d156b1039f83
+DIST yara-python-4.2.3.gh.tar.gz 34465 BLAKE2B 4b9689cef21f9c712960d08c357087f0278d8c20cef3a16072a005a4f8687999aa273c02c22ea9c6d5ea9a6b609c1a6f4c51f01b04f238e9e1faeeaef275d88b SHA512 588875d820f4e1b2aa5c6bbe83814ba2756f5ed301ba652efd280d5ca9745f7388f1f9eaa3875d11de5644ce9c41dcb76eebbee86269f8d6723c7d16ffa134be
next reply other threads:[~2022-08-24 0:30 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 0:30 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-28 4:57 [gentoo-commits] repo/gentoo:master commit in: dev-python/yara-python/ Michał Górny
2025-05-27 17:10 Michał Górny
2025-05-25 8:22 Sam James
2025-05-25 8:22 Sam James
2025-05-17 14:13 Arthur Zamarin
2025-05-17 14:13 Arthur Zamarin
2025-05-03 6:08 Michał Górny
2025-04-24 18:23 Sam James
2025-01-04 15:00 Michał Górny
2025-01-04 14:37 Sam James
2025-01-04 13:28 Arthur Zamarin
2024-12-17 20:17 Arthur Zamarin
2024-05-28 1:59 Sam James
2024-05-08 9:48 Michał Górny
2024-05-08 8:18 Michał Górny
2024-04-19 12:24 Sam James
2024-04-19 12:24 Sam James
2023-10-27 3:20 Sam James
2023-10-19 6:16 Joonas Niilola
2023-10-19 6:16 Joonas Niilola
2023-09-18 7:40 Sam James
2023-05-25 14:38 Michał Górny
2023-05-25 8:25 Arthur Zamarin
2023-05-25 8:08 Arthur Zamarin
2023-05-06 9:18 Arthur Zamarin
2023-05-06 8:58 Sam James
2023-04-25 1:57 Sam James
2023-04-05 12:32 Joonas Niilola
2023-04-05 12:32 Joonas Niilola
2023-01-30 3:27 Sam James
2022-09-26 6:15 Michał Górny
2022-09-25 23:58 Sam James
2022-09-25 23:58 Sam James
2022-08-23 5:34 Sam James
2022-08-23 5:30 Sam James
2022-07-15 0:45 Sam James
2022-07-03 17:29 Arthur Zamarin
2022-06-16 8:10 Michał Górny
2022-06-09 7:29 Sam James
2022-06-09 5:18 Sam James
2022-06-09 5:17 Sam James
2022-04-10 17:01 Sam James
2022-04-05 3:08 Sam James
2022-01-28 8:22 Sam James
2022-01-28 5:18 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=1661301019.e0a3aa3f40e45b5ad87705db8c08759c6ece1c96.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