From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-electronics/klayout/
Date: Sun, 20 Aug 2017 08:59:29 +0000 (UTC) [thread overview]
Message-ID: <1503219558.823c52ab2be85aa75f27496f7e9433c23cb4d45b.graaff@gentoo> (raw)
commit: 823c52ab2be85aa75f27496f7e9433c23cb4d45b
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 20 08:10:33 2017 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Aug 20 08:59:18 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=823c52ab
sci-electronics/klayout: switch to ruby22 due to ruby21 removal
Package-Manager: Portage-2.3.6, Repoman-2.3.2
sci-electronics/klayout/klayout-0.23.10.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sci-electronics/klayout/klayout-0.23.10.ebuild b/sci-electronics/klayout/klayout-0.23.10.ebuild
index 998bf5dd622..2f96c460f1d 100644
--- a/sci-electronics/klayout/klayout-0.23.10.ebuild
+++ b/sci-electronics/klayout/klayout-0.23.10.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2016 Gentoo Foundation
+# Copyright 1999-2017 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=5
-USE_RUBY="ruby21"
+USE_RUBY="ruby22"
# note: define maximally ONE implementation here
RUBY_OPTIONAL=no
next reply other threads:[~2017-08-20 8:59 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 8:59 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-07 5:39 [gentoo-commits] repo/gentoo:master commit in: sci-electronics/klayout/ Sam James
2024-09-27 11:34 Andreas K. Hüttel
2023-06-25 20:18 Andreas K. Hüttel
2023-06-25 20:18 Andreas K. Hüttel
2023-06-25 20:18 Andreas K. Hüttel
2023-06-18 13:18 Andreas K. Hüttel
2023-03-29 13:04 Sam James
2023-03-29 12:29 Sam James
2023-03-28 22:19 Sam James
2023-03-28 22:19 Sam James
2023-03-14 13:09 Andreas K. Hüttel
2023-03-14 13:09 Andreas K. Hüttel
2023-03-14 13:09 Andreas K. Hüttel
2022-11-24 19:18 Andreas K. Hüttel
2022-11-24 19:18 Andreas K. Hüttel
2022-11-24 19:18 Andreas K. Hüttel
2022-07-09 12:26 Andreas K. Hüttel
2022-07-09 11:48 Andreas K. Hüttel
2022-07-09 11:48 Andreas K. Hüttel
2022-07-09 11:48 Andreas K. Hüttel
2022-02-06 15:12 Andreas K. Hüttel
2022-02-06 15:12 Andreas K. Hüttel
2022-02-06 15:12 Andreas K. Hüttel
2021-09-18 19:55 Andreas K. Hüttel
2021-09-18 19:55 Andreas K. Hüttel
2021-05-29 13:27 Andreas K. Hüttel
2021-05-29 13:27 Andreas K. Hüttel
2021-05-29 13:27 Andreas K. Hüttel
2021-03-12 23:58 Andreas K. Hüttel
2021-02-28 21:21 Andreas K. Hüttel
2021-02-28 21:21 Andreas K. Hüttel
2021-01-23 11:20 Andreas K. Hüttel
2021-01-21 20:53 Andreas K. Hüttel
2020-09-29 9:11 Andreas K. Hüttel
2020-09-29 9:11 Andreas K. Hüttel
2020-09-19 22:56 Andreas K. Hüttel
2020-06-04 20:00 Andreas K. Hüttel
2020-05-06 21:15 Andreas K. Hüttel
2020-05-06 21:15 Andreas K. Hüttel
2020-04-19 21:01 Andreas K. Hüttel
2020-04-19 14:33 Andreas K. Hüttel
2020-03-30 5:39 Hans de Graaff
2020-02-10 12:12 Michał Górny
2019-08-13 7:40 Michał Górny
2019-08-12 17:58 Michał Górny
2018-12-14 17:12 Andreas K. Hüttel
2018-06-09 14:09 Aaron Bauman
2018-04-14 7:28 Hans de Graaff
2018-03-19 0:54 Andreas Hüttel
2018-01-25 20:33 Andreas Sturmlechner
2018-01-25 20:32 Andreas Sturmlechner
2018-01-25 18:06 Andreas Sturmlechner
2018-01-25 16:43 Andreas Sturmlechner
2018-01-25 16:43 Andreas Sturmlechner
2018-01-25 16:43 Andreas Sturmlechner
2017-12-27 18:39 Andreas Hüttel
2017-10-09 23:44 Andreas Hüttel
2017-10-01 6:04 Andreas Hüttel
2017-09-30 1:48 Andreas Hüttel
2017-09-29 13:18 Andreas Hüttel
2017-09-29 13:18 Andreas Hüttel
2017-08-20 8:59 Hans de Graaff
2017-08-06 7:47 Andreas Hüttel
2016-12-13 20:50 Andreas Hüttel
2016-12-03 7:36 Hans de Graaff
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=1503219558.823c52ab2be85aa75f27496f7e9433c23cb4d45b.graaff@gentoo \
--to=graaff@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