From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/paint/
Date: Fri, 31 Mar 2023 01:03:50 +0000 (UTC) [thread overview]
Message-ID: <1680224073.536718df03f3b2870963a4529232913a5c353239.sam@gentoo> (raw)
commit: 536718df03f3b2870963a4529232913a5c353239
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 31 00:33:15 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 31 00:54:33 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=536718df
dev-ruby/paint: drop 2.2.1
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-ruby/paint/Manifest | 1 -
dev-ruby/paint/paint-2.2.1.ebuild | 22 ----------------------
2 files changed, 23 deletions(-)
diff --git a/dev-ruby/paint/Manifest b/dev-ruby/paint/Manifest
index 218af7b99b46..209b8d7cb226 100644
--- a/dev-ruby/paint/Manifest
+++ b/dev-ruby/paint/Manifest
@@ -1,2 +1 @@
-DIST paint-2.2.1.tar.gz 22181 BLAKE2B f0d3e39244fd103e7f248161369189e2e5dafc7eb0f0813998e0da4a80714ab355ca1ebb9357695e97b57db49a90198a2efc0a4043a4e7bfd18fedf58515d113 SHA512 8190c220310b724defa0f482b264afe32bcfd00044380dbb3d8354050857f121c1e084bd737f7b9b89a6950ea4be2c87b7f7282854641df65918bfb6bead5450
DIST paint-2.3.0.tar.gz 24208 BLAKE2B 6f9028c26966ba5c7e0b7de0e9957b2cd73585679347f281a07d2ac95ab5d12f043580cc5afba8f68fd416854c1824b18ed1f53e11f24277f1718786729e66b9 SHA512 296c73ae3066f2114fdadfbaab81bb0f4b4893c8ab5b41d5dc8ef511104541df2a1bfd9f35582742769cb32e11ad22527fef7938952147eec6d4d36526fb5f60
diff --git a/dev-ruby/paint/paint-2.2.1.ebuild b/dev-ruby/paint/paint-2.2.1.ebuild
deleted file mode 100644
index a7b57a3529d0..000000000000
--- a/dev-ruby/paint/paint-2.2.1.ebuild
+++ /dev/null
@@ -1,22 +0,0 @@
-# Copyright 1999-2022 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-USE_RUBY="ruby26 ruby27 ruby30 ruby31"
-
-RUBY_FAKEGEM_RECIPE_TEST="rspec3"
-
-RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md README.md SHORTCUTS.md"
-
-RUBY_FAKEGEM_GEMSPEC=paint.gemspec
-
-inherit ruby-fakegem
-
-DESCRIPTION="Terminal painter"
-HOMEPAGE="https://github.com/janlelis/paint"
-SRC_URI="https://github.com/janlelis/paint/archive/v${PV}.tar.gz -> ${P}.tar.gz"
-
-LICENSE="MIT"
-SLOT="0"
-KEYWORDS="~amd64 ~x86"
-IUSE="test doc"
next reply other threads:[~2023-03-31 1:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 1:03 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-31 11:09 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/paint/ Hans de Graaff
2023-07-21 10:47 Hans de Graaff
2023-06-20 4:38 Hans de Graaff
2022-07-06 5:28 Hans de Graaff
2022-04-30 9:08 Hans de Graaff
2022-04-30 9:08 Hans de Graaff
2020-12-10 5:09 Hans de Graaff
2020-08-01 9:05 Hans de Graaff
2020-02-22 5:32 Hans de Graaff
2019-08-29 5:24 Hans de Graaff
2019-08-29 5:24 Hans de Graaff
2019-01-18 8:23 Hans de Graaff
2018-12-17 5:37 Hans de Graaff
2018-09-09 14:32 Hans de Graaff
2018-02-08 6:25 Hans de Graaff
2017-11-02 5:40 Hans de Graaff
2017-08-26 8:27 Hans de Graaff
2017-06-15 6:08 Hans de Graaff
2016-12-25 6:55 Hans de Graaff
2016-03-25 6:36 Hans de Graaff
2016-01-04 6:21 Hans de Graaff
2016-01-04 6:21 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=1680224073.536718df03f3b2870963a4529232913a5c353239.sam@gentoo \
--to=sam@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