Automatic snap duplicity update to 2.0.0 has broken my scripts

[Colin Law]

On Tue, 8 Aug 2023 at 17:47, Keith <keithw at caramail.com> wrote:
>
> On 8/8/23 03:49, Colin Law wrote:
> > Snap has automatically updated my duplicity on multiple systems to
> > version 2.0.0 and all my backup scripts are failing.  It appears there
> > are breaking changes in version 2, or there is a bug.  For example,
> > when I run the command
> >
> > /snap/bin/duplicity verify   --no-encryption --full-if-older-than "4W"
> >    --log-file /home/colinl/temp/duplicity.log -v5 --exclude <exclude
> > list> --include <include list> rsync://user@server/path <target_dir>
> >
> > I get the error
> >
> > CommandLineError: Source should be url, not directory.  Got
> > '/home/colinl/temp/duplicity.log' instead.
>
> Wild guess: Does changing --log-file to --log-file= make any difference?
> Manpage doesn't specify, but "$ duplicity -h" lists the latter syntax
> for log-file and the --include and --exclude options. It makes me wonder
> since you mentioned a change to the command-line parser.

I am away for a few days, will give that a go when I get back.

>
> Do your scripts work if you revert the duplicity snap back to the
> previous (working) version?

Yes, I have reverted and all is well, I should have said that.

>
> If they do then it's probably a bug or the result of the new parser
> being more finicky about the syntax.

I think you are right.

Thanks

Colin