From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/aws-eventstream/
Date: Sat, 13 Jul 2024 06:10:40 +0000 (UTC) [thread overview]
Message-ID: <1720850949.5e66bf2bb1099659a5728a6f8fb06a8c21ea9492.graaff@gentoo> (raw)
commit: 5e66bf2bb1099659a5728a6f8fb06a8c21ea9492
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 13 06:03:45 2024 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sat Jul 13 06:09:09 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5e66bf2b
dev-ruby/aws-eventstream: drop 1.2.0
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/aws-eventstream/Manifest | 1 -
.../aws-eventstream/aws-eventstream-1.2.0.ebuild | 21 ---------------------
2 files changed, 22 deletions(-)
diff --git a/dev-ruby/aws-eventstream/Manifest b/dev-ruby/aws-eventstream/Manifest
index f45f76aaa92b..6f97d45334a3 100644
--- a/dev-ruby/aws-eventstream/Manifest
+++ b/dev-ruby/aws-eventstream/Manifest
@@ -1,2 +1 @@
-DIST aws-eventstream-1.2.0.gem 12800 BLAKE2B 3d3459894bfcfa9b4a3cb04b358e011d495250430931c638038e66ac366ad902c8e79c44afc5b123b9ef3bb82efe9a8705017898ffaf268ae829923b6b820cd0 SHA512 d7d8a318523b1d4c4d950861f8fb4fb6b65a76b8df2bd788ca1d81d40f7a1d1fd91ad9db106892b508d348fd7f8678aa387b43ac390bcd75f8fb03d081c3e60b
DIST aws-eventstream-1.3.0.gem 12800 BLAKE2B d66c1597c63a07f8a84f0743fae5df5fd28d58fe89b821f9f68177e0d5afdc58906f020c4cacf796ac999b4f8ce4e5dae61e8e2a86fd148e19c9a28f7cdbf1c1 SHA512 98200938fb087748010b494a75b3dc69c28903175631490cc529a5f740aef217e362eb77a98aa7ae3292e14a3cc559fe3f1f263293f536d47a515e7b77d8ddd8
diff --git a/dev-ruby/aws-eventstream/aws-eventstream-1.2.0.ebuild b/dev-ruby/aws-eventstream/aws-eventstream-1.2.0.ebuild
deleted file mode 100644
index f9658cfaaf22..000000000000
--- a/dev-ruby/aws-eventstream/aws-eventstream-1.2.0.ebuild
+++ /dev/null
@@ -1,21 +0,0 @@
-# Copyright 1999-2023 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-USE_RUBY="ruby27 ruby30 ruby31 ruby32"
-
-# Not packaged and upstream not tagged.
-RUBY_FAKEGEM_RECIPE_TEST="none"
-
-RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md"
-
-inherit ruby-fakegem
-
-DESCRIPTION="Amazon Web Services event stream library"
-HOMEPAGE="https://aws.amazon.com/sdk-for-ruby/"
-
-LICENSE="Apache-2.0"
-SLOT="1"
-KEYWORDS="~amd64 ~arm64"
-IUSE=""
next reply other threads:[~2024-07-13 6:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 6:10 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-03 7:04 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/aws-eventstream/ Hans de Graaff
2025-06-01 7:01 Hans de Graaff
2025-06-01 7:01 Hans de Graaff
2025-03-18 11:46 Hans de Graaff
2025-02-22 10:25 Hans de Graaff
2023-12-27 21:13 Hans de Graaff
2023-11-25 7:53 Hans de Graaff
2023-06-29 5:17 Hans de Graaff
2022-07-26 6:45 Hans de Graaff
2022-06-26 5:43 Hans de Graaff
2021-09-04 6:53 Hans de Graaff
2021-03-18 6:20 Hans de Graaff
2020-10-01 0:26 Sam James
2020-09-16 6:15 Hans de Graaff
2020-04-19 8:57 Hans de Graaff
2020-04-16 23:03 Robin H. Johnson
2019-12-03 7:12 Hans de Graaff
2019-05-11 5:39 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=1720850949.5e66bf2bb1099659a5728a6f8fb06a8c21ea9492.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