Re: Refreshing a mirror throws 'Cannot write to .... (Is a directory)' error, when the directory is alreary downloaded

[Tim Rühsen]

On 11/26/19 11:22 AM, Boris Behrens wrote:
> Am Di., 26. Nov. 2019 um 11:04 Uhr schrieb Tim Rühsen <address@hidden>:
>> I think you run into the (well-known) issue that there are URLs like
>>   name/
>> which is saved as
>>   name/index.html
>>
>> Then later there is
>>   name
>> which should be saved as 'name' but there already is a a subdir with
>> that name.
> Ah ok. That could indeed be a problem. I am not sure if this is the
> problem here.
> I am not fit enough with therese kind of things.
> 
>> Since with recursive (especially mirroring/timestamping) downloads
>> 'clobbering' is off, no .<N> extensions are generated. Doing so in older
>> wget versions was possibly considered a bug.
> Sweet. Well if this is expected behavior I need to find a way to handle this.

If you mirror into an existing directory, you normally only want to
update changes files. Like keeping the server's and your copy in sync.

If wget now creates .<N> files each time you sync, the files will stuff
up - even if they didn't change on the server. This is normally not what
a user wants. So, what do *you* exactly want ?

Maybe I was wrong with --clobber, another try would be --no-timestamping
after --mirror.

Regards, Tim

signature.asc
Description: OpenPGP digital signature