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/necromancer/
Date: Fri, 11 Sep 2020 05:14:05 +0000 (UTC)	[thread overview]
Message-ID: <1599801172.9a3d3467de4a7035ffbb6b7bdd1e0e2fb93820a0.graaff@gentoo> (raw)

commit:     9a3d3467de4a7035ffbb6b7bdd1e0e2fb93820a0
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Fri Sep 11 05:12:52 2020 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Fri Sep 11 05:12:52 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9a3d3467

dev-ruby/necromancer: cleanup

Package-Manager: Portage-3.0.4, Repoman-3.0.1
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-ruby/necromancer/Manifest                 |  1 -
 dev-ruby/necromancer/necromancer-0.5.0.ebuild | 24 ------------------------
 2 files changed, 25 deletions(-)

diff --git a/dev-ruby/necromancer/Manifest b/dev-ruby/necromancer/Manifest
index 692d7a5ebd7..c85817b490c 100644
--- a/dev-ruby/necromancer/Manifest
+++ b/dev-ruby/necromancer/Manifest
@@ -1,2 +1 @@
-DIST necromancer-0.5.0.gem 19968 BLAKE2B c9cce66c913443ee3b74f603e72f05347de052416499aed65b3b06f4062497d0dbe6a0b8a50cc853096878acf524d0125ca9f76770f7fee122df6a2fc6bd6a3b SHA512 582f566eec1bbf418d4466ba334e20a28b4e44c53ecdb41b62637e58b1a9337faf7af9c8af6a32ab9e49241ec1f5fde5f54d27d227e196478580c1c814e7c0ce
 DIST necromancer-0.5.1.gem 19968 BLAKE2B 32bf97caea056a1290ad574a32dbd8f9f258d0830694b28c3691d9d39039fcf6fb1d66c909f720350f455399fbbc9e416354de99bdad532d94843a8f8f1fdab5 SHA512 439358288bbdba674de9ebc4e43ddbba2fd8602c25114fff7a4c93fa11eb5d2a21aae7b6a95d82e78216fa19b5254270292e2e609fd08d6954f2b39afb9a3854

diff --git a/dev-ruby/necromancer/necromancer-0.5.0.ebuild b/dev-ruby/necromancer/necromancer-0.5.0.ebuild
deleted file mode 100644
index 2bf99910c6c..00000000000
--- a/dev-ruby/necromancer/necromancer-0.5.0.ebuild
+++ /dev/null
@@ -1,24 +0,0 @@
-# Copyright 1999-2019 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-USE_RUBY="ruby24 ruby25 ruby26"
-
-RUBY_FAKEGEM_RECIPE_DOC="rdoc"
-RUBY_FAKEGEM_RECIPE_TEST="rspec3"
-
-RUBY_FAKEGEM_EXTRADOC="README.md"
-
-inherit ruby-fakegem
-
-DESCRIPTION="Conversion from one object type to another with a bit of black magic"
-HOMEPAGE="https://github.com/piotrmurach/necromancer"
-
-LICENSE="MIT"
-SLOT="0"
-KEYWORDS="~amd64"
-IUSE=""
-
-all_ruby_prepare() {
-	echo '-rspec_helper' > .rspec || die
-}


             reply	other threads:[~2020-09-11  5:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11  5:14 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-01 16:57 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/necromancer/ Hans de Graaff
2023-12-31 14:36 Hans de Graaff
2023-07-21 10:47 Hans de Graaff
2023-07-02  6:35 Hans de Graaff
2022-12-04 15:08 Hans de Graaff
2022-05-01  7:40 Hans de Graaff
2021-01-10  7:51 Hans de Graaff
2020-09-11  5:14 Hans de Graaff
2019-11-25  6:22 Hans de Graaff
2019-06-16  6:38 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=1599801172.9a3d3467de4a7035ffbb6b7bdd1e0e2fb93820a0.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