From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-misc/binwalk/
Date: Sat, 30 Oct 2021 17:24:10 +0000 (UTC) [thread overview]
Message-ID: <1635614647.505d4fa5a919ab18a77d5e18bd4c9b88ebf7d055.ago@gentoo> (raw)
commit: 505d4fa5a919ab18a77d5e18bd4c9b88ebf7d055
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 30 17:23:39 2021 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sat Oct 30 17:24:07 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=505d4fa5
app-misc/binwalk: x86 stable wrt bug #820608
Package-Manager: Portage-3.0.20, Repoman-3.0.3
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
app-misc/binwalk/binwalk-2.3.3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-misc/binwalk/binwalk-2.3.3.ebuild b/app-misc/binwalk/binwalk-2.3.3.ebuild
index a6497db7ea2..88ea03d972f 100644
--- a/app-misc/binwalk/binwalk-2.3.3.ebuild
+++ b/app-misc/binwalk/binwalk-2.3.3.ebuild
@@ -13,7 +13,7 @@ if [[ ${PV} == "9999" ]] ; then
inherit git-r3
else
SRC_URI="https://github.com/ReFirmLabs/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
- KEYWORDS="amd64 ~arm arm64 ~ppc ppc64 ~x86 ~x64-macos"
+ KEYWORDS="amd64 ~arm arm64 ~ppc ppc64 x86 ~x64-macos"
fi
DESCRIPTION="A tool for identifying files embedded inside firmware images"
next reply other threads:[~2021-10-30 17:24 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 17:24 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-12 16:56 [gentoo-commits] repo/gentoo:master commit in: app-misc/binwalk/ Arthur Zamarin
2024-09-12 12:27 Arthur Zamarin
2024-09-09 20:58 Arthur Zamarin
2024-09-09 20:47 Arthur Zamarin
2024-09-09 20:44 Arthur Zamarin
2024-09-09 20:44 Arthur Zamarin
2024-08-10 7:24 Joonas Niilola
2024-08-10 7:24 Joonas Niilola
2024-06-11 17:18 Sam James
2024-06-11 16:57 Sam James
2024-06-11 16:57 Sam James
2024-06-11 16:57 Sam James
2024-06-11 16:54 Sam James
2024-06-11 16:54 Sam James
2024-04-28 16:06 Arthur Zamarin
2024-04-28 16:06 Arthur Zamarin
2024-04-24 9:51 Sam James
2024-04-24 6:05 Sam James
2024-04-23 20:53 Sam James
2024-04-23 20:53 Sam James
2024-04-23 20:52 Sam James
2024-04-23 20:52 Sam James
2024-03-25 13:09 Florian Schmaus
2024-03-10 12:13 Arthur Zamarin
2024-03-10 12:13 Arthur Zamarin
2024-03-10 12:08 Sam James
2024-03-10 12:04 Arthur Zamarin
2024-03-10 12:04 Arthur Zamarin
2024-03-10 12:04 Arthur Zamarin
2024-03-08 8:15 Florian Schmaus
2024-03-08 8:15 Florian Schmaus
2024-02-28 20:43 Sam James
2024-02-28 20:43 Sam James
2024-02-28 20:43 Sam James
2023-05-31 4:37 John Helmert III
2023-04-07 4:10 Sam James
2023-04-01 16:07 Arthur Zamarin
2023-04-01 16:07 Arthur Zamarin
2023-04-01 16:07 Arthur Zamarin
2023-04-01 16:07 Arthur Zamarin
2023-04-01 1:09 Sam James
2023-04-01 1:09 Sam James
2022-05-22 4:17 Sam James
2021-12-21 3:39 Yixun Lan
2021-10-29 18:32 Sam James
2021-10-29 18:30 Sam James
2021-10-29 5:52 Agostino Sarubbo
2021-04-26 10:34 Sam James
2021-04-25 12:32 Sam James
2021-04-25 5:14 Sam James
2021-04-24 18:57 Georgy Yakovlev
2021-04-23 20:02 Georgy Yakovlev
2021-04-23 20:02 Georgy Yakovlev
2021-03-23 21:36 Georgy Yakovlev
2021-03-23 21:36 Georgy Yakovlev
2021-03-23 21:36 Georgy Yakovlev
2021-03-04 4:24 Sam James
2021-02-28 12:22 Sergei Trofimovich
2020-10-13 1:31 Georgy Yakovlev
2020-10-13 1:31 Georgy Yakovlev
2020-09-21 6:34 Georgy Yakovlev
2020-07-23 23:02 Sam James
2020-06-11 2:00 Georgy Yakovlev
2020-01-23 9:59 Georgy Yakovlev
2019-12-26 12:56 Georgy Yakovlev
2019-11-19 1:35 Georgy Yakovlev
2019-11-18 22:55 Tim Harder
2019-09-28 3:42 Tim Harder
2018-04-06 11:05 Fabian Groffen
2017-04-26 6:24 Tim Harder
2017-04-26 6:24 Tim Harder
2016-09-02 23:18 Tim Harder
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=1635614647.505d4fa5a919ab18a77d5e18bd4c9b88ebf7d055.ago@gentoo \
--to=ago@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