From: "Kent Fredric" <kentnl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Set-Object/
Date: Tue, 13 Mar 2018 12:13:14 +0000 (UTC) [thread overview]
Message-ID: <1520942987.d77c11f888d4a200c15b7e8ffff69af50e194211.kentnl@gentoo> (raw)
commit: d77c11f888d4a200c15b7e8ffff69af50e194211
Author: Kent Fredric <kentnl <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 13 12:09:47 2018 +0000
Commit: Kent Fredric <kentnl <AT> gentoo <DOT> org>
CommitDate: Tue Mar 13 12:09:47 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d77c11f8
dev-perl/Set-Object: Cleanup old re bug #623100
Closes: https://bugs.gentoo.org/623100
Package-Manager: Portage-2.3.24, Repoman-2.3.6
dev-perl/Set-Object/Manifest | 1 -
dev-perl/Set-Object/Set-Object-1.350.0.ebuild | 25 -------------------------
2 files changed, 26 deletions(-)
diff --git a/dev-perl/Set-Object/Manifest b/dev-perl/Set-Object/Manifest
index 89141190236..9feedbee3cc 100644
--- a/dev-perl/Set-Object/Manifest
+++ b/dev-perl/Set-Object/Manifest
@@ -1,2 +1 @@
-DIST Set-Object-1.35.tar.gz 79370 BLAKE2B d7e9f95c9b02335bf29104456b69f08723bcdd8ef86e8af2435779ecaf705c082640087272206242c44e0aa0db48e6f2a6bca169bf8f8f1738592a828f26acc8 SHA512 5b915d77772dd3146e89ea8448a178b3faa6fe044a9df1d4aa217afa228df26367faa2d073fe9b6886cbc0a9075ab8ac46ebaf884624aa82be575fd89279d6a7
DIST Set-Object-1.38.tar.gz 80719 BLAKE2B ff7a42a2fd1f368d58bbc73bf10ea3579c952b49a826e47ac9e7ea3c64a792117fd55b2f52979c51ec8964f2abd9c0f5c2f05211e0c7a407e7f37e91ab3486f7 SHA512 fa0411f543fe1837d7c07a07a99d3b8a3735162fb7b665060870cec8edd40ab39eed74791ce2aa96b9ca04a8e773d810ba979508b03f8d4698e8d844f62bee1a
diff --git a/dev-perl/Set-Object/Set-Object-1.350.0.ebuild b/dev-perl/Set-Object/Set-Object-1.350.0.ebuild
deleted file mode 100644
index 638412859cd..00000000000
--- a/dev-perl/Set-Object/Set-Object-1.350.0.ebuild
+++ /dev/null
@@ -1,25 +0,0 @@
-# Copyright 1999-2015 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=5
-
-MODULE_AUTHOR=RURBAN
-MODULE_VERSION=1.35
-inherit perl-module
-
-DESCRIPTION="set of objects and strings"
-
-LICENSE="Artistic-2"
-SLOT="0"
-KEYWORDS="amd64 ~hppa ~ppc x86"
-IUSE="test"
-
-RDEPEND="
- virtual/perl-Scalar-List-Utils
-"
-DEPEND="${RDEPEND}
- virtual/perl-ExtUtils-MakeMaker
- test? ( virtual/perl-Test-Simple )
-"
-
-SRC_TEST="do parallel"
next reply other threads:[~2018-03-13 12:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 12:13 Kent Fredric [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-04 9:22 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Set-Object/ Sam James
2023-07-24 3:19 Sam James
2023-07-24 3:17 Sam James
2023-07-24 3:17 Sam James
2023-06-18 23:46 Sam James
2021-12-05 22:15 Andreas K. Hüttel
2021-08-26 14:57 Sam James
2021-08-26 14:57 Sam James
2021-08-07 23:37 Sam James
2021-08-07 23:37 Sam James
2021-07-24 20:23 Matt Turner
2021-06-08 18:39 Sergei Trofimovich
2021-06-08 9:36 Sam James
2021-06-06 13:28 Andreas K. Hüttel
2018-02-25 18:21 Thomas Deutschmann
2018-02-24 8:07 Jason Zaman
2016-06-25 22:15 Andreas Hüttel
2016-05-13 10:12 Agostino Sarubbo
2015-09-29 21:08 Andreas Hüttel
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=1520942987.d77c11f888d4a200c15b7e8ffff69af50e194211.kentnl@gentoo \
--to=kentnl@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