From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libmowgli/
Date: Sun, 11 Mar 2018 11:42:29 +0000 (UTC) [thread overview]
Message-ID: <1520768545.7100f4c6918af8e73945e9ecf04a2c230f33890f.slyfox@gentoo> (raw)
commit: 7100f4c6918af8e73945e9ecf04a2c230f33890f
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 11 11:42:07 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Mar 11 11:42:25 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7100f4c6
dev-libs/libmowgli: stable 2.1.3 for ppc, bug #639142
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc"
dev-libs/libmowgli/libmowgli-2.1.3.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-libs/libmowgli/libmowgli-2.1.3.ebuild b/dev-libs/libmowgli/libmowgli-2.1.3.ebuild
index bf373213c27..48262435f8e 100644
--- a/dev-libs/libmowgli/libmowgli-2.1.3.ebuild
+++ b/dev-libs/libmowgli/libmowgli-2.1.3.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -9,7 +9,7 @@ SRC_URI="https://github.com/atheme/libmowgli-2/archive/v${PV}.tar.gz -> ${P}.tar
LICENSE="BSD-2"
SLOT="2"
-KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos"
+KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ppc ~ppc64 ~sparc ~x86 ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos"
IUSE="libressl ssl"
RDEPEND="ssl? (
next reply other threads:[~2018-03-11 11:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 11:42 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-25 15:24 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libmowgli/ Andreas K. Hüttel
2022-02-06 7:40 Sam James
2021-11-02 11:00 Sam James
2021-10-31 18:03 Sam James
2021-10-31 17:58 Sam James
2021-10-31 5:59 Sam James
2021-10-31 5:59 Sam James
2021-10-30 22:55 Sam James
2021-10-30 22:55 Sam James
2021-09-24 7:22 Joonas Niilola
2021-09-24 7:22 Joonas Niilola
2021-09-24 7:22 Joonas Niilola
2021-05-02 15:38 Mikle Kolyada
2021-02-16 12:34 Sam James
2021-02-09 21:31 Sam James
2021-02-09 21:30 Sam James
2021-02-09 9:48 Sam James
2021-02-09 6:16 Sam James
2020-12-21 20:02 Sam James
2020-04-10 10:30 Joonas Niilola
2019-09-20 7:34 Michał Górny
2018-04-14 19:36 Mikle Kolyada
2018-04-05 14:57 Aaron Bauman
2018-03-31 8:15 Tobias Klausmann
2018-03-22 13:17 Mikle Kolyada
2018-03-21 5:55 Markus Meier
2018-03-20 22:21 Sergei Trofimovich
2018-03-11 22:20 Sergei Trofimovich
2018-03-11 15:07 Thomas Deutschmann
2018-01-13 22:54 David Seifert
2017-12-01 21:35 Andreas Sturmlechner
2017-12-01 21:35 Andreas Sturmlechner
2017-09-22 9:48 Patrice Clement
2017-09-06 10:59 Michał Górny
2017-09-02 8:45 Michał Górny
2017-07-30 9:15 Michał Górny
2017-02-26 16:30 Michael Weber
2017-02-23 10:12 Michael Palimaka
2017-02-23 9:57 Michael Palimaka
2017-02-23 9:08 Michael Weber
2017-01-29 16:19 Fabian Groffen
2016-08-07 7:42 Pacho Ramos
2016-08-07 7:25 Pacho Ramos
2016-06-26 0:09 Anthony G. Basile
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=1520768545.7100f4c6918af8e73945e9ecf04a2c230f33890f.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