From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/dvipsk/
Date: Fri, 14 Jun 2024 17:20:16 +0000 (UTC) [thread overview]
Message-ID: <1718385563.50de3b8ec4f29a61bcf9a0f214325b9872de7e9d.sam@gentoo> (raw)
commit: 50de3b8ec4f29a61bcf9a0f214325b9872de7e9d
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Jun 14 17:19:23 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jun 14 17:19:23 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=50de3b8e
app-text/dvipsk: Stabilize 2023.03.11_p66203 ppc64, #934250
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-text/dvipsk/dvipsk-2023.03.11_p66203.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-text/dvipsk/dvipsk-2023.03.11_p66203.ebuild b/app-text/dvipsk/dvipsk-2023.03.11_p66203.ebuild
index 671d8354046e..237fccd52f44 100644
--- a/app-text/dvipsk/dvipsk-2023.03.11_p66203.ebuild
+++ b/app-text/dvipsk/dvipsk-2023.03.11_p66203.ebuild
@@ -22,7 +22,7 @@ SRC_URI+=" ) "
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~mips ~ppc ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
IUSE="doc source"
DEPEND=">=dev-libs/kpathsea-6.2.1:="
next reply other threads:[~2024-06-14 17:20 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 17:20 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-15 11:47 [gentoo-commits] repo/gentoo:master commit in: app-text/dvipsk/ Sam James
2025-01-15 11:44 Sam James
2025-01-15 11:44 Sam James
2024-12-01 13:46 Sam James
2024-06-21 4:23 Arthur Zamarin
2024-06-14 17:36 Sam James
2024-06-14 17:20 Sam James
2024-06-14 17:20 Sam James
2024-06-14 14:42 Arthur Zamarin
2024-06-14 14:42 Arthur Zamarin
2023-09-13 4:13 Sam James
2023-07-07 21:53 Conrad Kostecki
2023-03-20 2:22 Sam James
2023-02-08 17:13 Sam James
2022-05-14 10:30 WANG Xuerui
2021-07-03 9:31 Mikle Kolyada
2021-06-05 11:29 Mikle Kolyada
2021-04-02 8:19 Mikle Kolyada
2020-06-04 17:57 Mikle Kolyada
2020-05-31 8:19 Sergei Trofimovich
2020-05-03 13:06 Mikle Kolyada
2020-04-17 7:57 Mikle Kolyada
2020-04-13 7:15 Mikle Kolyada
2019-10-10 18:06 Mikle Kolyada
2019-10-06 6:03 Mikle Kolyada
2019-05-30 10:55 Mikle Kolyada
2018-12-30 16:27 Mikle Kolyada
2018-12-27 19:09 Fabian Groffen
2018-04-08 15:08 Mart Raudsepp
2017-11-23 23:20 Sergei Trofimovich
2017-10-17 13:00 Sergei Trofimovich
2017-10-15 19:54 Sergei Trofimovich
2017-08-20 16:59 Thomas Deutschmann
2017-07-19 4:48 Markus Meier
2017-07-16 11:08 Tobias Klausmann
2017-07-15 16:42 Tobias Klausmann
2017-07-10 21:31 Sergei Trofimovich
2017-06-17 19:15 Sergei Trofimovich
2017-06-05 13:02 Alexis Ballier
2017-06-05 13:02 Alexis Ballier
2017-05-26 8:20 Alexis Ballier
2017-03-29 6:18 Michael Weber
2017-03-28 22:57 Michael Weber
2017-03-28 22:57 Michael Weber
2017-02-17 8:17 Michael Weber
2017-01-22 15:25 Agostino Sarubbo
2017-01-22 8:18 Tobias Klausmann
2017-01-21 21:53 Agostino Sarubbo
2017-01-21 21:41 Agostino Sarubbo
2017-01-20 10:28 Alexis Ballier
2015-12-06 12:12 Markus Meier
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=1718385563.50de3b8ec4f29a61bcf9a0f214325b9872de7e9d.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