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/rack-attack/
Date: Mon, 22 Apr 2019 05:40:08 +0000 (UTC)	[thread overview]
Message-ID: <1555911564.09c1b38350d636206909937f7d3756960656b1ca.graaff@gentoo> (raw)

commit:     09c1b38350d636206909937f7d3756960656b1ca
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 22 05:35:53 2019 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon Apr 22 05:39:24 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=09c1b383

dev-ruby/rack-attack: don't install useless binstubs

Fixes: https://bugs.gentoo.org/684034

Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11

 dev-ruby/rack-attack/rack-attack-5.4.2.ebuild | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/dev-ruby/rack-attack/rack-attack-5.4.2.ebuild b/dev-ruby/rack-attack/rack-attack-5.4.2.ebuild
index 150fc467801..debf6466148 100644
--- a/dev-ruby/rack-attack/rack-attack-5.4.2.ebuild
+++ b/dev-ruby/rack-attack/rack-attack-5.4.2.ebuild
@@ -11,6 +11,8 @@ RUBY_FAKEGEM_TASK_TEST="test:units"
 RUBY_FAKEGEM_RECIPE_DOC="rdoc"
 RUBY_FAKEGEM_EXTRADOC="README.md"
 
+RUBY_FAKEGEM_BINWRAP=""
+
 inherit ruby-fakegem
 
 DESCRIPTION="A DSL for blocking & throttling abusive clients"


             reply	other threads:[~2019-04-22  5:40 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22  5:40 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-03  9:12 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rack-attack/ Hans de Graaff
2024-03-19  6:27 Hans de Graaff
2023-08-27  6:11 Hans de Graaff
2023-07-11  4:37 Hans de Graaff
2023-07-11  4:37 Hans de Graaff
2022-12-11  8:11 Hans de Graaff
2022-12-11  8:11 Hans de Graaff
2022-06-26  6:20 Hans de Graaff
2022-04-14  5:01 Hans de Graaff
2022-04-14  5:01 Hans de Graaff
2022-01-30  8:19 Hans de Graaff
2021-02-09  5:47 Hans de Graaff
2021-01-25  5:54 Hans de Graaff
2020-09-11  5:14 Hans de Graaff
2020-09-05  8:01 Hans de Graaff
2020-05-24  7:09 Hans de Graaff
2020-05-24  4:14 Hans de Graaff
2020-04-30  5:26 Hans de Graaff
2019-12-20  7:21 Hans de Graaff
2019-11-09  6:28 Hans de Graaff
2019-11-02  5:40 Hans de Graaff
2019-10-13  6:38 Hans de Graaff
2019-07-13  5:40 Hans de Graaff
2019-05-22 17:20 Hans de Graaff
2019-05-18  5:36 Hans de Graaff
2019-04-22  5:40 Hans de Graaff
2019-03-30  6:46 Hans de Graaff
2019-01-27 19:13 Hans de Graaff
2018-11-01  6:04 Hans de Graaff
2018-10-18  4:39 Hans de Graaff
2018-07-06  4:15 Hans de Graaff
2018-06-27  5:23 Hans de Graaff
2018-06-20  4:49 Hans de Graaff
2018-05-22  5:20 Hans de Graaff
2017-08-25  6:09 Hans de Graaff
2017-07-20  6:25 Hans de Graaff
2016-04-17  8:06 Hans de Graaff
2016-02-18  6:47 Hans de Graaff
2016-02-11 13:11 Hans de Graaff
2016-01-10  9:48 Hans de Graaff
2015-12-19  7:55 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=1555911564.09c1b38350d636206909937f7d3756960656b1ca.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