From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-dicts/myspell-eo/
Date: Mon, 6 Nov 2017 18:06:07 +0000 (UTC) [thread overview]
Message-ID: <1509991254.9f1748cf5e0b9aef59975b651cc1d01ba86e545b.mjo@gentoo> (raw)
commit: 9f1748cf5e0b9aef59975b651cc1d01ba86e545b
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 6 18:00:54 2017 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Mon Nov 6 18:00:54 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9f1748cf
app-dicts/myspell-eo: stabilize myspell-eo-1.0-r1.ebuild everywhere.
I've tested this myself on amd64, and since it contains only two data
files, have stabilized it everywhere under our ALLARCHES policy.
Bug: https://bugs.gentoo.org/626172
Package-Manager: Portage-2.3.8, Repoman-2.3.3
app-dicts/myspell-eo/myspell-eo-1.0-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-dicts/myspell-eo/myspell-eo-1.0-r1.ebuild b/app-dicts/myspell-eo/myspell-eo-1.0-r1.ebuild
index 35b87420abf..e05f6123750 100644
--- a/app-dicts/myspell-eo/myspell-eo-1.0-r1.ebuild
+++ b/app-dicts/myspell-eo/myspell-eo-1.0-r1.ebuild
@@ -22,7 +22,7 @@ SRC_URI="mirror://sourceforge/aoo-extensions/3377/1/${PV}-dev.oxt -> ${P}.oxt"
LICENSE="GPL-2 LGPL-3 MPL-1.1"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sh ~sparc ~x86 ~amd64-fbsd ~x86-fbsd"
+KEYWORDS="alpha amd64 arm ~arm64 hppa ia64 ~mips ppc ppc64 ~sh sparc x86 ~amd64-fbsd ~x86-fbsd"
IUSE=""
src_prepare() {
next reply other threads:[~2017-11-06 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 18:06 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-05 6:57 [gentoo-commits] repo/gentoo:master commit in: app-dicts/myspell-eo/ Agostino Sarubbo
2019-04-23 21:39 Aaron Bauman
2017-11-06 18:06 Michael Orlitzky
2017-07-25 21:18 Michael Orlitzky
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=1509991254.9f1748cf5e0b9aef59975b651cc1d01ba86e545b.mjo@gentoo \
--to=mjo@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