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/git/
Date: Wed, 31 Jan 2024 16:45:39 +0000 (UTC)	[thread overview]
Message-ID: <1706719530.b2f9455037c8029c0e0807ee085356db531246d7.graaff@gentoo> (raw)

commit:     b2f9455037c8029c0e0807ee085356db531246d7
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 31 16:44:56 2024 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Wed Jan 31 16:45:30 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b2f94550

dev-ruby/git: add missing test dependency

Closes: https://bugs.gentoo.org/923390
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-ruby/git/git-1.19.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/git/git-1.19.1.ebuild b/dev-ruby/git/git-1.19.1.ebuild
index cc2e9b815be9..36d7c68160a4 100644
--- a/dev-ruby/git/git-1.19.1.ebuild
+++ b/dev-ruby/git/git-1.19.1.ebuild
@@ -26,7 +26,7 @@ RDEPEND+=">=dev-vcs/git-1.6.0.0"
 
 ruby_add_rdepend ">=dev-ruby/addressable-2.8:0 >=dev-ruby/rchardet-1.8:1"
 
-ruby_add_bdepend "test? ( dev-ruby/bundler dev-ruby/minitar dev-ruby/test-unit:2 )"
+ruby_add_bdepend "test? ( dev-ruby/bundler dev-ruby/minitar >=dev-ruby/mocha-2.1:2 dev-ruby/test-unit:2 )"
 
 all_ruby_prepare() {
 	# Don't use hardcoded /tmp directory.


             reply	other threads:[~2024-01-31 16:45 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 16:45 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-22  7:47 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/git/ Hans de Graaff
2024-10-24  6:33 Hans de Graaff
2024-10-24  6:33 Hans de Graaff
2024-10-06 11:35 Sam James
2024-09-17 16:29 Arthur Zamarin
2024-09-02  5:22 Hans de Graaff
2024-09-02  5:22 Hans de Graaff
2024-08-31  2:42 Ionen Wolkens
2024-08-27  5:40 Hans de Graaff
2024-08-27  5:40 Hans de Graaff
2024-07-18  6:47 Hans de Graaff
2024-07-18  6:47 Hans de Graaff
2024-07-18  6:47 Hans de Graaff
2024-07-18  6:47 Hans de Graaff
2024-06-29  8:53 Sam James
2024-06-29  5:16 Hans de Graaff
2024-01-15  7:40 Hans de Graaff
2024-01-14  8:30 Hans de Graaff
2023-12-29  7:47 Hans de Graaff
2023-07-12  5:41 Hans de Graaff
2023-07-12  5:41 Hans de Graaff
2023-04-24 15:29 Arthur Zamarin
2023-04-08 10:57 Arthur Zamarin
2023-03-24  7:00 Hans de Graaff
2023-03-24  7:00 Hans de Graaff
2023-03-04  8:28 Hans de Graaff
2023-03-04  8:28 Hans de Graaff
2023-02-04  7:41 Hans de Graaff
2023-02-04  7:41 Hans de Graaff
2023-02-04  7:41 Hans de Graaff
2023-01-13  7:57 Hans de Graaff
2023-01-09  6:33 Hans de Graaff
2023-01-09  6:33 Hans de Graaff
2023-01-08 11:57 Hans de Graaff
2023-01-08  8:33 Hans de Graaff
2022-12-15  6:51 Hans de Graaff
2022-12-15  6:51 Hans de Graaff
2022-12-15  6:51 Hans de Graaff
2022-08-19  5:47 Hans de Graaff
2022-08-19  5:47 Hans de Graaff
2022-05-06  7:13 Hans de Graaff
2022-04-19  5:09 Hans de Graaff
2022-04-19  5:09 Hans de Graaff
2022-01-15  6:29 Hans de Graaff
2022-01-15  6:29 Hans de Graaff
2021-12-25  7:42 Hans de Graaff
2021-12-25  7:42 Hans de Graaff
2021-07-09  6:55 Hans de Graaff
2020-08-21  6:51 Hans de Graaff
2020-07-12  6:35 Hans de Graaff
2020-07-11 16:05 Sam James
2020-07-11  3:50 Sam James
2020-06-20 14:49 Thomas Deutschmann
2020-05-21  5:15 Hans de Graaff
2019-11-16  9:13 Hans de Graaff
2019-07-22 13:03 Hans de Graaff
2019-02-02  8:13 Hans de Graaff
2018-08-11  5:05 Hans de Graaff
2018-08-11  5:05 Hans de Graaff
2018-08-11  5:05 Hans de Graaff
2018-05-17  4:57 Hans de Graaff
2017-07-18  6:45 Hans de Graaff
2016-12-18  7:45 Hans de Graaff
2016-08-13  6:13 Hans de Graaff
2016-07-21 19:38 Hans de Graaff
2016-03-21 21:53 Manuel Rüger
2016-03-21 21:53 Manuel Rüger
2016-02-26  6:54 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=1706719530.b2f9455037c8029c0e0807ee085356db531246d7.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