From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/courier-unicode/
Date: Sat, 24 Oct 2020 17:53:32 +0000 (UTC) [thread overview]
Message-ID: <1603562004.0017dfbadc6932436521e44e3965f537387420c9.slyfox@gentoo> (raw)
commit: 0017dfbadc6932436521e44e3965f537387420c9
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Sat Oct 24 17:17:59 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Oct 24 17:53:24 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0017dfba
net-libs/courier-unicode: stable 2.1-r1 for sparc, bug #750443
Package-Manager: Portage-3.0.8, Repoman-3.0.2
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
net-libs/courier-unicode/courier-unicode-2.1-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-libs/courier-unicode/courier-unicode-2.1-r1.ebuild b/net-libs/courier-unicode/courier-unicode-2.1-r1.ebuild
index 793cf25b398..7a8b48ef55c 100644
--- a/net-libs/courier-unicode/courier-unicode-2.1-r1.ebuild
+++ b/net-libs/courier-unicode/courier-unicode-2.1-r1.ebuild
@@ -8,7 +8,7 @@ HOMEPAGE="https://www.courier-mta.org/"
SRC_URI="mirror://sourceforge/courier/${P}.tar.bz2"
LICENSE="GPL-3"
SLOT="0"
-KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 sparc ~x86"
IUSE=""
src_configure() {
next reply other threads:[~2020-10-24 17:53 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 17:53 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-20 4:13 [gentoo-commits] repo/gentoo:master commit in: net-libs/courier-unicode/ Sam James
2025-03-20 4:13 Sam James
2024-11-13 12:42 Sam James
2024-11-11 8:08 Arthur Zamarin
2024-11-11 0:07 Sam James
2024-11-10 20:01 Sam James
2024-11-10 9:58 Sam James
2024-09-05 9:47 Hanno Böck
2024-07-21 14:59 Hanno Böck
2024-05-24 2:46 Ionen Wolkens
2024-05-24 2:46 Ionen Wolkens
2024-04-28 19:11 Ionen Wolkens
2024-03-22 18:25 Sam James
2024-03-22 7:12 Sam James
2024-02-18 18:37 Hanno Böck
2024-02-18 16:04 Hanno Böck
2024-01-15 3:32 Ionen Wolkens
2023-12-14 4:15 Sam James
2023-09-21 20:11 Sam James
2023-07-19 9:33 Sam James
2023-07-18 19:24 Sam James
2023-02-21 14:10 Hanno Böck
2022-03-03 21:22 David Seifert
2021-08-16 2:24 Sam James
2021-08-07 23:41 Sam James
2021-08-06 20:44 Sam James
2021-08-06 20:44 Sam James
2021-08-06 20:44 Sam James
2021-08-06 13:35 Sam James
2021-08-06 13:35 Sam James
2021-07-05 13:25 Marek Szuba
2021-05-16 12:45 Sam James
2021-03-31 13:03 Hanno Böck
2021-03-06 9:55 Hanno Böck
2020-11-23 16:39 Sergei Trofimovich
2020-11-18 6:55 Agostino Sarubbo
2020-11-17 19:05 Agostino Sarubbo
2020-11-08 13:09 Sam James
2020-11-06 20:10 Sam James
2020-10-22 12:10 Sam James
2020-09-10 16:17 Hanno Böck
2020-09-10 16:15 Hanno Böck
2019-07-22 16:49 Aaron Bauman
2019-05-06 15:25 Tobias Klausmann
2019-03-17 10:29 Sergei Trofimovich
2019-03-13 22:36 Sergei Trofimovich
2019-03-10 14:41 Mikle Kolyada
2019-03-10 14:41 Mikle Kolyada
2019-03-02 20:02 Sergei Trofimovich
2019-03-02 16:23 Mikle Kolyada
2019-03-01 1:14 Thomas Deutschmann
2019-02-28 21:25 Sergei Trofimovich
2019-02-28 15:08 Mikle Kolyada
2019-02-23 11:49 Sergei Trofimovich
2018-12-19 11:27 Hanno Boeck
2018-12-18 9:27 Hanno Boeck
2018-12-18 9:15 Hanno Boeck
2018-08-18 5:11 Mikle Kolyada
2018-07-15 13:20 Mart Raudsepp
2018-06-09 19:57 Mikle Kolyada
2017-07-03 14:10 Eray Aslan
2017-02-24 23:14 Michael Weber
2015-11-19 11:52 Eray Aslan
2015-11-18 6:51 Eray Aslan
2015-11-18 6:51 Eray Aslan
2015-09-08 10:04 Joshua Kinard
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=1603562004.0017dfbadc6932436521e44e3965f537387420c9.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