From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/libb2/
Date: Thu, 26 Sep 2019 20:09:40 +0000 (UTC) [thread overview]
Message-ID: <1569528530.a24aa61ffad81296cf0e6d10d56ffa0ff333d019.zlogene@gentoo> (raw)
commit: a24aa61ffad81296cf0e6d10d56ffa0ff333d019
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Sep 26 20:08:50 2019 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Thu Sep 26 20:08:50 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a24aa61f
app-crypt/libb2: m68k stable wrt bug #694366
Package-Manager: Portage-2.3.69, Repoman-2.3.16
RepoMan-Options: --include-arches="m68k"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
app-crypt/libb2/libb2-0.98.1-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-crypt/libb2/libb2-0.98.1-r1.ebuild b/app-crypt/libb2/libb2-0.98.1-r1.ebuild
index 45bc705a0a3..43b3f7b8031 100644
--- a/app-crypt/libb2/libb2-0.98.1-r1.ebuild
+++ b/app-crypt/libb2/libb2-0.98.1-r1.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://github.com/BLAKE2/libb2/archive/${GITHASH}.tar.gz -> ${P}.tar.g
LICENSE="CC0-1.0"
SLOT="0"
-KEYWORDS="alpha amd64 arm arm64 hppa ia64 ~mips ppc ppc64 ~riscv sparc x86 ~x64-cygwin ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="alpha amd64 arm arm64 hppa ia64 m68k ~mips ppc ppc64 ~riscv sparc x86 ~x64-cygwin ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
IUSE="static-libs native-cflags openmp"
DEPEND="
next reply other threads:[~2019-09-26 20:09 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 20:09 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-25 9:17 [gentoo-commits] repo/gentoo:master commit in: app-crypt/libb2/ Fabian Groffen
2023-09-09 13:17 David Seifert
2023-05-29 20:18 Sam James
2023-05-28 19:06 Arthur Zamarin
2023-05-27 11:08 Arthur Zamarin
2023-05-27 10:30 Sam James
2023-05-26 20:06 Arthur Zamarin
2023-05-26 7:15 Sam James
2023-05-25 22:30 Sam James
2023-05-25 22:04 Sam James
2022-05-14 21:30 David Seifert
2021-01-06 12:55 Fabian Groffen
2020-01-12 14:34 Fabian Groffen
2019-11-22 9:37 Mikle Kolyada
2019-11-22 9:37 Mikle Kolyada
2019-11-22 9:37 Mikle Kolyada
2019-11-14 11:55 Agostino Sarubbo
2019-11-12 15:08 Agostino Sarubbo
2019-11-12 7:25 Sergei Trofimovich
2019-11-08 8:35 Mikle Kolyada
2019-11-06 20:11 Sergei Trofimovich
2019-11-05 9:27 Agostino Sarubbo
2019-11-05 8:24 Agostino Sarubbo
2019-11-05 0:54 Aaron Bauman
2019-10-27 17:11 Michał Górny
2019-09-26 20:09 Mikle Kolyada
2019-09-26 20:09 Mikle Kolyada
2019-09-26 20:09 Mikle Kolyada
2019-09-21 5:20 Matt Turner
2019-09-17 9:16 Jeroen Roovers
2019-09-17 1:13 Aaron Bauman
2019-09-16 22:03 Sergei Trofimovich
2019-09-16 22:02 Sergei Trofimovich
2019-09-16 22:00 Sergei Trofimovich
2019-09-16 7:56 Agostino Sarubbo
2019-09-16 7:55 Agostino Sarubbo
2019-09-15 9:36 Mikle Kolyada
2019-07-29 8:57 Mikle Kolyada
2019-07-29 8:57 Mikle Kolyada
2019-07-22 17:26 Aaron Bauman
2019-06-15 9:26 Sergei Trofimovich
2019-06-11 20:32 Göktürk Yüksek
2019-06-11 17:32 Ben Kohler
2019-06-10 19:50 Thomas Deutschmann
2019-06-09 19:22 Sergei Trofimovich
2019-06-08 0:26 Matt Turner
2019-06-06 19:03 Fabian Groffen
2019-06-06 16:34 Fabian Groffen
2019-06-06 8:49 Michael Haubenwallner
2019-06-05 14:20 Michael Haubenwallner
2019-06-05 9:31 Fabian Groffen
2019-06-05 8:39 Fabian Groffen
2019-06-05 8:37 Fabian Groffen
2019-06-05 8:37 Fabian Groffen
2019-06-05 8:35 Michael Haubenwallner
2019-06-05 8:03 Jeroen Roovers
2019-05-17 20:49 Fabian Groffen
2018-02-28 20:30 Fabian Groffen
2018-02-28 18:59 Fabian Groffen
2017-11-27 13:55 Fabian Groffen
2017-11-27 12:02 Fabian Groffen
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=1569528530.a24aa61ffad81296cf0e6d10d56ffa0ff333d019.zlogene@gentoo \
--to=zlogene@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