From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/YAML-LibYAML/
Date: Fri, 20 Jul 2018 08:08:22 +0000 (UTC) [thread overview]
Message-ID: <1532074050.7c8a34813f34c8706936656d7ee61b605fc25a40.slyfox@gentoo> (raw)
commit: 7c8a34813f34c8706936656d7ee61b605fc25a40
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 20 08:01:28 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Jul 20 08:07:30 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7c8a3481
dev-perl/YAML-LibYAML: stable 0.690.0 for ia64, bug #661196
Bug: https://bugs.gentoo.org/661196
Package-Manager: Portage-2.3.43, Repoman-2.3.10
RepoMan-Options: --include-arches="ia64"
dev-perl/YAML-LibYAML/YAML-LibYAML-0.690.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/YAML-LibYAML/YAML-LibYAML-0.690.0.ebuild b/dev-perl/YAML-LibYAML/YAML-LibYAML-0.690.0.ebuild
index 5548f2512fb..73e63088f5b 100644
--- a/dev-perl/YAML-LibYAML/YAML-LibYAML-0.690.0.ebuild
+++ b/dev-perl/YAML-LibYAML/YAML-LibYAML-0.690.0.ebuild
@@ -9,7 +9,7 @@ inherit perl-module
DESCRIPTION="Perl YAML Serialization using XS and libyaml"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~s390 sparc x86"
+KEYWORDS="~alpha amd64 ~arm ~hppa ia64 ~ppc ~ppc64 ~s390 sparc x86"
IUSE=""
RDEPEND=""
next reply other threads:[~2018-07-20 8:08 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 8:08 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-14 3:50 [gentoo-commits] repo/gentoo:master commit in: dev-perl/YAML-LibYAML/ Sam James
2024-06-09 20:36 Sam James
2024-04-27 6:51 Andreas K. Hüttel
2023-10-16 16:34 Joonas Niilola
2023-08-19 15:37 Arthur Zamarin
2023-08-19 7:23 Sam James
2023-08-19 6:10 Sam James
2023-08-19 6:07 Sam James
2023-08-19 6:03 Sam James
2023-08-19 5:58 Sam James
2023-06-17 23:35 Sam James
2021-12-11 15:52 Andreas K. Hüttel
2021-12-06 1:16 Sam James
2021-12-06 0:31 Sam James
2021-12-06 0:13 Sam James
2021-12-06 0:10 Sam James
2021-12-05 5:17 Sam James
2021-12-05 5:00 Sam James
2021-12-05 3:31 Sam James
2021-10-07 23:35 Andreas K. Hüttel
2021-09-21 13:41 Yixun Lan
2020-12-27 16:25 Fabian Groffen
2019-07-29 18:42 Aaron Bauman
2019-07-25 6:48 Kent Fredric
2019-04-01 19:33 Andreas Sturmlechner
2018-12-08 12:35 Mikle Kolyada
2018-10-27 19:50 Fabian Groffen
2018-07-23 19:00 Sergei Trofimovich
2018-07-23 0:43 Mikle Kolyada
2018-07-21 11:50 Tobias Klausmann
2018-07-20 23:18 Sergei Trofimovich
2018-07-20 22:48 Sergei Trofimovich
2018-07-16 6:54 Sergei Trofimovich
2018-06-13 10:19 Mikle Kolyada
2018-04-03 6:42 Kent Fredric
2017-11-02 8:44 Sergei Trofimovich
2017-06-08 23:21 Kent Fredric
2017-05-31 1:17 Kent Fredric
2017-05-28 6:43 Markus Meier
2017-05-22 1:19 Michael Weber
2017-05-20 9:34 Agostino Sarubbo
2017-05-20 8:49 Agostino Sarubbo
2017-04-08 3:25 Kent Fredric
2017-03-17 10:26 Agostino Sarubbo
2017-03-15 14:14 Michael Weber
2017-03-15 13:00 Michael Weber
2017-02-04 13:11 Jeroen Roovers
2016-10-19 11:05 Agostino Sarubbo
2016-09-29 19:43 Andreas Hüttel
2016-09-29 19:43 Andreas Hüttel
2016-05-25 6:52 Matt Turner
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=1532074050.7c8a34813f34c8706936656d7ee61b605fc25a40.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