From: "Kent Fredric" <kentnl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Net-SSH-Perl/
Date: Mon, 25 Jul 2016 09:16:32 +0000 (UTC) [thread overview]
Message-ID: <1469435572.cba198df3b3b031e9a6b4f38d75c7a46c6f47da8.kentnl@gentoo> (raw)
commit: cba198df3b3b031e9a6b4f38d75c7a46c6f47da8
Author: Kent Fredric <kentnl <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 25 08:00:40 2016 +0000
Commit: Kent Fredric <kentnl <AT> gentoo <DOT> org>
CommitDate: Mon Jul 25 08:32:52 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cba198df
dev-perl/Net-SSH-Perl: Fix dep on dev-perl/Convert-PEM
Part of migration to PN=Upstream.
Note: ~mips is broken due to Crypt-DSA not being satisfied, but this is a
residual issue.
Package-Manager: portage-2.3.0
RepoMan-Options: --ignore-arches --include-arches="alpha amd64 amd64-fbsd arm arm64 hppa ia64 m68k mips nios2 ppc ppc64 riscv s390 sh sparc sparc-fbsd x86 x86-fbsd"
dev-perl/Net-SSH-Perl/Net-SSH-Perl-1.360.0-r1.ebuild | 2 +-
dev-perl/Net-SSH-Perl/Net-SSH-Perl-1.420.0.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-perl/Net-SSH-Perl/Net-SSH-Perl-1.360.0-r1.ebuild b/dev-perl/Net-SSH-Perl/Net-SSH-Perl-1.360.0-r1.ebuild
index 14074e0..4d4afe2 100644
--- a/dev-perl/Net-SSH-Perl/Net-SSH-Perl-1.360.0-r1.ebuild
+++ b/dev-perl/Net-SSH-Perl/Net-SSH-Perl-1.360.0-r1.ebuild
@@ -24,7 +24,7 @@ DEPEND="
dev-perl/Crypt-DH
>=dev-perl/Crypt-DSA-0.110.0
virtual/perl-MIME-Base64
- >=dev-perl/convert-pem-0.05
+ >=dev-perl/Convert-PEM-0.05
dev-perl/Crypt-Blowfish
dev-perl/Crypt-DES
dev-perl/Crypt-IDEA
diff --git a/dev-perl/Net-SSH-Perl/Net-SSH-Perl-1.420.0.ebuild b/dev-perl/Net-SSH-Perl/Net-SSH-Perl-1.420.0.ebuild
index caf3066..5c4efbd 100644
--- a/dev-perl/Net-SSH-Perl/Net-SSH-Perl-1.420.0.ebuild
+++ b/dev-perl/Net-SSH-Perl/Net-SSH-Perl-1.420.0.ebuild
@@ -15,7 +15,7 @@ KEYWORDS="~amd64 ~mips ~x86"
IUSE="minimal test"
RDEPEND="
- >=dev-perl/convert-pem-0.50.0
+ >=dev-perl/Convert-PEM-0.50.0
dev-perl/Crypt-DES
>=dev-perl/Crypt-DH-0.10.0
>=dev-perl/Crypt-DSA-0.110.0
next reply other threads:[~2016-07-25 9:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 9:16 Kent Fredric [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-27 13:29 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Net-SSH-Perl/ Arthur Zamarin
2023-09-27 5:44 Sam James
2023-09-24 1:53 Sam James
2023-08-27 1:26 Sam James
2023-08-14 7:55 Sam James
2023-07-26 3:33 Sam James
2021-07-17 16:35 Andreas K. Hüttel
2018-09-08 5:30 Mikle Kolyada
2018-07-22 14:51 Thomas Deutschmann
2018-03-28 2:26 Matt Turner
2017-12-08 22:18 Patrice Clement
2017-05-03 0:10 Kent Fredric
2017-05-03 0:10 Kent Fredric
2017-03-23 16:35 Kent Fredric
2017-03-23 16:35 Kent Fredric
2017-03-23 15:35 Kent Fredric
2017-03-11 23:05 Matt Turner
2016-09-12 16:59 Kent Fredric
2016-04-15 19:56 Andreas Hüttel
2016-04-07 23:08 Andreas Hüttel
2016-04-02 0:55 Andreas Hüttel
2016-03-09 20:48 Andreas Hüttel
2016-03-09 20:48 [gentoo-commits] repo/gentoo:master commit in: dev-perl/net-ssh-perl/ Andreas Hüttel
2016-03-05 11:56 Patrice Clement
2016-03-05 11:56 Patrice Clement
2016-03-05 11:56 Patrice Clement
2016-03-05 11:56 Patrice Clement
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=1469435572.cba198df3b3b031e9a6b4f38d75c7a46c6f47da8.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