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: Wed, 16 Sep 2020 06:15:09 +0000 (UTC) [thread overview]
Message-ID: <1600235782.e4c4469d42b822b9c343ec6a8e8171fa3d8ab1a8.graaff@gentoo> (raw)
commit: e4c4469d42b822b9c343ec6a8e8171fa3d8ab1a8
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Wed Sep 16 05:56:22 2020 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Wed Sep 16 05:56:22 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e4c4469d
dev-ruby/aws-eventstream: cleanup
Package-Manager: Portage-3.0.4, Repoman-3.0.1
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/aws-eventstream/Manifest | 1 -
dev-ruby/aws-eventstream/aws-eventstream-1.0.3.ebuild | 19 -------------------
2 files changed, 20 deletions(-)
diff --git a/dev-ruby/aws-eventstream/Manifest b/dev-ruby/aws-eventstream/Manifest
index 36ace86acbf..ac99559ec04 100644
--- a/dev-ruby/aws-eventstream/Manifest
+++ b/dev-ruby/aws-eventstream/Manifest
@@ -1,2 +1 @@
-DIST aws-eventstream-1.0.3.gem 9216 BLAKE2B 32cb1d14562365bd9fc579272f6f5a56d542662dbca765431a980c278aa1ecdc4c61ba4875c52c83d962771e89f831c4b167b176882bf45649cea7732ec68c04 SHA512 bd2babd7ec1e3190b839925116cfe315f09087e106970603941ce4e1eea64cb4fcbf59d16c547a5ac4968792839de3dbb2e4719a05cd4433c611df44567029b0
DIST aws-eventstream-1.1.0.gem 8704 BLAKE2B 52018f2466f24b5c4ca9463321d4bad94579c6c98ef7fe0de34376da1e9ecfa0171de3485f65266a8b6be99c6eab956b88b367b8431c62aac1b46107f47925db SHA512 40af0ad738341bd879458060c5d5b1cda3d539ecec18e3e14f2c36582368e246a1dd510480629f7f29e044dc6f9d3a028af72650a0386491931f5a2691ac5d8a
diff --git a/dev-ruby/aws-eventstream/aws-eventstream-1.0.3.ebuild b/dev-ruby/aws-eventstream/aws-eventstream-1.0.3.ebuild
deleted file mode 100644
index 0fff340c1e8..00000000000
--- a/dev-ruby/aws-eventstream/aws-eventstream-1.0.3.ebuild
+++ /dev/null
@@ -1,19 +0,0 @@
-# Copyright 1999-2019 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-
-USE_RUBY="ruby24 ruby25 ruby26"
-
-# Not packaged and upstream not tagged.
-RUBY_FAKEGEM_RECIPE_TEST="none"
-
-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"
-IUSE=""
next reply other threads:[~2020-09-16 6:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 6:15 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
2024-07-13 6:10 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-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=1600235782.e4c4469d42b822b9c343ec6a8e8171fa3d8ab1a8.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