From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-tex/biblatex/
Date: Sun, 23 Jun 2024 17:47:34 +0000 (UTC) [thread overview]
Message-ID: <1719164776.3bff24c46d71b1b1a1753ccbdfc54e385de4820e.arthurzam@gentoo> (raw)
commit: 3bff24c46d71b1b1a1753ccbdfc54e385de4820e
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 23 17:46:16 2024 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sun Jun 23 17:46:16 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3bff24c4
dev-tex/biblatex: Stabilize 3.19 sparc, #934277
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-tex/biblatex/biblatex-3.19.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-tex/biblatex/biblatex-3.19.ebuild b/dev-tex/biblatex/biblatex-3.19.ebuild
index 0930ae1e0725..fd58302e482e 100644
--- a/dev-tex/biblatex/biblatex-3.19.ebuild
+++ b/dev-tex/biblatex/biblatex-3.19.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://downloads.sourceforge.net/${PN}/${P}.tds.tgz"
LICENSE="LPPL-1.3"
SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 hppa ~loong ~mips ppc ppc64 ~riscv ~s390 ~sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~loong ~mips ppc ppc64 ~riscv ~s390 sparc x86"
IUSE="+biber doc examples"
DEPEND="
next reply other threads:[~2024-06-23 17:47 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 17:47 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-26 14:43 [gentoo-commits] repo/gentoo:master commit in: dev-tex/biblatex/ Florian Schmaus
2025-03-10 7:53 Florian Schmaus
2025-01-15 16:19 Sam James
2025-01-15 11:47 Sam James
2025-01-15 11:44 Sam James
2025-01-15 11:44 Sam James
2025-01-15 11:44 Sam James
2024-07-11 2:40 Ionen Wolkens
2024-06-14 18:05 Sam James
2024-06-14 14:42 Arthur Zamarin
2024-05-26 6:06 Arthur Zamarin
2021-10-26 1:21 Yixun Lan
2021-05-04 22:24 Sam James
2021-05-02 22:06 Sergei Trofimovich
2021-03-09 22:03 Andreas K. Hüttel
2020-12-21 20:08 Sam James
2020-12-19 19:36 Sam James
2020-05-04 14:11 Joonas Niilola
2020-01-19 16:37 Mikle Kolyada
2019-09-27 19:19 Mikle Kolyada
2019-07-26 12:02 Mikle Kolyada
2019-02-10 23:11 Patrice Clement
2019-02-10 23:11 Patrice Clement
2019-01-02 10:10 Mikle Kolyada
2018-08-08 16:34 Michał Górny
2018-08-08 16:34 Michał Górny
2018-08-08 16:34 Michał Górny
2018-07-21 12:25 Alexis Ballier
2018-07-21 12:25 Alexis Ballier
2018-04-02 18:06 Mart Raudsepp
2018-02-04 23:41 Patrice Clement
2018-01-08 23:57 Thomas Deutschmann
2018-01-08 23:57 Thomas Deutschmann
2017-11-30 14:47 Patrice Clement
2017-11-30 14:47 Patrice Clement
2017-11-11 16:49 Jonas Stein
2017-06-15 16:27 Markus Meier
2017-06-12 9:40 Michał Górny
2017-05-30 8:02 Alexis Ballier
2017-05-15 9:09 Michał Górny
2017-05-07 11:05 Mikle Kolyada
2017-04-28 21:23 Manuel Rüger
2017-03-16 19:45 Manuel Rüger
2017-03-16 19:45 Manuel Rüger
2016-09-26 19:52 Manuel Rüger
2016-09-26 19:51 Manuel Rüger
2016-05-24 15:20 Amy Winston
2016-05-20 19:57 Manuel Rüger
2016-03-13 12:51 Manuel Rüger
2016-03-03 23:13 Manuel Rüger
2016-01-23 18:17 Manuel Rüger
2015-12-22 20:34 Manuel Rüger
2015-10-28 21:11 Manuel Rüger
2015-10-28 18:38 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=1719164776.3bff24c46d71b1b1a1753ccbdfc54e385de4820e.arthurzam@gentoo \
--to=arthurzam@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