public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: git send-email Undefined subroutine &IO::Socket::SSL
Date: Thu, 19 Sep 2019 09:14:40 -0400	[thread overview]
Message-ID: <49FD3D92-6860-46A4-8AF3-2478C24B798D@ipfire.org> (raw)
In-Reply-To: <98f0d22ff02b4e438542aef6314661853983407d.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 3978 bytes --]

Hi,

> On 18 Sep 2019, at 08:57, ummeegge <ummeegge(a)ipfire.org> wrote:
> 
> Hi Michael,
> 
> On Mi, 2019-09-18 at 08:29 -0400, Michael Tremer wrote:
>> Hi,
>> 
>> No this looks like an FTP connection issue, but we don’t use FTP.
> Have used SFTP like in earlier times with FilZilla -->
> 
> fzSftp started, protocol_version=8
> 
> Login and navigation was possible but no upload.
> Was nevertheless able to upload now the IO-Socket-SSL sources via
> console on a Linux Mint system.
> There seems to be some new really sharp settings on SSH, my IP has been
> two times banned where i am not 100% sure why that´s happend.

Since when is that?

Peter has installed fail2ban this week and maybe that is a little bit too… err.. secure now?!

-Michael

> 
> Best,
> 
> Erik
> 
>> 
>> What did you use to upload this file?
>> 
>> -Michael
>> 
>>> On 18 Sep 2019, at 01:01, ummeegge <ummeegge(a)ipfire.org> wrote:
>>> 
>>> Hi Michael,
>>> have currently a problem to upload the IO-Socket-SSL sources to the
>>> pub
>>> directory.
>>> The log says:
>>> 
>>> Status:	Verbinde mit git.ipfire.org...
>>> Status:	Connected to fw01.ipfire.org
>>> Status:	Starte Upload von /home/neptun/Downloads/IO-Socket-SSL-
>>> 2.066.tar.gz
>>> Befehl:	cd "/pub/sources/source-2.x"
>>> Antwort:	New directory is: "/pub/sources/source-2.x"
>>> Befehl:	put "/home/neptun/Downloads/IO-Socket-SSL-2.066.tar.gz" 
>>> "IO-Socket-SSL-2.066.tar.gz"
>>> Befehl:	local:/home/neptun/Downloads/IO-Socket-SSL-2.066.tar.gz 
>>> => remote:/pub/sources/source-2.x/IO-Socket-SSL-2.066.tar.gz
>>> Fehler:	Zeitüberschreitung der Verbindung nach 20 Sekunden
>>> Inaktivität
>>> Fehler:	Dateiübertragung fehlgeschlagen
>>> Status:	Verbindung zum Server getrennt
>>> 
>>> May a permission problem ?
>>> 
>>> IO-Socket-SSL update patch has been send.
>>> 
>>> Best,
>>> 
>>> Erik
>>> 
>>> 
>>> On Di, 2019-09-17 at 16:05 -0400, Michael Tremer wrote:
>>>> Hi,
>>>> 
>>>>> On 17 Sep 2019, at 10:17, ummeegge <ummeegge(a)ipfire.org> wrote:
>>>>> 
>>>>> Hi Michael,
>>>>> 
>>>>> On Di, 2019-09-17 at 09:39 -0400, Michael Tremer wrote:
>>>>>> Is this on IPFire or what distribution are you using here?
>>>>> 
>>>>> Yes, the basis system is IPFire.
>>>>> 
>>>>>> 
>>>>>> Looks like a bug in the perl module. Core Update 136 comes
>>>>>> with
>>>>>> an
>>>>>> updated perl. Do you have that installed?
>>>>> 
>>>>> Yes, the build system runs on core 136. Have updated IO-Socket-
>>>>> SSL
>>>>> now
>>>>> to version 2.066 -->
>>>>> https://metacpan.org/pod/IO::Socket::SSL
>>>>> and it seems to work now. Should i send the update tooto the
>>>>> list ?
>>>> 
>>>> Yes, can you do this very swiftly because I think we might want
>>>> to
>>>> consider to re-open Core Update 136 and include this patch if
>>>> there
>>>> are more problems being caused by it.
>>>> 
>>>> Best,
>>>> -Michael
>>>> 
>>>>> 
>>>>>> 
>>>>>> -Michael
>>>>>> 
>>>>> 
>>>>> Best,
>>>>> 
>>>>> Erik
>>>>> 
>>>>>>> On 17 Sep 2019, at 00:54, ummeegge <ummeegge(a)ipfire.org>
>>>>>>> wrote:
>>>>>>> 
>>>>>>> Hi all,
>>>>>>> i wanted to report a porblem with git send-email. I
>>>>>>> currently
>>>>>>> get a
>>>>>>> 
>>>>>>> Send this email? ([y]es|[n]o|[q]uit|[a]ll): y
>>>>>>> Undefined subroutine &IO::Socket::SSL::set_client_defaults
>>>>>>> called
>>>>>>> at /usr/libexec/git-core/git-send-email line 1371.
>>>>>>> 
>>>>>>> if i try to send patches to the mailinglist. The email
>>>>>>> setup
>>>>>>> is configured like explained in the wiki
>>>>>>> 
>>>>>>> git config --global sendemail.smtpencryption ssl
>>>>>>> git config --global sendemail.smtpserver
>>>>>>> submissions.ipfire.org
>>>>>>> git config --global sendemail.smtpserverport 465
>>>>>>> git config --global sendemail.smtpuser USERNAME
>>>>>>> 
>>>>>>> 
>>>>>>> Best,
>>>>>>> 
>>>>>>> Erik
>>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>>> 
>> 
>> 
> 


  reply	other threads:[~2019-09-19 13:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17  4:54 ummeegge
2019-09-17 13:39 ` Michael Tremer
2019-09-17 14:17   ` ummeegge
2019-09-17 20:05     ` Michael Tremer
2019-09-18  5:01       ` ummeegge
2019-09-18 12:29         ` Michael Tremer
2019-09-18 12:57           ` ummeegge
2019-09-19 13:14             ` Michael Tremer [this message]
2019-09-19 14:34               ` ummeegge
2019-09-23 22:33                 ` Michael Tremer
2019-09-19 16:22               ` fail2ban false positives on people01.haj.ipfire.org (was: Re: git send-email Undefined subroutine &IO::Socket::SSL) peter.mueller

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=49FD3D92-6860-46A4-8AF3-2478C24B798D@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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