From: Liam Breck <liam@networkimprov.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: send-email: Net::SMTP::SSL failure
Date: Wed, 7 Jun 2017 11:04:58 -0700 [thread overview]
Message-ID: <CAKvHMgRpS3AgRAm1ukH18kX5jNF6PEU8YTsq7mQ36myQgRe=Pw@mail.gmail.com> (raw)
In-Reply-To: <CACBZZX6AKYA5PmE6Le4cxCTCOOix1ErHyT21C=L83CQBYaN=RQ@mail.gmail.com>
Thanks for your help!
On Wed, Jun 7, 2017 at 10:16 AM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> On Wed, Jun 7, 2017 at 7:00 PM, Liam Breck <liam@networkimprov.net> wrote:
>> On Tue, Jun 6, 2017 at 10:47 PM, Liam Breck <liam@networkimprov.net> wrote:
>>>
>>> This is configured to send via a gmail account
>>> git send-email --to-cover --cc-cover <patch-list>
>>>
>>> I See
>>> Attempt to reload IO/Socket/SSL.pm aborted.
>>> Compilation failed in require at
>>> /usr/share/perl5/vendor_perl/Net/SMTP/SSL.pm line 6.
>>> BEGIN failed--compilation aborted at
>>> /usr/share/perl5/vendor_perl/Net/SMTP/SSL.pm line 6.
>>> Compilation failed in require at /usr/lib/git-core/git-send-email line 1386.
>>> fatal: 'send-email' appears to be a git command, but we were not
>>> able to execute it. Maybe git-send-email is broken?
>>>
>>> Net/SMTP/SSL.pm v1.04
>>>
>>> perl v5.26.0
>>>
>>> Seen in git 2.11.1, 2.12.2, 2.13.0, 2.13.1 on Arch Linux
>>
>> Also fails with perl 5.24.1 & 5.24.0
>>
>> Last working config was git 2.9.3 on perl 5.24.1
>>
>> The relevant code from git-send-email is:
>>
>> require Net::SMTP;
>> $smtp_domain ||= maildomain();
>> $smtp_server_port ||= 25;
>> $smtp ||= Net::SMTP->new($smtp_server,
>> Hello => $smtp_domain,
>> Debug => $debug_net_smtp,
>> Port => $smtp_server_port);
>> if ($smtp_encryption eq 'tls' && $smtp) {
>> require Net::SMTP::SSL;
>> $smtp->command('STARTTLS');
>>
>> I really wish git bundled its non-core perl libs...
>
> What's the output from just:
>
> perl -MNet::SMTP -we1
No output, exit code 0, however...
$ perl -MIO::Socket::SSL -we1
Can't load '/usr/lib/perl5/site_perl/auto/Net/SSLeay/SSLeay.so' for
module Net::SSLeay: libssl.so.1.0.0: cannot open shared object file:
No such file or directory at /usr/lib/perl5/core_perl/DynaLoader.pm
line 193.
at /usr/share/perl5/vendor_perl/IO/Socket/SSL.pm line 19.
Compilation failed in require at
/usr/share/perl5/vendor_perl/IO/Socket/SSL.pm line 19.
BEGIN failed--compilation aborted at
/usr/share/perl5/vendor_perl/IO/Socket/SSL.pm line 19.
Compilation failed in require.
BEGIN failed--compilation aborted.
I don't have {vendor,site}_perl/auto/ tho I have the package for
ssleay installed.
Since which git release was that required?
> I have not looked deeply at this, but the error you're getting means
> "we tried to load it before and failed, and here you are trying
> again".
>
> This is almost definitely due to this line in git-send-email:
>
> if (eval { require Net::SMTP; 1 }) {
>
> And more generally, this code is all buggy:
>
> 4 matches for "eval.*require" in buffer: git-send-email.perl
> 153:my $have_email_valid = eval { require Email::Valid; 1 };
> 154:my $have_mail_address = eval { require Mail::Address; 1 };
> 1118: if (eval { require Net::Domain; 1 }) {
> 1129: if (eval { require Net::SMTP; 1 }) {
>
> Well, "buggy" in the sense that we're just happy-go-lucky trying to
> load these modules, and if they have an error we don't report it, then
> when we try to load them again perl just emits a generic error saying
> you're trying to require() something that already failed somewhere
> before, a minimal test case for that is:
>
> $ cat /tmp/Fails.pm
> package Fails;
> die "oh noes";
> $ perl -I/tmp -we 'eval { require Fails }; require Fails'
> Attempt to reload Fails.pm aborted.
> Compilation failed in require at -e line 1.
>
> Whereas what we really want to do is some variant of:
>
> $ perl -MData::Dumper -I/tmp -we 'eval { require Fails } or warn
> $@; require Fails'
> oh noes at /tmp/Fails.pm line 2.
> Compilation failed in require at -e line 1.
> Attempt to reload Fails.pm aborted.
> Compilation failed in require at -e line 1.
>
> Or even the more adventerous, this can have some bad side-effects with
> some libraries (you lie to perl saying you haven't seen it before),
> but I doubt Net::SMTP cares much, particularly when we're just about
> to report an error:
>
> $ perl -MData::Dumper -I/tmp -we 'eval { require Fails } or do {
> delete $INC{"Fails.pm"} }; require Fails'
> oh noes at /tmp/Fails.pm line 2.
> Compilation failed in require at -e line 1.
next prev parent reply other threads:[~2017-06-07 18:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 5:47 send-email: Net::SMTP::SSL failure Liam Breck
2017-06-07 17:00 ` Liam Breck
2017-06-07 17:16 ` Ævar Arnfjörð Bjarmason
2017-06-07 18:04 ` Liam Breck [this message]
2017-06-07 19:30 ` Ævar Arnfjörð Bjarmason
2017-06-07 19:39 ` Liam Breck
2017-06-07 20:43 ` Ævar Arnfjörð Bjarmason
2017-06-07 21:06 ` Liam Breck
2017-06-08 0:06 ` Samuel Lijin
2017-06-08 0:26 ` Liam Breck
2017-06-08 6:28 ` Ævar Arnfjörð Bjarmason
2017-06-09 16:37 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKvHMgRpS3AgRAm1ukH18kX5jNF6PEU8YTsq7mQ36myQgRe=Pw@mail.gmail.com' \
--to=liam@networkimprov.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).