From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/build-docbook-catalog/
Date: Sun, 26 Dec 2021 03:58:25 +0000 (UTC) [thread overview]
Message-ID: <1640490897.a1cd9073d92a4e8ed15022eab5d97916794ab0cc.sam@gentoo> (raw)
commit: a1cd9073d92a4e8ed15022eab5d97916794ab0cc
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 26 03:54:54 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Dec 26 03:54:57 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a1cd9073
app-text/build-docbook-catalog: destabilize 2.1
We want to stabilise a version of Portage which
warns on missing /run before stabling this.
Bug: https://bugs.gentoo.org/816747
Bug: https://bugs.gentoo.org/829468
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-text/build-docbook-catalog/build-docbook-catalog-2.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-text/build-docbook-catalog/build-docbook-catalog-2.1.ebuild b/app-text/build-docbook-catalog/build-docbook-catalog-2.1.ebuild
index 76fcdf03d9a2..3deb1d96043e 100644
--- a/app-text/build-docbook-catalog/build-docbook-catalog-2.1.ebuild
+++ b/app-text/build-docbook-catalog/build-docbook-catalog-2.1.ebuild
@@ -9,7 +9,7 @@ SRC_URI="https://gitweb.gentoo.org/proj/build-docbook-catalog.git/snapshot/${P}.
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~x64-cygwin ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~x64-cygwin ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
RDEPEND="
dev-libs/libxml2
next reply other threads:[~2021-12-26 3:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 3:58 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-01 3:29 [gentoo-commits] repo/gentoo:master commit in: app-text/build-docbook-catalog/ Sam James
2023-04-25 3:50 Sam James
2022-06-29 14:13 Guilherme Amadio
2022-06-13 7:07 Agostino Sarubbo
2022-04-29 8:19 Sam James
2022-04-29 8:14 Sam James
2022-01-17 23:39 Andreas K. Hüttel
2022-01-17 23:39 Andreas K. Hüttel
2021-12-26 23:38 Sam James
2021-12-26 3:58 Sam James
2021-12-22 22:40 Sam James
2021-12-17 18:30 Jakov Smolić
2021-12-17 18:30 Jakov Smolić
2021-12-17 16:50 Arthur Zamarin
2021-12-17 14:54 Arthur Zamarin
2021-12-17 14:51 Arthur Zamarin
2021-12-17 14:49 Arthur Zamarin
2021-12-17 14:44 Arthur Zamarin
2021-10-11 1:59 Sam James
2021-10-09 6:39 罗百科
2021-10-08 12:25 Mike Frysinger
2021-10-07 2:48 Sam James
2021-10-03 4:06 Mike Frysinger
2021-03-22 5:45 Mike Frysinger
2021-01-24 17:26 Sam James
2020-12-27 14:01 Fabian Groffen
2019-05-04 14:43 Andreas K. Hüttel
2018-06-06 17:58 Mike Frysinger
2018-05-21 9:51 Mikle Kolyada
2018-05-21 9:51 Mikle Kolyada
2018-05-03 7:06 Mart Raudsepp
2018-04-28 11:36 Mikle Kolyada
2018-04-20 21:27 Sergei Trofimovich
2018-04-01 18:24 Aaron Bauman
2018-04-01 11:09 Tobias Klausmann
2018-03-31 10:05 Sergei Trofimovich
2018-03-30 12:08 Sergei Trofimovich
2016-05-23 16:13 Michael Haubenwallner
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=1640490897.a1cd9073d92a4e8ed15022eab5d97916794ab0cc.sam@gentoo \
--to=sam@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