From: "Torsten Veller (tove)" <tove@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-perl/crypt-rsa: crypt-rsa-1.990.0.ebuild ChangeLog
Date: Sat, 27 Aug 2011 19:59:10 +0000 (UTC) [thread overview]
Message-ID: <20110827195910.77CDC20035@flycatcher.gentoo.org> (raw)
tove 11/08/27 19:59:10
Modified: ChangeLog
Added: crypt-rsa-1.990.0.ebuild
Log:
Change version scheme
(Portage version: 2.2.0_alpha51/cvs/Linux x86_64)
Revision Changes Path
1.41 dev-perl/crypt-rsa/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-perl/crypt-rsa/ChangeLog?rev=1.41&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-perl/crypt-rsa/ChangeLog?rev=1.41&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-perl/crypt-rsa/ChangeLog?r1=1.40&r2=1.41
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-perl/crypt-rsa/ChangeLog,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- ChangeLog 24 Apr 2011 15:57:02 -0000 1.40
+++ ChangeLog 27 Aug 2011 19:59:10 -0000 1.41
@@ -1,6 +1,11 @@
# ChangeLog for dev-perl/crypt-rsa
# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-perl/crypt-rsa/ChangeLog,v 1.40 2011/04/24 15:57:02 grobian Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-perl/crypt-rsa/ChangeLog,v 1.41 2011/08/27 19:59:10 tove Exp $
+
+*crypt-rsa-1.990.0 (27 Aug 2011)
+
+ 27 Aug 2011; Torsten Veller <tove@gentoo.org> +crypt-rsa-1.990.0.ebuild:
+ Change version scheme
24 Apr 2011; Fabian Groffen <grobian@gentoo.org> crypt-rsa-1.99.ebuild:
Marked ~x86-solaris, bug #296509
1.1 dev-perl/crypt-rsa/crypt-rsa-1.990.0.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-perl/crypt-rsa/crypt-rsa-1.990.0.ebuild?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-perl/crypt-rsa/crypt-rsa-1.990.0.ebuild?rev=1.1&content-type=text/plain
Index: crypt-rsa-1.990.0.ebuild
===================================================================
# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/dev-perl/crypt-rsa/crypt-rsa-1.990.0.ebuild,v 1.1 2011/08/27 19:59:10 tove Exp $
EAPI=4
MY_PN=Crypt-RSA
MODULE_AUTHOR=VIPUL
MODULE_VERSION=1.99
inherit perl-module
DESCRIPTION="RSA public-key cryptosystem"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~mips ~ppc ~sparc ~x86 ~x86-solaris"
IUSE=""
DEPEND="dev-perl/class-loader
dev-perl/Crypt-Blowfish
dev-perl/convert-ascii-armour
dev-perl/crypt-cbc
dev-perl/crypt-primes
dev-perl/crypt-random
dev-perl/data-buffer
dev-perl/digest-md2
virtual/perl-Digest-MD5
dev-perl/Digest-SHA1
>=dev-perl/math-pari-2.010603
dev-perl/Sort-Versions
dev-perl/tie-encryptedhash"
RDEPEND="${DEPEND}"
SRC_TEST="do"
next reply other threads:[~2011-08-27 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 19:59 Torsten Veller (tove) [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-03 21:04 [gentoo-commits] gentoo-x86 commit in dev-perl/crypt-rsa: crypt-rsa-1.990.0.ebuild ChangeLog Torsten Veller (tove)
2012-03-31 17:12 Raul Porcel (armin76)
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=20110827195910.77CDC20035@flycatcher.gentoo.org \
--to=tove@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