From: "Andreas Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Devel-Cycle/
Date: Tue, 5 Jan 2016 13:10:57 +0000 (UTC) [thread overview]
Message-ID: <1451999435.66a7a15c8dc10208e127e47ca97322a3fdf47b55.dilfridge@gentoo> (raw)
commit: 66a7a15c8dc10208e127e47ca97322a3fdf47b55
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 5 13:05:40 2016 +0000
Commit: Andreas Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Tue Jan 5 13:10:35 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=66a7a15c
dev-perl/Devel-Cycle: Remove old
Package-Manager: portage-2.2.26
dev-perl/Devel-Cycle/Devel-Cycle-1.110.0-r1.ebuild | 17 -----------------
dev-perl/Devel-Cycle/Manifest | 1 -
2 files changed, 18 deletions(-)
diff --git a/dev-perl/Devel-Cycle/Devel-Cycle-1.110.0-r1.ebuild b/dev-perl/Devel-Cycle/Devel-Cycle-1.110.0-r1.ebuild
deleted file mode 100644
index c6fcbe3..0000000
--- a/dev-perl/Devel-Cycle/Devel-Cycle-1.110.0-r1.ebuild
+++ /dev/null
@@ -1,17 +0,0 @@
-# Copyright 1999-2014 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-# $Id$
-
-EAPI=5
-
-MODULE_AUTHOR=LDS
-MODULE_VERSION=1.11
-inherit perl-module
-
-DESCRIPTION="Find memory cycles in objects"
-
-SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ppc ppc64 x86 ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos"
-IUSE=""
-
-SRC_TEST="do"
diff --git a/dev-perl/Devel-Cycle/Manifest b/dev-perl/Devel-Cycle/Manifest
index 0caac91..3f14c05 100644
--- a/dev-perl/Devel-Cycle/Manifest
+++ b/dev-perl/Devel-Cycle/Manifest
@@ -1,2 +1 @@
-DIST Devel-Cycle-1.11.tar.gz 6843 SHA256 3a9325a04d0649643cc1c37909a347698d0a3c11f8780475de5d8c9cba1f879d SHA512 605290e6cfa0876534b07ad04e60ba08b1b229341b5d5237de2b9aa142b3c2627640bf59df830888ba09ed62c11fbf4d65d0bc99036fcac0fd282497135355ed WHIRLPOOL 92aa01864f51d336ce97b4cef7ea5b36d34cb848dc9fff03f53354e83d7771e0630987777bea7033f6a370ac45a1432cd32a640289f32973adc4a45e811e9878
DIST Devel-Cycle-1.12.tar.gz 7276 SHA256 fd3365c4d898b2b2bddbb78a46d507a18cca8490a290199547dab7f1e7390bc2 SHA512 e2c83829905449d13c86233ad5bfce28e7b4eca61a8ac1e2f73e3c906a2d8580f66ae84d865ef876c38c2d25f0a5a8adeb05f6e94594274d8a5fa1739842d08d WHIRLPOOL b2c73356363c043fd6c6595fdc8f471a47999712e9503ca70ac0ad796b3d5feaed7a067aab8b7af85db3ccb943d5508f5c05e8e15466570afe27935b9b14104c
next reply other threads:[~2016-01-05 13:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 13:10 Andreas Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-23 17:47 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Devel-Cycle/ Arthur Zamarin
2024-06-20 15:07 Ionen Wolkens
2021-10-16 0:48 Sam James
2021-08-02 2:24 Sam James
2021-05-23 22:54 Andreas K. Hüttel
2021-05-23 22:54 Andreas K. Hüttel
2020-12-27 14:54 Fabian Groffen
2020-10-22 5:11 Joshua Kinard
2020-09-03 4:33 Yixun Lan
2020-09-02 6:33 Sergei Trofimovich
2020-08-17 21:42 Sergei Trofimovich
2020-08-17 9:40 Sam James
2020-08-17 8:50 Sam James
2020-08-17 8:04 Sam James
2020-07-30 2:15 Kent Fredric
2018-10-17 18:54 Fabian Groffen
2016-02-03 14:36 Tobias Klausmann
2016-01-05 9:23 Agostino Sarubbo
2015-11-08 6:25 Jeroen Roovers
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=1451999435.66a7a15c8dc10208e127e47ca97322a3fdf47b55.dilfridge@gentoo \
--to=dilfridge@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