git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Samuel Lijin <sxlijin@gmail.com>
Cc: Liam Breck <liam@networkimprov.net>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: send-email: Net::SMTP::SSL failure
Date: Thu, 8 Jun 2017 08:28:19 +0200	[thread overview]
Message-ID: <CACBZZX5SMsXHkVS-a9iarTw_VnH8hBEdN7a56e8ma89nfOLqrA@mail.gmail.com> (raw)
In-Reply-To: <CAJZjrdUSVeZ-zHpeyuN4p29Hg8eGk6ip2Tikkrh-wE-KaxWbEw@mail.gmail.com>

On Thu, Jun 8, 2017 at 2:06 AM, Samuel Lijin <sxlijin@gmail.com> wrote:
> On Wed, Jun 7, 2017 at 4:43 PM, Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>> Ah, so you installed Net::SSLeay via CPAN, and then upgraded your Arch
>> openssl, breaking the CPAN-built *.so object?
>>
>>> Agreed that send-email should be report errors properly. It's a rather
>>> essential tool.
>>
>> Indeed, do you get a meaningful error if you apply my patch?
>
> FWIW I'm on Arch as well and am getting what I assume is a related error:
>
> SSLeay.c: loadable library and perl binaries are mismatched (got
> handshake key 0xdb80080, needed 0xde00080)
>
> The last patch I sent out was on 5/23, and I just ran a system upgrade
> today (only one I've done since then), which presumably is what
> "broke" send-email. I used CPAN to install Net::SMTP::SSL,
> Mime::Base64, and Authen::SASL; I assume that Net::SSLeay is installed
> as a dependency of one of the three (presumably the first)?
>
> I know Net::SSLeay isn't controlled by Arch's package manager:
>
> $ perldoc -l Net::SSLeay
> /usr/lib/perl5/site_perl/Net/SSLeay.pod
> $ pacman -Qo /usr/lib/perl5/site_perl/Net/SSLeay.pod
> error: No package owns /usr/lib/perl5/site_perl/Net/SSLeay.pod
>
> Ævar's patch unfortunately does not fix or change anything for me.

It doesn't fix anything, it should make you get a better error message
when the thing does break, i.e. not an "Attempt to reload" error,
doesn't that happen? What error do you get with/without my patch?

> Liam: when you say "uninstall" /usr/{lib,share}/perl5/site_perl/*, do
> you just mean rm -rf?

  parent reply	other threads:[~2017-06-08  6:28 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
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 [this message]
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=CACBZZX5SMsXHkVS-a9iarTw_VnH8hBEdN7a56e8ma89nfOLqrA@mail.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=liam@networkimprov.net \
    --cc=sxlijin@gmail.com \
    /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).