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-protection/
Date: Sat, 23 Nov 2024 10:31:29 +0000 (UTC)	[thread overview]
Message-ID: <1732357876.899e24bfd2e36adcc12bf61996af0ca57d24761c.graaff@gentoo> (raw)

commit:     899e24bfd2e36adcc12bf61996af0ca57d24761c
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 23 10:02:17 2024 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sat Nov 23 10:31:16 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=899e24bf

dev-ruby/rack-protection: add 4.1.1

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

 dev-ruby/rack-protection/Manifest                  |  1 +
 .../rack-protection/rack-protection-4.1.1.ebuild   | 25 ++++++++++++++++++++++
 2 files changed, 26 insertions(+)

diff --git a/dev-ruby/rack-protection/Manifest b/dev-ruby/rack-protection/Manifest
index 740c1aead874..0759e827da95 100644
--- a/dev-ruby/rack-protection/Manifest
+++ b/dev-ruby/rack-protection/Manifest
@@ -1,2 +1,3 @@
 DIST rack-protection-3.2.0.gem 20480 BLAKE2B ac471dd39e8aad633bf20835f8dbeb9ca53b314b038391a8b334b1e5f2dd2c88983b1988655b5c946211883956318e50a7c2990386a0a43881f29bca474c8789 SHA512 8c8a715e031bbba3a572dc70e3ebc75357e43860fb8c3c88d15c9f07c07b3d6d27b335abc2eebb29c12a78871ef7be9788231f7ccfafca692afea49397310fee
 DIST rack-protection-4.0.0.gem 17408 BLAKE2B e49827ada7524d4e93734f8513502f9c12cb83e0bfb1a5bd02a9a382a2f7be162114984d4ba06e76832d50b26bae17a542856dd40c3d41d8b59004baa2e0328f SHA512 5eb33e4829e5e0d320a14d169fd007111641e388f2b6e5f8de98d45dfd1e6705cdb4e1ce29524ebb6fb5afe14079b8e5370c9c389cb2befca4ca508da73165b3
+DIST rack-protection-4.1.1.gem 18432 BLAKE2B ae91504820aded17a5a819508c91f31066590a208bc64622c3e0d41176e382ad1b506101099f3b0b80a9208e94dfc6102bf8afec14cdabba60a88850cd4adb87 SHA512 0f5fd96d93eab654a7333fe75772b460e91b129da143df420f84ac259f2e24e3b1cf5a1892c1edd2dee3a2ed456cd025ae49dc961c7122a1852de3f15f77d1b1

diff --git a/dev-ruby/rack-protection/rack-protection-4.1.1.ebuild b/dev-ruby/rack-protection/rack-protection-4.1.1.ebuild
new file mode 100644
index 000000000000..f82a981fbb15
--- /dev/null
+++ b/dev-ruby/rack-protection/rack-protection-4.1.1.ebuild
@@ -0,0 +1,25 @@
+# Copyright 1999-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+USE_RUBY="ruby31 ruby32 ruby33"
+
+# There are no specs in the gem and the source cannot be downloaded separately.
+RUBY_FAKEGEM_RECIPE_TEST="none"
+
+RUBY_FAKEGEM_EXTRADOC="README.md"
+
+inherit ruby-fakegem
+
+DESCRIPTION="This gem protects against typical web attacks"
+HOMEPAGE="https://sinatrarb.com/protection/"
+
+LICENSE="MIT"
+SLOT="$(ver_cut 1)"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
+
+ruby_add_rdepend "
+	>=dev-ruby/base64-0.1.0
+	>=dev-ruby/logger-1.6.0
+	|| ( dev-ruby/rack:3.1 dev-ruby/rack:3.0 )
+"


             reply	other threads:[~2024-11-23 10:31 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-23 10:31 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-01  6:05 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rack-protection/ Hans de Graaff
2024-10-06 14:27 Sam James
2024-07-14  8:48 Hans de Graaff
2024-07-14  7:48 Hans de Graaff
2024-05-28  4:54 Hans de Graaff
2024-05-28  4:54 Hans de Graaff
2024-01-21  7:45 Hans de Graaff
2023-12-29  7:40 Hans de Graaff
2023-08-19  5:25 Hans de Graaff
2023-08-12  7:21 Hans de Graaff
2023-07-24 12:07 Jakov Smolić
2023-06-13 10:11 Hans de Graaff
2023-06-13 10:11 Hans de Graaff
2023-06-13 10:11 Hans de Graaff
2023-04-07 11:25 Sam James
2023-04-07  4:12 Sam James
2023-01-08  7:49 Hans de Graaff
2023-01-08  7:49 Hans de Graaff
2022-12-04 17:56 Arthur Zamarin
2022-12-03 11:04 Hans de Graaff
2022-10-22  4:36 Hans de Graaff
2022-10-01  7:55 Hans de Graaff
2022-07-24  7:38 Hans de Graaff
2022-07-16  6:53 Hans de Graaff
2022-06-04  5:47 Hans de Graaff
2022-05-06  8:22 Hans de Graaff
2022-05-06  8:22 Hans de Graaff
2022-03-18  6:57 Hans de Graaff
2021-09-07 21:28 Marek Szuba
2021-05-22  7:21 Hans de Graaff
2020-12-29 10:48 Hans de Graaff
2020-12-29  7:21 Hans de Graaff
2020-09-19  6:06 Hans de Graaff
2020-09-05  8:01 Hans de Graaff
2020-07-05  6:27 Hans de Graaff
2020-06-21  9:05 Hans de Graaff
2020-03-12 13:47 Hans de Graaff
2020-03-01  8:22 Hans de Graaff
2019-08-24  4:45 Hans de Graaff
2019-04-27  6:13 Hans de Graaff
2019-04-27  6:13 Hans de Graaff
2019-01-11  7:59 Hans de Graaff
2018-12-24  7:04 Hans de Graaff
2018-09-27  4:11 Hans de Graaff
2018-07-19  6:30 Hans de Graaff
2018-07-18  5:51 Hans de Graaff
2018-07-18  5:51 Hans de Graaff
2018-07-18  5:51 Hans de Graaff
2018-07-18  5:51 Hans de Graaff
2018-07-06  4:15 Hans de Graaff
2018-06-07  4:43 Hans de Graaff
2018-04-27  8:33 Hans de Graaff
2018-02-19  6:18 Hans de Graaff
2017-06-30 11:17 Alexis Ballier
2017-06-23  3:38 Hans de Graaff
2017-06-12  6:04 Hans de Graaff
2016-07-25 17:28 Hans de Graaff
2016-07-25 17:28 Hans de Graaff
2016-06-02 21:48 Richard Farina
2016-04-16  5:59 Hans de Graaff
2015-08-16 23:14 Mikle Kolyada

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=1732357876.899e24bfd2e36adcc12bf61996af0ca57d24761c.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