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: Sun, 21 Jan 2024 07:45:05 +0000 (UTC) [thread overview]
Message-ID: <1705822711.eca69f5427f13321f2f75e6c6be9a48cae1381b6.graaff@gentoo> (raw)
commit: eca69f5427f13321f2f75e6c6be9a48cae1381b6
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 21 07:38:31 2024 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Jan 21 07:38:31 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eca69f54
dev-ruby/rack-protection: add 3.2.0
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/rack-protection/Manifest | 1 +
.../rack-protection/rack-protection-3.2.0.ebuild | 24 ++++++++++++++++++++++
2 files changed, 25 insertions(+)
diff --git a/dev-ruby/rack-protection/Manifest b/dev-ruby/rack-protection/Manifest
index 53bbf271c721..bb5be98d1139 100644
--- a/dev-ruby/rack-protection/Manifest
+++ b/dev-ruby/rack-protection/Manifest
@@ -1,3 +1,4 @@
DIST rack-protection-3.0.5.gem 20480 BLAKE2B 1fa11760c6ddac58234ffe2e6d783c985e29b5e2bd10ea21b0782f7824b5930351c8e32c9401b6276ef028adcd8b25ca4458333d8008a554c413f54315ff8809 SHA512 4ed0ee9e8fe08532ff7f2905251af110f3fff0e419da5be50ae3e5a90906e43c39cf8edc219fcfe3e27a72591500c040afcc9552da875773375b170fb91aa9ff
DIST rack-protection-3.0.6.gem 20480 BLAKE2B b29d8b87dd7bc4629d97923a448feacb53ae62f8d3753b44a627db742e3065eb1d09846e0be9131b02c83a32e1241154a844fcd5a5a7e708039cae7f6938fbb8 SHA512 4763a0439a3d99cfd799325004c7e6cb46783b3fcd77ea0df08caa6b5cdfc95c6ec96791d79261a0d7df26eb0b084e7ead2cceb05b589617159e948b3172e564
DIST rack-protection-3.1.0.gem 20480 BLAKE2B ae5a784eb7420b756d15b251ebc981197f11979e76fed2ad42eb0bcf84719f4b9ab9d68a40ac9ee8db392ad7a8c45c8d4f03de2efb0375dbaa131ec5ff2022e2 SHA512 18a5ffe614a906ca876926bff3e4d1657f0b6963005ee32de80d0ab987b9465f603b30d69f07fd8d8a1ebf4fa85eb89bfd0b607d72387b360d13bea113a63ef7
+DIST rack-protection-3.2.0.gem 20480 BLAKE2B ac471dd39e8aad633bf20835f8dbeb9ca53b314b038391a8b334b1e5f2dd2c88983b1988655b5c946211883956318e50a7c2990386a0a43881f29bca474c8789 SHA512 8c8a715e031bbba3a572dc70e3ebc75357e43860fb8c3c88d15c9f07c07b3d6d27b335abc2eebb29c12a78871ef7be9788231f7ccfafca692afea49397310fee
diff --git a/dev-ruby/rack-protection/rack-protection-3.2.0.ebuild b/dev-ruby/rack-protection/rack-protection-3.2.0.ebuild
new file mode 100644
index 000000000000..b79877ef8fa3
--- /dev/null
+++ b/dev-ruby/rack-protection/rack-protection-3.2.0.ebuild
@@ -0,0 +1,24 @@
+# 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"
+IUSE=""
+
+ruby_add_rdepend "dev-ruby/rack:*"
+
+# ruby_add_bdepend "test? ( dev-ruby/rack-test )"
next reply other threads:[~2024-01-21 7:45 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 7:45 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-06 14:27 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rack-protection/ 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
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=1705822711.eca69f5427f13321f2f75e6c6be9a48cae1381b6.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