public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/test_declarative/
Date: Sun, 12 Nov 2023 07:07:52 +0000 (UTC)	[thread overview]
Message-ID: <1699772869.226efc53c98ed2720fbb4e746dd77a00d9035740.graaff@gentoo> (raw)

commit:     226efc53c98ed2720fbb4e746dd77a00d9035740
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 12 07:07:08 2023 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Nov 12 07:07:49 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=226efc53

dev-ruby/test_declarative: drop minitest workaround

This is now covered by a patch from upstream.

Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-ruby/test_declarative/test_declarative-0.0.6-r1.ebuild | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/dev-ruby/test_declarative/test_declarative-0.0.6-r1.ebuild b/dev-ruby/test_declarative/test_declarative-0.0.6-r1.ebuild
index 2da6eed8edf0..6d224410b2b2 100644
--- a/dev-ruby/test_declarative/test_declarative-0.0.6-r1.ebuild
+++ b/dev-ruby/test_declarative/test_declarative-0.0.6-r1.ebuild
@@ -30,9 +30,6 @@ all_ruby_prepare() {
 	sed -i -e '/rake/ s/~> 12.0.0/>= 10/ ; /minitest/ s/5.10.1/5.10/' Gemfile || die
 
 	sed -i -e 's/git ls-files --/find/' ${RUBY_FAKEGEM_GEMSPEC} || die
-
-	# Work around incompatibilities in newer minitest versions.
-	sed -i -e "15irequire 'minitest/unit'" test/test_declarative_test.rb || die
 }
 
 each_ruby_test() {


             reply	other threads:[~2023-11-12  7:07 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12  7:07 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-27  8:10 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/test_declarative/ Hans de Graaff
2023-12-05 18:25 Ionen Wolkens
2023-11-11  7:36 Hans de Graaff
2023-04-23 22:21 Sam James
2023-04-23 21:40 Sam James
2023-04-23 21:33 Sam James
2023-04-23 21:33 Sam James
2023-04-23 21:33 Sam James
2023-03-10 20:29 Hans de Graaff
2022-05-10  1:07 WANG Xuerui
2022-04-26 14:38 Sam James
2022-04-17  6:57 Hans de Graaff
2022-01-15  6:43 Hans de Graaff
2022-01-15  6:43 Hans de Graaff
2021-11-23 11:28 Hans de Graaff
2021-11-23 10:48 Hans de Graaff
2021-10-02 20:40 Sam James
2021-09-07 15:34 Marek Szuba
2021-01-03  8:05 Hans de Graaff
2020-04-20 17:05 Sergei Trofimovich
2020-01-03 15:55 Hans de Graaff
2019-01-09  8:07 Hans de Graaff
2019-01-09  8:07 Hans de Graaff
2018-07-08  3:45 Hans de Graaff
2018-07-04 20:56 Hans de Graaff
2018-07-04 20:56 Hans de Graaff
2018-07-04 20:56 Hans de Graaff
2017-12-27  7:02 Hans de Graaff
2017-12-27  7:02 Hans de Graaff
2017-06-30 12:47 Alexis Ballier
2017-05-07  9:44 Hans de Graaff
2016-03-28 10:21 Hans de Graaff
2016-03-28 10:21 Hans de Graaff
2015-12-25  8:46 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=1699772869.226efc53c98ed2720fbb4e746dd77a00d9035740.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