From: "Kent Fredric" <kentnl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: xfce-extra/xfce4-notes-plugin/
Date: Tue, 23 Jul 2019 14:11:00 +0000 (UTC) [thread overview]
Message-ID: <1563890163.ae35611d12ee4e271f392d36171c21e3a255610a.kentnl@gentoo> (raw)
commit: ae35611d12ee4e271f392d36171c21e3a255610a
Author: Kent Fredric <kentnl <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 23 13:56:03 2019 +0000
Commit: Kent Fredric <kentnl <AT> gentoo <DOT> org>
CommitDate: Tue Jul 23 13:56:03 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ae35611d
xfce-extra/xfce4-notes-plugin: Drop ~x86-fbsd due to bug #665088
Judicious dropping of keywords due to inactivity in bug #665088
This percolates due to keyword inconsistencies in:
dev-perl/Log-Agent, dev-perl/glib-perl, xfce-base/xfconf
Bug: https://bugs.gentoo.org/665088
Package-Manager: Portage-2.3.66, Repoman-2.3.16
RepoMan-Options: --include-arches="x86-fbsd"
Signed-off-by: Kent Fredric <kentnl <AT> gentoo.org>
| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--git a/xfce-extra/xfce4-notes-plugin/xfce4-notes-plugin-1.8.1-r1.ebuild b/xfce-extra/xfce4-notes-plugin/xfce4-notes-plugin-1.8.1-r1.ebuild
index 26d796e8bbe..f3f229e31d1 100644
--- a/xfce-extra/xfce4-notes-plugin/xfce4-notes-plugin-1.8.1-r1.ebuild
+++ b/xfce-extra/xfce4-notes-plugin/xfce4-notes-plugin-1.8.1-r1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://archive.xfce.org/src/panel-plugins/${PN}/$(ver_cut 1-2)/${P}.ta
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="alpha amd64 arm ~hppa ~ia64 ppc ppc64 ~sparc x86 ~x86-fbsd ~amd64-linux ~x86-linux"
+KEYWORDS="alpha amd64 arm ~hppa ~ia64 ppc ppc64 ~sparc x86 ~amd64-linux ~x86-linux"
IUSE=""
RDEPEND=">=dev-libs/glib-2.24:2
next reply other threads:[~2019-07-23 14:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 14:11 Kent Fredric [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-18 0:55 [gentoo-commits] repo/gentoo:master commit in: xfce-extra/xfce4-notes-plugin/ Sam James
2025-03-18 0:55 Sam James
2025-03-01 8:31 Michał Górny
2025-02-02 3:22 Michał Górny
2025-01-25 10:05 Arthur Zamarin
2024-12-29 14:24 Michał Górny
2024-02-24 8:49 Michał Górny
2024-02-24 2:44 Ionen Wolkens
2024-02-24 2:44 Ionen Wolkens
2024-02-09 1:04 Sam James
2024-02-09 1:04 Sam James
2024-02-08 15:28 Michał Górny
2024-01-13 20:15 Michał Górny
2023-06-11 16:18 Michał Górny
2023-06-11 15:04 Sam James
2023-06-11 15:04 Sam James
2023-06-11 15:04 Sam James
2023-06-11 13:46 Sam James
2023-03-18 15:03 Michał Górny
2021-11-19 6:24 Yixun Lan
2021-02-18 22:08 Sam James
2021-02-18 7:26 Sam James
2021-02-08 6:11 Sam James
2021-02-08 6:05 Sam James
2021-01-18 23:34 Michał Górny
2019-12-06 14:20 Michał Górny
2019-10-20 11:07 Michał Górny
2019-10-20 9:06 Michał Górny
2019-08-22 12:31 Michał Górny
2019-08-22 11:15 Michał Górny
2019-05-18 11:11 Michał Górny
2019-05-02 22:00 Michał Górny
2019-05-02 21:34 Mikle Kolyada
2019-05-02 21:34 Mikle Kolyada
2019-04-28 13:03 Sergei Trofimovich
2019-04-28 7:42 Sergei Trofimovich
2019-04-21 19:19 Mikle Kolyada
2019-04-21 19:19 Mikle Kolyada
2019-04-10 8:19 Michał Górny
2019-04-09 14:33 Michał Górny
2018-04-08 9:04 Michał Górny
2017-01-30 7:37 Fabian Groffen
2016-02-19 19:42 Michał Górny
2015-10-17 18:32 Mikle Kolyada
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=1563890163.ae35611d12ee4e271f392d36171c21e3a255610a.kentnl@gentoo \
--to=kentnl@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