Re: Couldn't fetch when cloning a repository

Am 28.08.21 um 23:03 schrieb Alexis Praga:
> I'm trying darcs again since a few days and have hit an issue when
> cloning a (non-empty) repository hosted on hub.darcs.net.
> The error is:
>> Done fetching and unpacking basic pack.
>> Copying patches, to get lazy repository hit ctrl-C...
>> Exception while getting patches pack:
>> user error (Couldn't fetch 0000001251-f948ccb7fba745717a321df8692dd42a829f9f74bff78205e20ddcafcc0b61d8
>> in subdir patches from sources:
>>
>> thisrepo:/usr/home/alex/code/blog
>> cache:/home/alex/.cache/darcs
>> repo:.
>> repo:[email protected]:blog
>> )
>> Couldn't fetch 0000001251-f948ccb7fba745717a321df8692dd42a829f9f74bff78205e20ddcafcc0b61d8
>> in subdir patches from sources:
>>
>> thisrepo:/usr/home/alex/code/blog
>> cache:/home/alex/.cache/darcs
>> repo:.
>> repo:[email protected]:blog
>>
>>
>> By the way, I could not reach the following location:
>>    [email protected]:blog
>> Unless you plan to restore access to it, you should delete the corresponding entry from _darcs/prefs/sources.
> 
> I managed to get around it by downloading the repository as a zip file,
> running 'darcs init' and 'darcs pull'.
> After that, cloning works again.
> 
> Any idea appreciated, thanks !

Indeed I can reproduce the problem with darcs-2.16.4, with different files:

ben@home[3]:~/scratch>darcs-2.16.4 clone [email protected]:alexdarcy/blog 
--no-cache
Done fetching and unpacking basic pack.
Copying patches, to get lazy repository hit ctrl-C...
Exception while getting patches pack:
user error (Couldn't fetch 
0000002258-69b6b76aa783a1a96ffa71c33e3f3c47187191f5f8a824376662c78494ceb2dc
in subdir patches from sources:

thisrepo:/home/ben/scratch/blog
repo:.
repo:[email protected]:alexdarcy/blog
)
Couldn't fetch 
0000153496-12b83e9c17802e71926c9bf9d3cdeda3f1b93e1188de445b95556ff03cabdc4a
in subdir inventories from sources:

thisrepo:/home/ben/scratch/blog
repo:.
repo:[email protected]:alexdarcy/blog


By the way, I could not reach the following location:
   [email protected]:alexdarcy/blog
Unless you plan to restore access to it, you should delete the 
corresponding entry from _darcs/prefs/sources.


(I used --no-cache to circumvent the cache on my machine to make sure it 
actually tries to download all files.)

This is pretty strange. It works when I pass --lazy. And when I issue a 
darcs check --no-cache afterwards (which should download all missing 
files) this seems to work, too.

I can also clone from the https URL. And, notably, I can clone the same 
repo via ssh from localhost (also with --no-cache). This suggests the 
problem may lie with hub.darcs.net and not with darcs; perhaps a slow 
response runs into a timeout? I have cc'ed Simon...

Cheers
Ben
-- 
I would rather have questions that cannot be answered, than answers that
cannot be questioned.  -- Richard Feynman