Misleading error message from tlmgr

[Ralph Martin]

Hi Norbert

> On 30 Jan 2020, at 09:06, Norbert Preining <preining at logic.at> wrote:
> 
> On Thu, 30 Jan 2020, Ralph Martin wrote:
>> Now, the (no access...) part of the message  is fine - but the (not signed...) part of the message  is not, and seems to be a faulty deduction arising from the lack of access. (When the network came back on, the tlmgr update went as expected). 
> 
> How to distinguish between an unsigned database and one where the
> signature cannot be downloaded due to whatever intermittent reasons?

Doesn't the networking stack give different responses for "connection cannot be made / timed out / dropped / lost" and (signature) "file not found"? 
If so, the former could be reported as "networking error" rather than "not signed".

If the networking stack doesn't do this, perhaps the request for better error messages should be passed upwards!

Thanks for listening.

Ralph