public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kent Fredric" <kentnl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: xfce-extra/xfce4-fsguard-plugin/
Date: Tue, 23 Jul 2019 14:11:00 +0000 (UTC)	[thread overview]
Message-ID: <1563890138.fc7f06148bf0f058be0bf3ac94cadb6093f1951e.kentnl@gentoo> (raw)

commit:     fc7f06148bf0f058be0bf3ac94cadb6093f1951e
Author:     Kent Fredric <kentnl <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 23 13:55:38 2019 +0000
Commit:     Kent Fredric <kentnl <AT> gentoo <DOT> org>
CommitDate: Tue Jul 23 13:55:38 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fc7f0614

xfce-extra/xfce4-fsguard-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/libxfce4ui
  xfce-base/xfce4-panel, 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>

 xfce-extra/xfce4-fsguard-plugin/xfce4-fsguard-plugin-1.1.0.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xfce-extra/xfce4-fsguard-plugin/xfce4-fsguard-plugin-1.1.0.ebuild b/xfce-extra/xfce4-fsguard-plugin/xfce4-fsguard-plugin-1.1.0.ebuild
index 444e12a8ba9..61a72657289 100644
--- a/xfce-extra/xfce4-fsguard-plugin/xfce4-fsguard-plugin-1.1.0.ebuild
+++ b/xfce-extra/xfce4-fsguard-plugin/xfce4-fsguard-plugin-1.1.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -11,7 +11,7 @@ SRC_URI="https://archive.xfce.org/src/panel-plugins/${PN}/${PV%.*}/${P}.tar.bz2"
 
 LICENSE="GPL-3"
 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=">=xfce-base/libxfce4ui-4.12:=[gtk3(+)]


             reply	other threads:[~2019-07-23 14:11 UTC|newest]

Thread overview: 27+ 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-01  8:31 [gentoo-commits] repo/gentoo:master commit in: xfce-extra/xfce4-fsguard-plugin/ Michał Górny
2025-01-25 11:41 Michał Górny
2025-01-25 11:01 Arthur Zamarin
2023-06-11 19:19 Michał Górny
2023-06-11 18:38 Jakov Smolić
2023-06-11 15:37 Sam James
2023-06-11 13:33 Sam James
2023-04-20  2:32 Michał Górny
2022-06-19 13:36 Yixun Lan
2021-02-19  1:11 Michał Górny
2021-02-18  7:26 Sam James
2021-02-08  6:05 Sam James
2020-12-28  8:42 Michał Górny
2019-10-20 10:24 Michał Górny
2019-10-10 18:35 Mikle Kolyada
2019-10-10 18:31 Mikle Kolyada
2019-08-13 12:10 Michał Górny
2018-04-08  8:06 Jason Zaman
2018-03-25 17:27 Michał Górny
2018-03-23 19:53 Markus Meier
2018-01-06  5:05 Thomas Deutschmann
2018-01-05 11:16 Mikle Kolyada
2017-01-30  7:37 Fabian Groffen
2016-11-20 16:19 Jason Zaman
2016-07-30 19:53 Michał Górny
2016-07-30 19:53 Michał Górny

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=1563890138.fc7f06148bf0f058be0bf3ac94cadb6093f1951e.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