From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/plist/
Date: Fri, 16 Dec 2016 21:06:05 +0000 (UTC) [thread overview]
Message-ID: <1481922147.d9e8260524cccc7cc16ffaeac37535bd7463e7e6.graaff@gentoo> (raw)
commit: d9e8260524cccc7cc16ffaeac37535bd7463e7e6
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 16 20:51:52 2016 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Fri Dec 16 21:02:27 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d9e82605
dev-ruby/plist: fix tests for new rake versions
Package-Manager: portage-2.3.0
dev-ruby/plist/plist-3.2.0.ebuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-ruby/plist/plist-3.2.0.ebuild b/dev-ruby/plist/plist-3.2.0.ebuild
index b05405e..29d0804 100644
--- a/dev-ruby/plist/plist-3.2.0.ebuild
+++ b/dev-ruby/plist/plist-3.2.0.ebuild
@@ -21,5 +21,6 @@ IUSE=""
all_ruby_prepare() {
sed -e '/gempackagetask/ s:^:#:' \
-e '/GemPackageTask/,/end/ s:^:#:' \
+ -e '/rubyforgepublisher/ s:^:#:' \
-i Rakefile || die
}
next reply other threads:[~2016-12-16 21:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 21:06 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-31 8:53 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/plist/ Hans de Graaff
2023-12-28 9:33 Hans de Graaff
2023-12-27 13:55 Hans de Graaff
2023-06-29 20:13 Hans de Graaff
2023-06-29 20:13 Hans de Graaff
2023-02-25 7:21 Hans de Graaff
2022-04-30 9:08 Hans de Graaff
2022-04-30 9:08 Hans de Graaff
2021-01-03 8:05 Hans de Graaff
2020-07-31 6:28 Hans de Graaff
2020-07-22 13:44 Hans de Graaff
2019-07-16 6:56 Hans de Graaff
2019-01-14 16:36 Hans de Graaff
2018-02-08 6:25 Hans de Graaff
2018-02-08 6:25 Hans de Graaff
2017-12-11 6:24 Hans de Graaff
2017-04-30 5:12 Hans de Graaff
2016-04-07 5:26 Hans de Graaff
2016-01-30 15:50 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=1481922147.d9e8260524cccc7cc16ffaeac37535bd7463e7e6.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