From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/docbook-sgml-dtd/
Date: Fri, 28 Sep 2018 08:32:38 +0000 (UTC) [thread overview]
Message-ID: <1538123544.135dee7731255d6e6307cf9143f4cc763d925772.zlogene@gentoo> (raw)
commit: 135dee7731255d6e6307cf9143f4cc763d925772
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Fri Sep 28 08:32:24 2018 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Fri Sep 28 08:32:24 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=135dee77
app-text/docbook-sgml-dtd: amd64 stable wrt bug #666826
Package-Manager: Portage-2.3.49, Repoman-2.3.10
app-text/docbook-sgml-dtd/docbook-sgml-dtd-4.5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-text/docbook-sgml-dtd/docbook-sgml-dtd-4.5.ebuild b/app-text/docbook-sgml-dtd/docbook-sgml-dtd-4.5.ebuild
index db0e23ff07c..d3912738df8 100644
--- a/app-text/docbook-sgml-dtd/docbook-sgml-dtd-4.5.ebuild
+++ b/app-text/docbook-sgml-dtd/docbook-sgml-dtd-4.5.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://www.docbook.org/sgml/${PV}/${MY_P}.zip"
LICENSE="docbook"
SLOT="4.5"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos ~sparc-solaris ~x64-solaris"
+KEYWORDS="~alpha amd64 ~arm ~arm64 hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos ~sparc-solaris ~x64-solaris"
IUSE=""
DEPEND=">=app-arch/unzip-5.41"
next reply other threads:[~2018-09-28 8:32 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 8:32 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-19 4:50 [gentoo-commits] repo/gentoo:master commit in: app-text/docbook-sgml-dtd/ WANG Xuerui
2022-11-19 4:50 WANG Xuerui
2022-08-27 10:11 WANG Xuerui
2022-08-27 10:11 WANG Xuerui
2022-08-27 10:11 WANG Xuerui
2022-08-27 10:11 WANG Xuerui
2022-05-14 7:04 WANG Xuerui
2021-12-12 8:33 Michał Górny
2021-08-28 8:22 Fabian Groffen
2021-08-27 15:36 Fabian Groffen
2021-07-26 8:07 Yixun Lan
2021-07-19 23:14 Marek Szuba
2021-02-08 18:59 Fabian Groffen
2021-02-08 18:59 Fabian Groffen
2020-12-20 11:52 Mikle Kolyada
2019-11-08 21:13 Michał Górny
2019-11-08 21:13 Michał Górny
2019-10-16 20:46 Sergei Trofimovich
2019-10-16 20:46 Sergei Trofimovich
2019-10-16 20:46 Sergei Trofimovich
2019-10-16 20:46 Sergei Trofimovich
2019-10-16 20:46 Sergei Trofimovich
2019-10-16 20:46 Sergei Trofimovich
2019-10-16 20:46 Sergei Trofimovich
2019-10-16 20:46 Sergei Trofimovich
2019-10-16 12:42 Aaron Bauman
2019-10-14 11:31 Agostino Sarubbo
2019-10-14 11:25 Agostino Sarubbo
2019-10-14 11:07 Agostino Sarubbo
2019-10-12 8:55 Mikle Kolyada
2019-10-12 8:55 Mikle Kolyada
2019-10-12 8:55 Mikle Kolyada
2019-09-17 7:12 Michał Górny
2019-09-11 17:58 Michał Górny
2018-11-27 12:03 Mart Raudsepp
2018-10-12 16:16 Mikle Kolyada
2018-10-11 18:49 Tobias Klausmann
2018-10-09 9:32 Mikle Kolyada
2018-10-06 19:46 Matt Turner
2018-10-06 19:46 Matt Turner
2018-09-30 21:38 Sergei Trofimovich
2018-09-26 6:22 Sergei Trofimovich
2018-09-24 21:26 Sergei Trofimovich
2018-04-14 18:45 Pacho Ramos
2017-09-05 17:38 Jonas Stein
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=1538123544.135dee7731255d6e6307cf9143f4cc763d925772.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