From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-p2p/amule/
Date: Sat, 6 Oct 2018 19:12:29 +0000 (UTC) [thread overview]
Message-ID: <1538853142.1cc6adb7d4090a41f3bf8ad7452ba164fba672c4.slyfox@gentoo> (raw)
commit: 1cc6adb7d4090a41f3bf8ad7452ba164fba672c4
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 6 19:11:24 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Oct 6 19:12:22 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1cc6adb7
net-p2p/amule: stable 2.3.2-r2 for ppc, bug #661698
Tested-by: ernsteiswuerfel
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
Package-Manager: Portage-2.3.50, Repoman-2.3.11
RepoMan-Options: --include-arches="ppc"
net-p2p/amule/amule-2.3.2-r2.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net-p2p/amule/amule-2.3.2-r2.ebuild b/net-p2p/amule/amule-2.3.2-r2.ebuild
index ac7f657aa11..3fc08e6fc94 100644
--- a/net-p2p/amule/amule-2.3.2-r2.ebuild
+++ b/net-p2p/amule/amule-2.3.2-r2.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -15,7 +15,7 @@ SRC_URI="mirror://sourceforge/${PN}/${MY_P}.tar.xz"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="alpha amd64 ~arm ~ppc ppc64 ~sparc x86"
+KEYWORDS="alpha amd64 ~arm ppc ppc64 ~sparc x86"
IUSE="daemon debug geoip nls remote stats upnp +X"
COMMON_DEPEND="
next reply other threads:[~2018-10-06 19:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 19:12 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-07 12:39 [gentoo-commits] repo/gentoo:master commit in: net-p2p/amule/ Yixun Lan
2024-07-13 11:06 Yixun Lan
2024-07-05 17:49 Pacho Ramos
2024-04-12 8:12 Joonas Niilola
2024-04-11 17:40 Arthur Zamarin
2024-04-11 16:57 Arthur Zamarin
2023-12-22 6:46 Sam James
2023-12-20 6:23 Arthur Zamarin
2023-12-20 6:23 Arthur Zamarin
2023-12-20 6:23 Arthur Zamarin
2023-12-20 3:44 Sam James
2023-06-27 0:02 Yixun Lan
2023-06-26 14:43 Sam James
2022-04-28 15:05 Jakov Smolić
2021-06-20 7:52 Agostino Sarubbo
2021-06-20 7:51 Agostino Sarubbo
2021-06-20 7:50 Agostino Sarubbo
2021-06-20 7:50 Agostino Sarubbo
2021-02-22 14:47 Joonas Niilola
2020-06-15 15:16 Agostino Sarubbo
2020-06-14 20:19 Sergei Trofimovich
2020-06-14 20:08 Sergei Trofimovich
2020-04-30 12:00 Joonas Niilola
2020-04-30 12:00 Joonas Niilola
2020-02-20 13:27 Joonas Niilola
2020-02-20 13:27 Joonas Niilola
2020-01-17 6:23 Joonas Niilola
2018-07-29 10:35 Sergei Trofimovich
2018-07-23 13:10 Tobias Klausmann
2018-07-21 17:50 Mikle Kolyada
2018-06-22 22:17 Patrice Clement
2018-06-22 22:17 Patrice Clement
2018-06-22 22:17 Patrice Clement
2018-06-22 22:17 Patrice Clement
2017-06-13 12:31 Agostino Sarubbo
2017-06-08 10:16 Agostino Sarubbo
2017-04-05 14:22 Michael Weber
2017-03-27 2:19 Michael Orlitzky
2017-03-27 2:19 Michael Orlitzky
2016-10-01 14:19 Pacho Ramos
2016-05-03 17:35 Austin English
2016-01-22 10:43 Patrice Clement
2016-01-22 10:43 Patrice Clement
2016-01-22 10:43 Patrice Clement
2015-11-07 12:57 Pacho Ramos
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=1538853142.1cc6adb7d4090a41f3bf8ad7452ba164fba672c4.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