t stucks on gnutls too long, for some reason.
>
> I'm not aware of a way for a use to set the livecheck timeout.
>
> How long is too long?
15 seconds
On Nov 23, 2017, at 11:53, Rainer Müller wrote:
> On 2017-11-23 18:13, db wrote:
>>
>> Before the change, it should have timed out in 30", not in 30'. Why didn't
>> it?
>
> I still have no idea what these units are, please communicate clearly.
https://en.wikipedia.org/wiki/Prime_(symbol)#Desig
On 2017-11-23 18:13, db wrote:
> On 23 Nov 2017, at 17:06, Ryan Schmidt wrote:
>> ftp connections fail in many circumstances, due to either the use or non-use
>> of passive mode, or for other reasons. I'm certainly tired of attempting to
>> debug them, which is why it's great when we can remove
On 23 Nov 2017, at 17:06, Ryan Schmidt wrote:
> ftp connections fail in many circumstances, due to either the use or non-use
> of passive mode, or for other reasons. I'm certainly tired of attempting to
> debug them, which is why it's great when we can remove the use of ftp from a
> portfile an
I updated master_sites for gnutls, as the old ftp server was off line for over
a month. It seems to have been restored a couple weeks ago.
> On Nov 23, 2017, at 10:06 AM, Ryan Schmidt wrote:
>
>
> On Nov 23, 2017, at 10:04, db wrote:
>> On 23 Nov 2017, at 16:52, Ryan Schmidt wrote:
>>> $ time
On Nov 23, 2017, at 10:04, db wrote:
> On 23 Nov 2017, at 16:52, Ryan Schmidt wrote:
>> $ time port livecheck gnutls
>> real 0m1.252s
>> user 0m0.196s
>> sys 0m0.079s
>
> Hmm…master_sites was updated,
> https://github.com/macports/macports-ports/commit/1ca7e7e669f82b834b993270053c0b9331caf526#d
On 23 Nov 2017, at 16:52, Ryan Schmidt wrote:
> $ time port livecheck gnutls
> real 0m1.252s
> user 0m0.196s
> sys 0m0.079s
Hmm…master_sites was updated,
https://github.com/macports/macports-ports/commit/1ca7e7e669f82b834b993270053c0b9331caf526#diff-7672b36dcb72869ed4708bfef213e57d.
Is ther
On Nov 23, 2017, at 09:05, db wrote:
> On 23 Nov 2017, at 15:14, Rainer Müller wrote:
>> The connect timeout of 30 seconds for downloads using libcurl is hardcoded
>> in base [1] and cannot be configured.
>> [1]
>> https://github.com/macports/macports-base/blob/a1e0b3bd5c062ff4d6eb1fd23badd395bdd
On 23 Nov 2017, at 15:14, Rainer Müller wrote:
> The connect timeout of 30 seconds for downloads using libcurl is hardcoded in
> base [1] and cannot be configured.
> [1]
> https://github.com/macports/macports-base/blob/a1e0b3bd5c062ff4d6eb1fd23badd395bdd39c7f/src/pextlib1.0/curl.c#L57
Can you te
But he said 30 minutes, not 30 seconds… or is it a typo ?
Laurent
> Le 23 nov. 2017 à 15:14, Rainer Müller a écrit :
>
> On 2017-11-23 11:09, db wrote:
>> On 23 Nov 2017, at 06:42, Ryan Schmidt wrote:
>>> How long is too long?
>>
>> 30'
>
> The connect timeout of 30 seconds for downloads usi
On 2017-11-23 11:09, db wrote:
> On 23 Nov 2017, at 06:42, Ryan Schmidt wrote:
>> How long is too long?
>
> 30'
The connect timeout of 30 seconds for downloads using libcurl is
hardcoded in base [1] and cannot be configured.
Rainer
[1]
https://github.com/macports/macports-base/blob/a1e0b3bd5c0
On 23 Nov 2017, at 06:42, Ryan Schmidt wrote:
> How long is too long?
30'
or a use to set the livecheck timeout.
How long is too long?
I use a script that runs livecheck on all my ports, and does many checks
simultaneously, to reduce the impact of timeouts and slow servers.
https://github.com/ryandesign/macports-user-ryandesign/blob/master/scripts/portmylivecheck
Is it possible to set this? I checked man pages for both port-livecheck and
port but couldn't find a way. I have a shell function for a list of ports that
stucks on gnutls too long, for some reason.
14 matches
Mail list logo
