From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-tex/biber/
Date: Wed, 2 Jan 2019 10:10:23 +0000 (UTC) [thread overview]
Message-ID: <1546423795.03c066d0a55b8d0060dd6c993c4cd69e42eb68ae.zlogene@gentoo> (raw)
commit: 03c066d0a55b8d0060dd6c993c4cd69e42eb68ae
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 2 10:09:55 2019 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Wed Jan 2 10:09:55 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=03c066d0
dev-tex/biber: amd64 stable wrt bug #626616
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
dev-tex/biber/biber-2.7.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-tex/biber/biber-2.7.ebuild b/dev-tex/biber/biber-2.7.ebuild
index f74084ea47c..5a2aaf1c1a1 100644
--- a/dev-tex/biber/biber-2.7.ebuild
+++ b/dev-tex/biber/biber-2.7.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/plk/biber/archive/v${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="Artistic-2"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~x86"
+KEYWORDS="amd64 ~arm ~x86"
IUSE="test"
RDEPEND=">=dev-lang/perl-5.24
next reply other threads:[~2019-01-02 10:10 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 10:10 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-11 2:40 [gentoo-commits] repo/gentoo:master commit in: dev-tex/biber/ Ionen Wolkens
2024-06-23 17:47 Arthur Zamarin
2024-06-20 15:07 Ionen Wolkens
2024-06-15 6:18 Viorel Munteanu
2024-06-14 18:05 Sam James
2024-06-14 14:42 Arthur Zamarin
2024-05-28 18:23 Arthur Zamarin
2024-05-26 6:06 Arthur Zamarin
2024-04-12 16:42 Florian Schmaus
2024-04-12 16:42 Florian Schmaus
2022-08-24 3:16 Sam James
2021-10-26 1:21 Yixun Lan
2021-06-10 8:13 Joonas Niilola
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-19 19:36 Sam James
2020-05-04 14:11 Joonas Niilola
2020-01-19 17:31 Mikle Kolyada
2019-09-27 19:19 Mikle Kolyada
2019-05-11 20:46 Andreas K. Hüttel
2019-02-10 23:11 Patrice Clement
2019-02-10 23:11 Patrice Clement
2018-08-20 7:15 Mikle Kolyada
2018-08-20 1:32 Mikle Kolyada
2018-08-08 16:34 Michał Górny
2018-08-08 16:34 Michał Górny
2018-07-22 8:27 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-17 18:55 David Seifert
2017-11-12 9:15 Jonas Stein
2017-11-11 16:49 Jonas Stein
2017-06-15 16:27 Markus Meier
2017-05-15 9:09 Michał Górny
2017-05-07 11:05 Mikle Kolyada
2017-05-02 12:23 Manuel Rüger
2017-03-16 19:45 Manuel Rüger
2016-09-26 19:51 Manuel Rüger
2016-09-26 19:49 Manuel Rüger
2016-09-26 19:44 Manuel Rüger
2016-08-02 11:54 Kent Fredric
2016-03-13 12:51 Manuel Rüger
2016-03-12 1:58 Jason Donenfeld
2016-01-24 12:37 Andreas Hüttel
2016-01-24 12:37 Andreas Hüttel
2016-01-23 18:17 Manuel Rüger
2016-01-23 18:17 Manuel Rüger
2015-10-28 21:09 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=1546423795.03c066d0a55b8d0060dd6c993c4cd69e42eb68ae.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