From: "Aaron Bauman" <bman@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/radvd/
Date: Sun, 1 Sep 2019 21:32:04 +0000 (UTC) [thread overview]
Message-ID: <1567373515.49294a52f38fc05fd088581db779f438a8bde790.bman@gentoo> (raw)
commit: 49294a52f38fc05fd088581db779f438a8bde790
Author: Aaron Bauman <bman <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 1 21:31:44 2019 +0000
Commit: Aaron Bauman <bman <AT> gentoo <DOT> org>
CommitDate: Sun Sep 1 21:31:55 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=49294a52
net-misc/radvd: arm64 stable (bug #693080)
Signed-off-by: Aaron Bauman <bman <AT> gentoo.org>
Package-Manager: Portage-2.3.74, Repoman-2.3.17
RepoMan-Options: --include-arches="arm64"
net-misc/radvd/radvd-2.18.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-misc/radvd/radvd-2.18.ebuild b/net-misc/radvd/radvd-2.18.ebuild
index 21c73f6c0ca..e42974c512d 100644
--- a/net-misc/radvd/radvd-2.18.ebuild
+++ b/net-misc/radvd/radvd-2.18.ebuild
@@ -11,7 +11,7 @@ SRC_URI="http://v6web.litech.org/radvd/dist/${P}.tar.gz"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 hppa ppc sparc x86 ~x86-fbsd"
+KEYWORDS="amd64 ~arm arm64 hppa ppc sparc x86 ~x86-fbsd"
IUSE="kernel_FreeBSD selinux test"
CDEPEND="dev-libs/libdaemon"
next reply other threads:[~2019-09-01 21:32 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 21:32 Aaron Bauman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-31 17:16 [gentoo-commits] repo/gentoo:master commit in: net-misc/radvd/ Robin H. Johnson
2024-12-31 6:40 Robin H. Johnson
2024-10-15 5:22 Sam James
2024-10-12 10:08 Michał Górny
2024-10-12 9:44 Michał Górny
2024-10-12 9:44 Michał Górny
2024-10-12 9:44 Michał Górny
2024-10-12 9:44 Michał Górny
2024-10-12 7:52 Michał Górny
2024-01-03 18:52 Arthur Zamarin
2023-12-06 16:01 Sam James
2023-03-15 13:50 Arthur Zamarin
2023-03-15 12:27 Arthur Zamarin
2023-03-15 12:18 Arthur Zamarin
2023-03-15 12:18 Arthur Zamarin
2023-03-15 12:18 Arthur Zamarin
2023-03-15 12:18 Arthur Zamarin
2023-02-28 15:47 Matthew Thode
2023-01-01 3:11 Sam James
2022-12-04 17:56 Arthur Zamarin
2022-12-03 12:14 Sam James
2022-12-03 12:14 Sam James
2022-12-03 12:14 Arthur Zamarin
2022-12-03 12:11 Arthur Zamarin
2022-12-03 12:11 Arthur Zamarin
2022-11-24 12:21 David Seifert
2022-09-13 14:34 Sam James
2022-09-12 19:42 Sam James
2022-07-29 4:17 Sam James
2022-04-12 21:04 Sam James
2022-01-04 3:29 Sam James
2021-09-27 22:05 Marek Szuba
2021-07-10 0:09 Conrad Kostecki
2021-07-10 0:09 Conrad Kostecki
2021-05-28 15:57 David Seifert
2021-04-27 18:09 Sam James
2021-04-27 18:09 Sam James
2021-04-27 18:02 Sam James
2021-04-27 18:01 Sam James
2021-02-22 22:40 Matthew Thode
2021-02-02 18:48 Ben Kohler
2021-02-02 16:40 Matthew Thode
2021-01-28 18:19 Matthew Thode
2020-11-27 16:28 Aaron Bauman
2020-05-06 19:58 Matthew Thode
2019-12-28 21:32 Georgy Yakovlev
2019-09-13 18:15 Mikle Kolyada
2019-08-31 12:27 Sergei Trofimovich
2019-08-30 18:39 Sergei Trofimovich
2019-08-30 13:18 Agostino Sarubbo
2019-08-30 7:57 Agostino Sarubbo
2019-03-10 18:12 Matthew Thode
2018-02-06 15:10 Thomas Deutschmann
2018-01-18 19:03 Markus Meier
2017-12-15 9:36 Jason Zaman
2017-12-09 1:36 Michael Weber
2017-11-18 9:41 Sergei Trofimovich
2017-11-18 9:21 Sergei Trofimovich
2017-11-15 23:22 Sergei Trofimovich
2017-08-19 10:11 Sergei Trofimovich
2017-07-18 4:07 Matt Thode
2017-02-01 10:02 Michael Weber
2017-02-01 10:02 Michael Weber
2016-11-13 8:43 Markus Meier
2016-10-01 14:55 Jeroen Roovers
2016-10-01 14:55 Jeroen Roovers
2016-09-27 21:58 Michael Weber
2016-07-23 19:39 Matt Thode
2016-06-06 16:15 Agostino Sarubbo
2016-05-31 19:23 Markus Meier
2016-04-23 15:36 Matt Thode
2016-04-03 19:04 Markus Meier
2016-03-26 16:39 Agostino Sarubbo
2016-02-28 6:43 Matt Thode
2016-02-23 19:56 Matt Thode
2015-10-04 15:26 Mike Gilbert
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=1567373515.49294a52f38fc05fd088581db779f438a8bde790.bman@gentoo \
--to=bman@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