Re: [Duplicity-talk] -asynchronous-upload needs argument?

[Scott Hannahs]

> On Oct 12, 2023, at 06:16, edgar.soldin--- via Duplicity-talk 
> <duplicity-talk@nongnu.org> wrote:
> 
> On 12.10.2023 02:56, Scott Hannahs via Duplicity-talk wrote:
>> I have tried updating duplicity to 2.1.3.  The script I have used for years 
>> is failing naturally because it uses some now removed flags.  That is fine, 
>> but now it is telling me that I need an argument to the -asynchronous-upload 
>> flag.  The man page says nothing about an argument.
>> 
>> CommandLineError: argument --asynchronous-upload: expected one argument
>> 
>> The other error is expected and I will remove "--s3-use-new-style” from my 
>> script.
>> 
>> I may try adding a numerical argument (ie 2) to the async upload flag.
> 
> hey Scott,
> 
> duplicity 2.x had a ruff start. the ui parser neded to be replaced. wrt. 
> `--asynchronous-upload` read here
> https://gitlab.com/duplicity/duplicity/-/issues/759
> 
> tl;dr simply do not use that flag anymore. it is risking to silently corrupt 
> your backup.
> 
> sunny regards.. ede

Ede,

Thanks for the info.  Silent corruption of a backup would be bad.  I understand 
the 2.x startup problems but was starting to switch by 2.1.x where I thought it 
was resonably stable.  I see the proposed patch to fix the command line error 
but will that also avoid the backup corruption?
best,
-Scott