From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-tex/latexmk/
Date: Thu, 27 Jun 2019 07:23:48 +0000 (UTC) [thread overview]
Message-ID: <1561620221.b0254683ad9c16988cb0a68a1dabd340941be4b1.slyfox@gentoo> (raw)
commit: b0254683ad9c16988cb0a68a1dabd340941be4b1
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 27 07:06:17 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Thu Jun 27 07:23:41 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b0254683
dev-tex/latexmk: stable 456 for ia64, bug #688590
Package-Manager: Portage-2.3.67, Repoman-2.3.16
RepoMan-Options: --include-arches="ia64"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-tex/latexmk/latexmk-456.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-tex/latexmk/latexmk-456.ebuild b/dev-tex/latexmk/latexmk-456.ebuild
index 09240ef8c36..f97c9eb9c45 100644
--- a/dev-tex/latexmk/latexmk-456.ebuild
+++ b/dev-tex/latexmk/latexmk-456.ebuild
@@ -11,7 +11,7 @@ SRC_URI="http://www.phys.psu.edu/~collins/software/latexmk/${P}.zip"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~ppc-macos ~x64-macos ~x86-macos"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~ppc-macos ~x64-macos ~x86-macos"
RDEPEND="virtual/latex-base
dev-lang/perl"
next reply other threads:[~2019-06-27 7:23 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 7:23 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-21 4:23 [gentoo-commits] repo/gentoo:master commit in: dev-tex/latexmk/ Arthur Zamarin
2024-06-14 17:45 Sam James
2024-06-14 17:29 Sam James
2024-06-14 17:21 Sam James
2024-06-14 17:20 Sam James
2024-06-14 17:20 Sam James
2024-06-14 14:42 Arthur Zamarin
2023-04-28 17:21 Sam James
2023-04-28 16:22 Arthur Zamarin
2023-04-28 15:24 Arthur Zamarin
2023-04-28 15:13 Arthur Zamarin
2023-04-28 15:07 Arthur Zamarin
2023-04-28 14:50 Arthur Zamarin
2023-04-28 14:41 Arthur Zamarin
2023-04-26 7:07 Florian Schmaus
2022-12-08 7:38 WANG Xuerui
2022-04-17 18:32 Sam James
2021-03-15 6:32 Sam James
2021-03-15 2:26 Sam James
2021-03-15 1:40 Thomas Deutschmann
2021-03-15 0:52 Sam James
2021-03-14 22:11 Sam James
2021-03-14 22:11 Sam James
2021-03-14 13:48 Sergei Trofimovich
2021-02-11 15:54 Aaron W. Swenson
2021-01-06 22:35 Fabian Groffen
2020-04-25 11:35 Mikle Kolyada
2020-04-25 9:49 Mikle Kolyada
2019-12-10 0:48 Aaron Bauman
2019-12-10 0:48 Aaron Bauman
2019-11-30 21:45 Sergei Trofimovich
2019-11-20 11:48 Agostino Sarubbo
2019-07-28 20:14 Mikle Kolyada
2019-07-23 0:45 Aaron Bauman
2019-06-28 11:42 Agostino Sarubbo
2019-06-27 7:31 Sergei Trofimovich
2019-06-27 7:26 Sergei Trofimovich
2019-06-26 6:50 Agostino Sarubbo
2019-06-25 7:04 Agostino Sarubbo
2019-06-24 8:00 Jonas Stein
2018-08-05 15:07 Alexis Ballier
2017-08-26 12:32 Alexis Ballier
2017-06-17 14:41 Alexis Ballier
2017-01-31 8:59 Alexis Ballier
2016-12-01 17:36 Alexis Ballier
2016-05-23 11:13 Alexis Ballier
2016-02-28 12:10 Manuel Rüger
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=1561620221.b0254683ad9c16988cb0a68a1dabd340941be4b1.slyfox@gentoo \
--to=slyfox@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